Editing Grady Booch (section)

===Booch method===

[[File:Booch-diagram.png|thumb|250px|Class diagram]]
Booch developed the '''<nowiki/>'Booch method'''' of software development, which he presents in his 1991/94 book, ''Object Oriented Analysis and Design With Applications''.<ref name="book">{{cite book| first = Grady| last = Booch| author-link = Grady Booch| year = 1993| title = Object-oriented Analysis and Design with Applications| edition = 2nd| location = Redwood City| publisher = Benjamin Cummings| isbn = 0-8053-5340-2| url = https://archive.org/details/objectorientedan00booc}}</ref> The method was authored by Booch when he was working for [[Rational Software]] (acquired by IBM), published in 1992 and revised in 1994.

The method is composed of an [[object modeling language]],<ref>{{cite book|last=Booch|first=Grady|title=Object-Oriented Analysis and Design with Applications|year=1994|publisher=Addison-Wesley|isbn=0-8053-5340-2|chapter=Chapter 5:Notation|edition=2nd |url=https://archive.org/details/objectorientedan00booc}}</ref> an iterative object-oriented development process,<ref name="auto">{{cite book |last=Booch |first=Grady |url=https://archive.org/details/objectorientedan00booc |title=Object-Oriented Analysis and Design with Applications |publisher=Addison-Wesley |year=1994 |isbn=0-8053-5340-2 |edition=2nd |chapter=Chapter 6:The process}}</ref> and a set of recommended practices.<ref name="auto1">{{cite book |last=Booch |first=Grady |url=https://archive.org/details/objectorientedan00booc |title=Object-Oriented Analysis and Design with Applications |publisher=Addison-Wesley |year=1994 |isbn=0-8053-5340-2 |edition=2nd |chapter=Chapter 7:Pragmatics}}</ref> The recommended practices include adding more classes to simplify complex code. The methodology was widely used in [[software engineering]] for [[object-oriented analysis and design]] and benefited from ample documentation and support tools.<ref>{{cite book| first = Robert Cecil| last = Martin| author-link = Robert Cecil Martin| year = 1995| title = Designing Object-Oriented C++ Applications using the Booch Method| publisher = Prentice-Hall| isbn = 0-13-203837-4| url = https://archive.org/details/designingobjecto00mart}}</ref>

The Booch notation is characterized by cloud shapes to represent classes and distinguishes the following diagrams:
{| class="wikitable"
|-
! Model !! Type !! Diagram !! UML correspondence
|-
| Logical || Static || Class diagram || [[Class diagram]]
|-
|  ||  || Object diagram || [[Object diagram]]
|-
|  || Dynamic  || State transition diagram || [[State diagram (UML)|State chart diagram]]
|-
|  ||  || Interaction diagram || [[Sequence diagram]]
|-
| Physical || Static || Module diagram || [[Component diagram]]
|-
|  ||  || Process diagram || [[Deployment diagram]]
|}
 
The process is organized around a macro and a micro process.<ref name="book" />

The macro process identifies the following activities cycle: 
* Conceptualization : establish core requirements
* Analysis : develop a model of the desired behavior
* Design : create an architecture 
* Evolution: for the implementation
* Maintenance : for evolution after the delivery

The micro process is applied to new classes, structures or behaviors that emerge during the macro process.  It is made of the following cycle: 
* Identification of classes and objects
* Identification of their semantics 
* Identification of their relationships
* Specification of their interfaces and implementation

The notation aspect of the Booch method has now been superseded by the [[Unified Modeling Language]] (UML), which features graphical elements from the Booch method along with elements from the [[object-modeling technique]] (OMT) and [[object-oriented software engineering]] (OOSE).

Methodological aspects of the Booch method have been incorporated into several methodologies and processes, the primary such methodology being the [[Rational Unified Process]] (RUP).