You are on page 1of 3

BACHELOR OF SCIENCE IN INFORMATION TECHNOLOGY

System Analysis and Design (IT24)


CASE STUDY 2
TERM 2 2009
Instructions:

NO marks will be awarded if any part of it is found to be copied directly from other web site or from
another student.
Complete this cover sheet and attach it to your final documents.

Student declaration:
I declare that:
I understand what is meant by plagiarism
The implication of plagiarism has been explained to me by my institution
This is all my own work and I have acknowledged any use of the published and unpublished works of other
people.

Students signature: Date:


Total number of pages including this cover page
Submission
Date
Students
ID
Students
Full Name
Lecturers
Name

Due Date
Class Code

Ms. Marie Joy P. Morano

OFFICIAL USE ONLY


Markers comments

Markers name

T3 2009 Case Study


IT 24 System Analysis and Design

Marks Awarded

THE STATE PATROL TICKET PROCESSING SYSTEM


The purpose of the State Patrol ticket procession system is to record driver violations, to
keep records of the fines paid by drivers when they plead guilty or are found guilty of moving
violations by the courts, and to notify the court that a warrant of arrest should be issued when
such fines are not paid in a timely manner. A separate State Patrol system records accidents and
verification of financial responsibility (insurance). Yet a third system produces driving record
reports from the ticket and accident records for insurance companies. Finally, a fourth system
issues, renews, or suspends drivers licenses. These four systems are obviously integrated in that
they share access to the same database, but otherwise, they are operated separately by different
departments of the State Patrol. State Patrol operations (what the officers do) are entirely
separate.
The portion of the database used with the ticket-procession system involves driver date,
ticket date, officer date, and court date. Driver date, officer date, and court date are used by the
system. The system creates and maintains ticket date. Driver attributes include license number,
name, address, date of birth, date licensed, and so on. Ticket attributes include ticket number
(each is unique and preprinted on each sheet of the officers ticket book), location, ticket type,
ticket date, ticket time, plea, trial date, verdict, fine amount, and date paid. Court and officer date
include the name and address of each, respectively. Each driver may have zero or more tickets,
and each ticket applies to only one driver. Officers write quite a few tickets.
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 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-procession 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 drivers license be suspended, and the system that processes drivers
licenses handles the suspension.

T3 2009 Case Study


IT 24 System Analysis and Design

Student Name:
Student ID:
Case Study Title:
Documentation
Preliminary Investigation
Report
Data and Process
Modelling:
Data Flow
Diagram
Data Dictionary
Decision Trees
Decision Table
Object Modelling:
Use Case Diagram
Class Diagrams
Sequence Diagram
State Transition
Diagram
Activity Diagram

Base
mark
10

10
5
5
5

10
5
10
10
5

Data Design
Entity
Relationship
Diagram

10

Application Architecture

10

Project Scheduling
Total

5
100

Marker Name:
Marker Signature:
T3 2009 Case Study
IT 24 System Analysis and Design

Mark
Allocated

Comments

You might also like