Keep track of penalties incurred by drivers through software


In an advanced country, a point system is maintained to keep track of erring drivers, and vehicle owners. The objective for this lab is to come up with software to keep track of penalties incurred by the drivers, and help decide those drivers whose driving license should be revoked.

Each driver is assigned an initial score of ten. Every minor offense (parking ticket, over speeding, under speeding, etc.) will be awarded a penalty of -1. Every major offense (drunk driving, reckless driving, and accidents) will be awarded a penalty of -5.  If a driver's score becomes 0 or negative, his/her license will be revoked.

For this problem, it is assumed that the owner of the car is always going to be driving the car. The list of offenses is provided as a text file containing the vehicle number and the nature of offense (Minor, Major). The list of drivers along with their UID and license number is available as input in a file named drivers.txt. A file named owners.txt maps the vehicle number to the UID of the owner. For the sake of simplicity, license number is a 10-digit integer, and vehicle number contains 3 characters followed by 4 digits. UID is a unique identifier provided to every citizen in the country, and it contains 12 digits.

The data structures to be used, the file format for various files and the general step-by-step process for this lab’s task are being stated in the remainder of this document.

 Data structures to be used:

A) Vehicle: This contains the list of all vehicles along with the vehicle number and UID of owners, with UID as the key.  Vehicle is maintained as a dynamic list.

B) Drivers: This represents the dynamic list of the tuples (license number, UID, score).

C) RevokeList: This list contains the current list of revoked drivers in the form of tuple (license number, vehicle number, UID).

File Formats:

The file format for the input files is as follows:

drivers.txt:

 ,

For ex:

182930101222,9929929921

 The file format for owner.txt is as follows:



Note: There is no space between number of items and item name. End Note.

For ex:

182930101222,KLA1512

 The file format for offenses.txt is as follows

 

For ex:

DNA1423 1

KAS1002 0

BEL1923 0

KAS1002 1


Note that 0 indicates Minor offense here, and 1 indicates a major offense.

Step 1: Identify appropriate data structures relevant for the problem and write them in Offense.h

Step 2: Design Offense ADT with the following operations (OffenseOps.h). The relevant operations are:

i) populateVehicles: This function reads input from file and populates its content in the Vehicles list in lexicographic order of vehicle numbers. It then returns the populated list.

ii) populateDrivers: This function reads input from file  and populates its content in the Drivers list in non-decreasing order of UIDs. It then returns the populated list.

iii) updateOffenses: This function reads the contents of the file containing offenses. It looks up the Vehicle list to find the UID of owner. Using the UID, it looks up the license number of the driver. It then updates the score in the corresponding tuple in the drivers list.

iv) markRevokedDrivers: This function identifies all drivers whose license needs to be revoked, and puts them in the file named revoke.txt

v) Add prototypes in OffensesOps.h

You might need the following support functions:

a)  insertVehicle: this function inserts a row of vehicle details in order

b)  insertDriver: this function inserts a row of driver details in order

c) lookupUID: search for a UID from the Vehicles list given the vehicle number, and return it.

d)  lookupVehicle: search  for  a vehicle number from the  Vehicle List given the  UID of the owner and return it.

e)  lookupDriverDetails: search  the Drivers list based on UID,   and return the index of the entry containing that UID.

 

Step 3: Implement the above operations in the corresponding c files

·         All relevant code must go to OffensesOps.c

·         All list creations must have filename as a parameter.

 Step 4:  driver file.

Create a simple driver file (revoke.c) that can read multiple input files corresponding to the various input files. The names of input files are passed as command line parameters.  Note that if no input file is passed, the program should attempt to run with drivers.txt, owners.txt and offenses.txt for the relevant input set.

The executable revoke generates output files revoke.txt that will contain the list of drivers (license number, UID, vehicle number) whose license is to be revoked.

For the purposes of testing, you may implement some functions to print the data structures or other test data.

But all such functions must be commented before submission to server.

Deliverables: All relevant header files, OffenseOps.c, revoke.

Request for Solution File

Ask an Expert for Answer!!
Basic Computer Science: Keep track of penalties incurred by drivers through software
Reference No:- TGS086

Expected delivery within 24 Hours