Question

Use case Names: Record a Ticket

Scenario: Officer Issues a Ticket

Triggering Event: Traffic Ticket

Description: The Officer provides the Clerk with the ticket. And then the ticket information is verified by the clerk. First he/she enters the Officers badge number and next enters the drivers license number to verify their information.

Action: Clerk

Stakeholders: Manager, Officer

Precondition: The officer and driver must exist.

Postcondition: The ticket must exit and be associated with the Officer, the driver, and the Court.

Exception Conditions: Officer not found, Driver not found.

Flow of Event:

Action	System
1. Officer enters offices badge number.	System reads officer information and displays name.
2. Officer enters drivers license number.	System reads the drivers information and displays the drivers name and address.
3. Clerk enters ticket information.	System displays ticker and drivers information.

Task

1. Develop a DFD diagram 0 for the use case based on the narratives. Diagram 0 should include major processes in the use case. Group use case steps into a few processes (for example, three or four). Do not model each step. No child diagrams needed.   
2. Develop an Activity diagram for the use case based on the narrative.

Answer 1

Context level DFD, also known as level 0 DFD, sees the whole system as a single process and emphasis the interaction between the system and external entities.

It’s designed to be an abstraction view, showing the system as a single process with its relationship to external entities. It represent the entire system as single bubble with input and output data indicated by incoming/outgoing arrows.

For above example DFD 0 is as given below:

Activity Diagram:

Activity diagram is another important behavioral diagram in UML diagram to describe dynamic aspects of the system. Activity diagram is essentially an advanced version of flow chart that modeling the flow from one activity to another activity.

For given narrative, activity diagram is as follow: