130 likes | 317 Views
The OOD Process. Design as a Logical Continuation of Analysis. Object-Oriented Design “Steps” of the Process?. OOA Model. OOD. Process. OOD Model. OOA. The Levels of the OOD Process - High-Level Design (1). extend the OOA Model [Coad/Yourdon] think in terms of OO model components
E N D
The OOD Process Design as a Logical Continuation of Analysis
Object-Oriented Design“Steps” of the Process? OOA Model OOD Process OOD Model OOA
The Levels of the OOD Process - High-Level Design (1) • extend the OOA Model [Coad/Yourdon] • think in terms of OO model components • OOA results are the basic component • problem domain component • include other components in the model • include human interface (HIC) • task management (TMC) • data management (DMC) ==> acknowledge that we develop a computer-based system around/with the analysis results
The Levels of the OOD Process - High-Level Design (2) • structure your approach • decide on a general system architecture • organize the objects into a well specified system structures • organize and extend scenarios according to generally applicable patterns • reuse existing patterns • generic templates • generic architectures and frameworks
The Levels of the OOD Process - Detailed Design • refine and • map the OOA Model to the infrastructure • detailed algorithms and datastructures • implementation of OO structures • implementation of states and transitions • optimization • maximize reuse • exception handling • etc.
The OO Co-DesignProcessMatrix of Domain Components and Levels extend HIC TMC PDC DMC high-level Design Miniworld refine & map detailed Design
Object Oriented Design means to navigate the domain/level matrix with the purpose to develop all model components on both levels in a meaningful sequence.
OOD Deliverables - I • extended Static Objectmodel • Coad & Yourdon: • Problem Domain Component (PDC) • Human Interaction Component (HIC) • Task Management Component (TMC) • Data Management Component (DMC) • on the level of high-level design • basically “another analysis step” • on the level of detailed design • connect to existing class hierarchy, ...
OOD Deliverables - II • completed & extended Scenarios • extend old scenarios accross domains • reflect the chosen architecture’s dynamics • build links between domain components • add new scenarios to accomodate internal organisation • e.g. data backup, rollback, load/save • on the level of high-level design • extended and new scenario diagrams (& dictionary) • on the level of detailed design • complete all details in dictionary • diagrams only if necessary (optimization, ...)
Scenarios extend HIC TMC PDC DMC high-level Design refine & map detailed Design
OOD Deliverables - III • Object Dictionary • document & specify the added domain components • very much like during analysis: objects, structures, ... ==> for high-level design • map and refine existing specifications • translate structures, STDs, ... • map to existing patterns and objects • document optimizations ==> for detailed design
As in OOA it holds for OOD: Static Model and Scenarios are documented as graphical Views of the more complete Object Dictionary.
Scenarios Dictionary Static Model The complete OOAD SpecificationThe “schoolbook scenario” HIC TMC PDC DMC high-level Design Miniworld Scenarios detailed Design Dictionary Static Model