Reading material for these exercises:

• Holubs UML reference card is linked on the material page.
• Maciaszek: ch. 2.2.5 (pp 63-69) interactions, ch 4.3.3-4.3.4 (pp 143-146), ch 5.1.- 5.1.5, 5.1.7 (pp 155-167, 169-172)

Reading material for the next week:

• Maciaszek: ch 7 pp 244-267.
• Sari A. Laakso: Introduction to Application design, user interfaces, Department of computer science, university of Helsinki, 1999 (handout sales office, room B435, open daily 12-13)

Tasks

1. The description of the information content of the pizza system in task 3.5 did not cover the pizza delivery. Draw the use case specific class diagrams for the use cases:

next order from queue

The pizza maker takes the next order from the order queue and gives his estimate of the time the order is ready for delivery

order ready

The pizza maker marks the order as ready.

delivery assignment

The delivery manager takes a list of orders estimated to be ready within the next 15 minutes. He collects oreders to be delivered to the same area into one assignment. He takes a list of the estimated return times of delivery boys and selects the delivery boy for the assignment.

delivery

A delivery boy picks up an assignment. He prints the bills for all the orders in the assignment and waits for the orders to be ready. He registers his estimated return time from his delivery trip.

2. Combine the object diagrams of task 1 to the object diagram of task 3.5. (Diagram will be available as Plastic Lite PLA-file in the example solutions of last week on Friday 22.11)

3. Construct a dependency matrix to indicate how the use cases of the pizza system are related to the information content delined in task 2. Try to find out missing information or missing use cases.

The matrix should have one row for each class or association, and one column for each use cases. Use the following values in the elements of the matrix: C = use case creates an object or association instance, D = use case deletes an object or association instance, U = use case updates some attribute values of an object, R = Use case reads the information.). An example:



Each class and association should have a use case for creating instances. Most classes usually have use cases for deleting instances and for modifying them.

4. The appendix contains the essential part of a card playing program. Construct a class diagram to describe the structure of this program. (This kind of diagram building is called 'reverse engineering'. Normally you proceed from diagrams to program code).
(Hint: An interface should be treated like a class.)



5. Draw a sequence diagram to describe the cooperation of objects in providing the service CardGame.round of the example program of the previous task. Assume that there are two players.



---

18.11.2002 Harri Laine