CIS 616 Final - practice

Definitions.

1. [ ____] A type of relationship between A. Aggregation

classes that allows inheritance of attributes B. Cardinality
by subclasses. C. Generalization
2. [ ____] An interative style of software D. JAD
engineering methodology where the phases E. JIT
of the life cycle are repeated F. Participation
3. [ ____] A diagram which shows the G. RAD
various states that an object may have in its H. Spiral Method
lifetime. I. State diagram
4. [ ____] A notation for showing concurrent J. Swimlane notation
states K. Walkthrough
L. Waterfall Method

Short Answer.
1. Distinguish between an ERD and a class model

Comprehensive True/False
1. [ T | F ] A context diagram shows the flow of information from a user into the system.
2. [ T | F ] Both state and sequence diagrams show objects and messages, but only sequence
diagrams show objects being created.
3. [ T | F ] Business process reengineering aims for small, gradual improvements in business
operations.
4. [ T | F ] Functional requirements describe response time and other constraints on the system.
5. [ T | F ] Enterprise Resource Planning depends on purchasing software that has been developed
from industry best practices.
6. [ T | F ] In the context diagram of the Appointment Scheduling system, the requirement that
customers are charged for no-shows is modeled as a temporal event.
7. [ T | F ] Stakeholders are those who will be using the new system.
8. [ T | F ] System analysis focuses on understanding the business domain and specifying how the
system will perform.
9. [ T | F ] The “extends” relationship refers to a manditory association between two classes.
10. [ T | F ] There will be one use case for every functional objective defined in the charter.
System Modeling
You have courageously accepted responsibility for completing a specifications document initiated by
your predecessor (who recently mysteriously disappeared, without a trace). Fortunately, almost
every model gives you hints that you can use to complete (or correct) other elements of the analysis.

From the Introduction and System Summary you are able to determine the following:
The client is the State Traffic Court Clerk's Office.
The purpose of this system is state patrol ticket processing.
The client has indicated that they want the system to:
 Record driver violations and accidents
 Produce driving record reports for insurance companies
 Verify responsibility (insurance)
 Keep records of fines paid by the drivers
 Notify the court that a warrant for arrest should be issued when fines are not paid within two
weeks of being due
 Issue, renew or suspend driver's licenses

1. Add detail as necessary to correct this functional objective for the system (5 pts)
The system shall automatically generate a report, containing driver and ticket information,
to the insurance company whenever a driver is found guilty of a moving violation.

2. Use the system description and functional objective above to complete this partial event table and
preliminary list of data entities for this system. [no entry is required for the shaded blocks.] (5 pts)

Event Trigger Source Essential Activity Response Destination

Officer submits New Officer Verify driver license and record new n/a n/a
ticket ticket ticket
Driver sends in fine Fine Driver Record fine payment n/a n/a
payment Payment
Driver requests trial Trial Driver Process trial request  Trial Driver
request data
questionnaire Court
 Ticket
details
Court sends in Verdict Court Record verdict and send insurance Ins. Report with Insurance
verdict report to Insurance Co. driver and ticket Company
information
Time to produce two clock Produce warrant request Warrant request Court
warrant request weeks notice
after
 fine due
3. What is the minimum number of use cases that will appear on the initial use case diagram? (2 pts)
[_________]

4. If the court clerk is the only actor on the use case diagram, how many externals will there be on an
expanded scope context diagram for this system? (3 pts) [__________]

5. Provide the last two steps in the following use case scenario Basic Flow for the 'Enter Ticket'
scenario (5 pts)

1. The case begins when the clerk wishes to create a new ticket
2. The clerk submits the driver's license number.
3. The system displays the name and address that corresponds to given license number.
4. The clerk verifies the name and address.
5. The system creates a new ticket record

6. Clerk enters ticket details

6. Refer to the basic flow for the 'Enter Ticket' use case above. Correct the proposed interface
prototype for this use case. (5 pts)

Enter Ticket
Driver Name
Last [____________________]
First [____________________]

Ticketing Officer Badge ID [_____________]

Ticket Details
Date [___/____/___]
Time [___:___]
Violation Type [_____]
Location (major intersection) [______________________________]
Fine Amount [_$_________]
SUBMIT
 7. Use all the information given here and elsewhere in this test, to add associations and
cardinality to the class diagram for this system. Each ticket applies to only one driver, but
drivers may never get a ticket (or they might get lots). Drivers may choose to contest their
ticket in court or not. Officers write quite a few tickets. (10 pts)

Driver
Driver
License number Officer
License number
Name *
Name Address
Address Badge Number
Exp DateExp Date Name
Date of Birth
Date of Birth Rank
Restriction
Restriction Assignment
Address

Ticket Court
Ticket number* Court ID
Date of ticket
Time of ticket Name
Location Address
Violation Type
Fine Amount
Date Paid

Court

Court Number*
Name
Ticket
Address

Ticket Number Trial

Trial Date
Time Plea
Plea Location Date
Trial Date
Type Verdict
Verdict
Fine
Date Paid
8. Use the system description, partial basic flow and partial class diagram above, to complete this
sequence diagram for the 'Enter Ticket' Use Case (5 pts)

:driver

clerk

VerifyID(DriverID)

:ticket

CreateTicket(DriverID, TicketDetails)