CIS 644 Tues. Sept. 7, 1999 blank

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

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

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

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

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

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

* 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 ………… ++

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)

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

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

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

END