Order instructions

In this assignment you will explore events, use cases, and a CRUD table for domain classes.

• Complete Exercises 1, 2, 3 on p. 87 for the State Patrol Ticket-Processing System
• In your Word document, include a title page, your name, course, and instructor information.
• Clearly mark the answers to the questions.
• Your submission should be at least 3 pages.

Case Study

The State Patrol Ticket-Processing System

The purpose of the State Patrol ticket-processing system is to record moving violations, keep records of the fines paid by drivers when they plead guilty or are found guilty of moving violations, and notify the court that a warrant for arrest should be issued when such fines are not paid in a timely manner. A separate State Patrol system records accidents and the verification of financial responsibility (insurance). A third system uses ticket and accident records to produce driving record reports for insurance companies. Finally, a fourth system issues, renews, or suspends driver’s licenses. These four systems are obviously integrated in that they share access to the same database; otherwise, they are operated separately by different departments of the State Patrol.

When an officer gives a ticket to a driver, a copy of the ticket is turned in and entered into the system. A new ticket record is created, and relationships to the correct driver, officer, and court are established in the database. If the driver pleads guilty, he or she mails in the fine in a preprinted envelope with the ticket number on it. In some cases, the driver claims innocence and wants a court date. When the envelope is returned without a check and the trial request box has an “X” in it, the system does the following: notes the plea on the ticket record; looks up driver, ticket, and officer information; and sends a ticket details report to the appropriate court. A trial date questionnaire form is also produced at the same time and is mailed to the driver. The instructions on the questionnaire tell the driver to fill in convenient dates and mail the questionnaire directly to the court. Upon receiving this information, the court schedules a trial date and notifies the driver of the date and time.

When the trial is completed, the court sends the verdict to the ticketing system. The verdict and trial date are recorded for the ticket. If the verdict is innocent, the system that produces driving record reports for insurance companies will ignore the ticket. If the verdict is guilty, the court gives the driver another envelope with the ticket number on it for mailing in the fine.

If the driver fails to pay the fine within the required period, the ticket-processing system produces a warrant request notice and sends it to the court. This happens if the driver does not return the original envelope within two weeks or does not return the court-supplied envelope within two weeks of the trial date. What happens then is in the hands of the court. Sometimes, the court requests that the driver’s license be suspended, and the system that processes drivers’ licenses handles the suspension.

• 1. To what events must the ticket-processing system respond? List each event, the type of event, and the resulting use case.
• 2. Write a brief use case description for each use case.
• 3. The portion of the database used with the ticket processing system involves driver data, ticket data, officer data, and court data. Driver data, officer data, and court data are read by the system, and the ticket processing system creates and updates ticket data. In an integrated system like the ticket-processing system, some domain classes are created by and updated by other systems, as described in this case. Create a table with systems down the rows and the four types of data (domain classes) across the columns. Indicate C, R, U, or D for each domain class and each system.