“Chapter 9” Managing Object Design Done By: Alia Waled

Chapter Objectives Management challenge Documenting Object Design Assigning Responsibility

 1- Increased communication complexity  2- Consistency with prior decisions & documents

I t describes object design, the decomposition of subsystems into packages and classes, and the class interface. I t is used to exchange interface information among teams and as a reference during testing. 1-Self-contained ODD generated From model. 2- ODD as extension Of the RAD. 3- ODD embedded into source Code.

Analysis Document analysis Analysis model RAD System Design Subsystem decomposition Design goals Object design Initial object Design model Generate class stubs Implementation Initial class stubs Comment code Document Object design ODD

Object Design Model 1. Introduction 1.1 Object design trade-offs 1.2 Interface documentation guideline 1.3 Definitions, acronyms, and abbreviations 1.4 References 2. Packages 3. Class Interface Glossary

 Object design is characterized by a large number of participants accessing and modifying a large amount of information.  Several roles collaborate to control, communicate, and implement changes. These include the members of architecture team, liaisons and configuration managers.

1- The core architect 2- The architecture liaisons 3- The object designers 4- The configuration manager 5- Technical writers

The approach that needs high effort to maintain because of redundancy is: 1-Self-contained ODD generated From model 2- ODD as extension Of the RAD 3- ODD embedded into source Code. It is used to distinguish source code comments from object design description: 1- RAD 2- Tagged 3- class stubs