1. CIS 644 Tues. Sept. 7, 1999
blank

2. Email question: what model notation??
Answer: varies…
pure UML …. Prob. Domain level
w or w/o aggregation
w or w/o numbers
“owns” symbol
… implementation level

3. Problem: Auto agency PD model:
features … defined by manufacturer
autos … arrive, sold, have features
customers … select feature preferences
can buy or order autos
auto orders

4. Issues:
* “features” : don’t hard code dyanamic attributes
* PD / implementation level : 4 each
* Collections: Auto vs Autos …. 4 each

5. ?? Ambiguous / unknown requirements:
… can customer order multiple autos?
Strategy:
first build simple requirements model;
identify requirements questions
(and recommendations)

6. * Objects/classes vs methods:
classes define objects.
Objects have retained state.
(generally nouns)
what about: “arrive” , “search” or “match”
generally… methods
[advanced: class factories ]

7. * Generalization:
of common base classes
as…. Customer --> Person

8. * how to name relations:
by domain vocabulary: purchaser
generic, as “theCustomer”
* how to implement relations:
by reference … static or dynamic
by key …………. dynamic
by copy ………… ++

9. Class diagrams :
one class may represent several objects !
E.g. Airports
(generally static structure) VS
object diagrams
instances of class diagram
(may be different views for different cases)

10. Redo Auto class diagram (w annotations)
use some drawing tool.

11. Make reservation scenarios:
… partial view … p. 23
overview scenario … w/o parameters
supported by detail scenarios with parms

12. Do overview scenario for:
“find matching car”
and “place order”

13. END