Department of Motor Vehicles - Computerized Database System

Initial Requirements Documentation

Ryan Anderson

Thad Scott

Dave Mitchel

Wu Ding

Overview of System

This system will serve the data processing needs of the Department of Motor Vehicles (hereafter DMV) and related law-enforcement agencies in tracking automotive vehicles, registrations, titles, license plates, driver's licenses and other related documentation.

This system should be comprehensive in nature, automating tasks where appropriate, and augmenting human efforts elsewhere.

Business Requirements

The business needs of these departments encompass a wide variety of data, detailed in the following chart:
type auto, cycle, trucks, trailers
VIN #s allocated to certain vehicle parts (engines, body, etc..)
owner(s) primary owner, plus any liens and such held by other parties

license plates (id# stored)
cost vehicle type dependent
rules special rules which apply to this type of vehicle
driver's license number usually of the owner, may occasionally be different
tickets usually parking
renewal/expiration date at which this expires, and whether or not it can be renewed
tags latest tags issued

type dealer, owner, manufacturer
location/status which factory or warehouse, DMV office, or a status such as allocated, inactive, retired, stolen
owner reference to the registration and title related to this plate
plate number the license plate number

Driver's Licenses
types Commercial, cycle, chauffeur, general
tests status of both road and vision
tickets tickets assigned to this person (usually moving violations)
restrictions vision, restricted to driving to/from work/school, handicapped, suspended, revoked, etc.
id number standard driver's license number
picture digitized picture stored (not in prototype)
personal information name, address, birth date
physical information height, weight, eye color, hair color, etc.

Other permits
handicapped permits portable tags or plates

This system must also be able to handle a large variety of transactions on the data. These are detailed below:

Department of the Motor Vehicles
modify plates and tags can both change over time
fleet handling creation, renewal, and modification of large numbers of vehicles with a common owner
notices mailed, both renewal and tickets
Driver's licenses
Apply (can act as voter registration)
Notes for DMV
Should halt on recognition of warrants and/or tickets that prevent any of these transactions from occuring
Should be able to handle mailed renewals, applications, etc where appropriate
Law Enforcement
input/modify tickets parking violations
Driver's License
input/modify tickets moving violations
Notes for Law Enforcement
must support global entry of warrants with updates of both registration and driver's licenses

Hardware Requirements

For this prototype, only a simple Windows 95 workstation, with 32 megabytes of ram, and 1 gigabyte of disk space.

For the actual implementation, a two-tiered arrangement of servers would be ideal. The first tier would handle approximately 10 branch offices per server, using a short-distance WAN connection to handle the client connections to the server. The main server (probably a cluster of two or more) would be connected to the regional office servers via a wide area network as well.

The servers would be running DB/2, with replication technology controlling updates between them each night. Law enforcement functions (such as additional tickets and arrest warrants) would be processed through the servers at a priority level.

Client workstations would be identical to the prototype setup. Law enforcement clients would be ruggedized laptops with digital cellular connections to a law enforcement server.

Software Requirements

Microsoft Visual C++, version 5.0 will be used to develop both the prototype and the production application, while Microsoft Access will be used solely for the prototype database backend.

Time Spent:

Ryan Anderson 5 hours

Thad Scott 2 hours

Dave Mitchel 2 hours

Wu Ding 2 hours