The BOOCH Methodology

The Booch methodology is a widely used object-oriented method that helps you design your system using the object paradigm. It covers the analysis and design phases of an object-oriented system. Booch sometimes is criticized for his large set of symbols. Even though Booch defines a lot of symbols to document almost every design decision, if you work with his method, you will notice that you never use all these symbols and diagrams. You start with class and object diagrams in the analysis phase refine these diagrams in various steps. Only when you are ready to generate code, do you add design symbols and this is where the Booch method shines, you can document your object-oriented code. The Booch method consists of the following diagrams:
1. Class diagrams
2. Object diagrams
3. State transition diagrams
4. Module diagrams
5. Process diagrams
6. Interaction diagrams

The Booch methodology prescribes a macro development process and a micro development process.

1.The Macro Development Process

The macro process serves as a controlling framework for the micro process and can take weeks or even months. The primary concern of the macro process is technical management of the system. Such management is interested less in the actual object-oriented design than in how well the project corresponds to the requirements set for it and whether it is produced on time.

The macro development process consists of the following steps:
1. Conceptualization
2. Analysis and developenent of the model
3. Design or create the system architecture
4. Evolution or implementation
5. Maintenance

2.The Micro Developenent Process

The micro process is a description of the day-to-day activities by a single or small group of software developers.

The micro developenent process consists of the following steps:
1.Identify class and objects
2.Identify class and objects semantics
3.Identify class and object relationships
4.Identify class and object interfaces and implementation.