Adding Value to the Unified Process

Issues the tutorial will concentrate on • The UP is "use-case driven." Generalize this to "behavior driven." For example, events can be more helpful than use cases when modeling a domain with no business or system boundaries. • The UP is "architecture-centric." Distinguish the many kinds of architecture needed (technicallyoriented, subject-based, logical, physical, etc.). • Raise the status of domain, or business, models. A model of the key types in a domain can provide a single vocabulary for other models. • Separate the content of a model from its time of construction. For example, making a design decision early in a project does not turn it into an analysis issue, as the UP implicitly suggests. • Distinguish adding detail in order to increase precision from adding detail in order to support refinement. For example, avoid premature design of behavior by describing use cases with informal preconditions and postconditions rather than with sequences of actions. • Individual models are projections of a single, underlying model, and can sometimes be combined to good effect. For example, you can get the benefits of a sequence diagram and a collaboration diagram by overlaying the diagrams. • Define the UML carefully enough to support cross-checking between diagrams. For example, check that states are distinguishable on type models. (The tutorial will offer a list of more than 20 cross-checks.) • Work with example-level models as well as general-level models. For example, use snapshots to uncover subtleties of type models. • Define maturity tests on models. For example, ascertain whether certain cross-checks have been performed, and determine whether key example-level models are supported by the general-level models.