Professional Documents
Culture Documents
To follow: A medium sized case study for a car rental administration system
Explanation of central UML diagrams and language features therein
Used here: Use case, class, object, sequence, and activity diagrams
Development of the case study also demonstrates a typical development
process
Diagram order in this document does not reflect the order occurring in the
development
Typical Modeling Steps (TTDs) :
(1)
Start with a use case diagram giving an overview on the system, its
boundaries and its main functionality. Develop a specification for each use
case. (Exer. 1)
(2)
Develop sequence diagrams as desired scenarios for the system
structure and behavior (based on the flows in use case specifications). (Exer.
2)
(3)
Develop a class diagram based on the classes identified in (2). (Exer.
3)
(4) Develop a statechart diagram for each class; start with a textual
description of the statechart diagrams; continue with a more formal
description for the statecharts (optional)
(5)
Check whether the existing object diagrams and sequence diagrams are
consistent with the class diagram and the statechart diagrams; if
neccessary, modify them (partly done by CASE tools)
(6)
(7)
If an operations seems to become stable (no changes in the diagrams
for the parts with that operation), start to develop activity diagrams for
that operation; begin with a textual description and advance to a more
formal one
(8)
return a car more than 24 hours earlier, or more than 2 hours late, the charge
will be re-calculated based on the current rules stated by the company.
a. Based on the above description, identify the actors and use cases, and
draw the use case diagram.
b. Select one of the above use cases and write the specification of the use
case of your choice.