OOADwthUMLDesigner.pptVIP

March 21, 1999 OMG Meeting - Philadelphia, PA — Using VisualAge UML Designer Goals To understand the key tasks of OOAD To understand the key features of IBM VisualAge UML Designer Challenges of Analysis Design Climb Every Mountain The Wholeness of a System Iterative Incremental Development Essentials of OOAD Manage complexity Control levels types of abstraction Rich modeling artifacts and semantics Traceability from requirement through implementation Support iterative and incremental development Integration of models UML Designer Design Approach Transformational Linked model levels: requirement, analysis, design Appropriate level of details Avoid confusion of levels Recognize imprecision of natural language Evolutionary -- incremental iterative Minimalistic and pragmatic Only artifacts that are relevant for implementation or for setting system implementation Non-prescriptive -- methodology-neutral UML Designer Features Integrated model graphic views Seamless OOAD support Methodology-neutral Team modeling, shared repository UML diagramming compliance Java Smalltalk code generation UML Designer Features (Continue) Models Model, relationships, model elements Requirements, Concepts, Actors, Use Cases Things and Responsibilities Protocols and Message Specifications, Class Designs and Real Class UML Designer Features (continue) Browsers By Relationships, by Hierarchy Edition Changes Traceability Diagram Editors Use Case Diagram Class Diagram Sequence Diagram UML Designer Features (continue) Multiple publishing output formats HTML RTF UML Designer Unified Modeling Language-UML UML is two distinct things: ?A general notation for diagramming OOAD modeling artifacts via distillation of industry best practices, for example: Use case diagram Class diagram Sequence diagram ?A meta-model Assumes implicit, arbitrary, hypothetical program model UML Convergence of 3 methodologies (with large mind-share), crafted at Rational Software Corp Booch’s OOD Rumbaugh’s OM