High-Quality Modeling in UML
Richard Mitchell · Technology of Object-Oriented Languages and Systems · 2001
• Distinguish three kinds of models: models of a problem domain, models of a system as a black-box, and models of the internal workings of a system. • Raise the status of domain, or business, models. • Carry key concepts in models of a problem domain through into system models and design models, giving continuity of models. • Ensure that continuity addresses both behavioural aspects and structural aspects. • Build models of behaviour, such as essential use case models, in terms of a vocabulary provided by models of structure. • Cross-check every model to other models, to ensure that models are consistent. • Test general-level models (such as type models and essential use case specifications) using example-level models (such as snapshots and scenarios). • To get the full benefits of continuity, cross-checking and testing, constrain how you interpret UML models. • Distinguish adding detail to achieve precision from adding detail at a lower level of abstraction. • Distinguish the content of a model from its time of construction (corollary: phases in modeling can be misleading).