Object Oriented Design - Booch

By,

Rahul

Object Oriented Design - Booch

Ø  This method designed by Booch represents the following four models :

           a. logical model     : Defines class hierarchies. And key abstractions.

            b. physical model  : Defines the concrete software and hardware compositions of the

                                              system’s implementation.

            c. static model        : Static associations in the system using class diagram. Object
                                               diagrams, module diagrams and process diagrams.

            d. dynamic model. : Dynamic associations in the system using state transition
                                               diagrams and interaction diagrams.

Ø   The whole methodology can be broken down into two processes viz :

a. Macro development process :

                 i. Leads to the micro development process.

                 ii.More concerned with the technical management of the system.

                iii.Preserves the traditional phases of analysis and design. Thus consists 

                     of following sub phases :            
                     1.       Conceptualization : Establish the core requirements and the set

                                                               of goals meeting those requirements and design
                                                               a prototype.                                                                                                                                          

                     2.       Analysis and development : Use of diagrams for further clarity.

               
First use the class diagram to understand the roles and  responsibilities of the objects. Then use either object diagram or interaction diagrams to understand how those objects interact with each other and how do they achieve various functionalities in various scenarios.

i. Design:  Use the class diagram and object diagrams drawn in previous phase to
                  decide the actual design of the system and various interactions between
                  classes.Use the module diagram to decide where to declare each class
                  and object.
                  And use process diagram to decide where to allocate a process.

ii. Evolution : Pass the system through various iterations to make the design better
                        by identifying designing flaws. Produce a release at the end of each
                        iteration such that each release is better than its previous one. 

     iii.  Maintenance : Making localized changes to eliminate bugs and add new requirements     

                                    (if   any).

   b. Micro development process:

i.         It is an integral part of Macro development process.

ii.       This is a description of day-to-day’s work and tracking the activities of individual

                          users or a small group.

iii.      It contains the following activities :

                          a. Identify classes and objects.

                          b. Identify semantics of the above classes and objects.

                          c. Identify relationships among these classes and objects.

                          d. Specify the interfaces and implementation of the above classes.