Grady Booch

Last updated
Grady Booch
Grady Booch, CHM 2011 2 cropped.jpg
Grady Booch in 2011
Born (1955-02-27) February 27, 1955 (age 64)
Alma mater University of California, Santa Barbara (M.S.)
U.S. Air Force Academy (B.S.)
Known for
Scientific career

Grady Booch (born February 27, 1955) is an American software engineer, best known for developing the Unified Modeling Language (UML) with Ivar Jacobson and James Rumbaugh. He is recognized internationally for his innovative work in software architecture, software engineering, and collaborative development environments. [1] [2] [3] [4] [5] [6] [7]



Booch earned his bachelor's degree in 1977 from the United States Air Force Academy and a master's degree in electrical engineering in 1979 from the University of California, Santa Barbara. [8]

Career and research

Booch served as Chief Scientist of Rational Software Corporation since its founding in 1981 and through its acquisition by IBM in 2003, where he kept working until March 2008. Afterwards, he became Chief Scientist, Software Engineering in IBM Research, and series editor for Benjamin Cummings.

Booch has devoted his life's work to improving the art and the science of software development. In the 1980s, he wrote one of the more popular books on programming in Ada. He is best known for developing the Unified Modeling Language with Ivar Jacobson and James Rumbaugh in the 1990s.

IBM 1130

Booch got his first exposure to programming on an IBM 1130. [9]

... I pounded the doors at the local IBM sales office until a salesman took pity on me. After we chatted for a while, he handed me a Fortran [manual]. I'm sure he gave it to me thinking, "I'll never hear from this kid again." I returned the following week saying, "This is really cool. I've read the whole thing and have written a small program. Where can I find a computer?" The fellow, to my delight, found me programming time on an IBM 1130 on weekends and late-evening hours. That was my first programming experience, and I must thank that anonymous IBM salesman for launching my career. Thank you, IBM.

Booch method

Class diagram Booch-diagram.png
Class diagram

Booch developed the Booch method of software development, which he presents in his 1991/94 book, Object Oriented Analysis and Design With Applications. He advises adding more classes to simplify complex code. The Booch method is a technique used in software engineering. It is an object modeling language and methodology that was widely used in object-oriented analysis and design. It was developed by Booch while at Rational Software.

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).

Design patterns

Booch is also an advocate of design patterns. For instance, he wrote the foreword to Design Patterns , an early and highly influential book in the field.

IBM Research - Almaden

He now is part of IBM Research - Almaden, serving as Chief Scientist for Software Engineering, where he continues his work on the Handbook of Software Architecture and also leads several projects in software engineering that are beyond the constraints of immediate product horizons. Grady continues to engage with customers working on real problems and maintains deep relationships with academia and other research organizations around the world. Grady has served as architect and architectural mentor for numerous complex software-intensive systems around the world in just about every domain imaginable.


Grady Booch published several articles and books. A selection:

  • Software Engineering with Ada . [10]
  • Object Solutions: Managing the Object-Oriented Project. [11]
  • The Unified Software Development Process. With Ivar Jacobson and James Rumbaugh. [12]
  • The Complete UML Training Course. With James Rumbaugh and Ivar Jacobson. [13]
  • The Unified Modeling Language Reference Manual, Second Edition. With James Rumbaugh and Ivar Jacobson. [14]
  • The Unified Modeling Language User Guide, Second Edition. With James Rumbaugh and Ivar Jacobson. [15]
  • Object-Oriented Analysis and Design with Applications. [16]

Awards and honors

Booch at the IEEE Computer Society's first TechIgnite conference GradyBoochAtIEEETechIgnite2017.jpg
Booch at the IEEE Computer Society's first TechIgnite conference

In 1995 he was inducted as a Fellow of the Association for Computing Machinery. [17] He was named an IBM Fellow in 2003, soon after his entry into IBM, and assumed his current role on March 18, 2008. He was recognized as an IEEE Fellow in 2010. [18] In 2012, the British Computer Society announced Booch would receive the Lovelace Medal and give the 2013 Lovelace Lecture. [19] He gave the Turing Lecture in 2007. He was awarded the IEEE Computer Society Computer Pioneer award in 2016 for his pioneering work in Object Modeling that led to the creation of the Unified Modeling Language (UML). [20]

Related Research Articles

Booch method

The Booch method is a method for object-oriented software development. It is composed of an object modeling language, an iterative object-oriented development process, and a set of recommended practices.

Object-modeling language

An object-modeling language is a standardized set of symbols used to model a software system using an object-oriented framework. The symbols can be either informal or formal ranging from predefined graphical templates to formal object models defined by grammars and specifications.

Unified Modeling Language uchiha itachi

The Unified Modeling Language (UML) is a general-purpose, developmental, modeling language in the field of software engineering that is intended to provide a standard way to visualize the design of a system.

Object-oriented software engineering is an object-modeling language and methodology.

The Rational Unified Process (RUP) is an iterative software development process framework created by the Rational Software Corporation, a division of IBM since 2003. RUP is not a single concrete prescriptive process, but rather an adaptable process framework, intended to be tailored by the development organizations and software project teams that will select the elements of the process that are appropriate for their needs. RUP is a specific implementation of the Unified Process.

Software development is the process of conceiving, specifying, designing, programming, documenting, testing, and bug fixing involved in creating and maintaining applications, frameworks, or other software components. Software development is a process of writing and maintaining the source code, but in a broader sense, it includes all that is involved between the conception of the desired software through to the final manifestation of the software, sometimes in a planned and structured process. Therefore, software development may include research, new development, prototyping, modification, reuse, re-engineering, maintenance, or any other activities that result in software products.

Rational Machines was founded by Paul Levy and Mike Devlin in 1981 to provide tools to expand the use of modern software engineering practices, particularly explicit modular architecture and iterative development. It changed its name in 1994 to Rational Software, and was sold for US$2.1 billion to IBM on February 20, 2003.

The following outline is provided as an overview of and topical guide to software engineering:

Computer-aided software engineering type of software tools

Computer-aided software engineering (CASE) is the domain of software tools used to design and implement applications. CASE tools are similar to and were partly inspired by computer-aided design (CAD) tools used for designing hardware products. CASE tools are used for developing high-quality, defect-free, and maintainable software. CASE software is often associated with methods for the development of information systems together with automated tools that can be used in the software development process.

James E. Rumbaugh is an American computer scientist and object-oriented methodologist who is best known for his work in creating the Object Modeling Technique (OMT) and the Unified Modeling Language (UML).

Ivar Jacobson Swedish computer scientist

Ivar Hjalmar Jacobson is a Swedish-American computer scientist and software engineer, known as major contributor to UML, Objectory, Rational Unified Process (RUP), aspect-oriented software development and Essence.


A metamodel or surrogate model is a model of a model, and metamodeling is the process of generating such metamodels. Thus metamodeling or meta-modeling is the analysis, construction and development of the frames, rules, constraints, models and theories applicable and useful for modeling a predefined class of problems. As its name implies, this concept applies the notions of meta- and modeling in software engineering and systems engineering. Metamodels are of many types and have diverse applications.

The Shlaer–Mellor method, also known as Object-Oriented Systems Analysis (OOSA) or Object-Oriented Analysis (OOA) is an object-oriented software development methodology introduced by Sally Shlaer and Stephen Mellor in 1988. The method makes the documented analysis so precise that it is possible to implement the analysis model directly by translation to the target architecture, rather than by elaborating model changes through a series of more platform-specific models. In the new millennium the Shlaer–Mellor method has migrated to the UML notation, becoming Executable UML.

Object-oriented analysis and design (OOAD) is a technical approach for analyzing and designing an application, system, or business by applying object-oriented programming, as well as using visual modeling throughout the software development process to guide stakeholder communication and product quality.

UML Partners was a consortium of system integrators and vendors convened in 1996 to specify the Unified Modeling Language (UML). Initially the consortium was led by Grady Booch, Ivar Jacobson, and James Rumbaugh of Rational Software. The UML Partners' UML 1.0 specification draft was proposed to the Object Management Group (OMG) in January 1997. During the same month the UML Partners formed a Semantics Task Force, chaired by Cris Kobryn, to finalize the semantics of the specification and integrate it with other standardization efforts. The result of this work, UML 1.1, was submitted to the OMG in August 1997 and adopted by the OMG in November 1997.

Model-driven engineering (MDE) is a software development methodology that focuses on creating and exploiting domain models, which are conceptual models of all the topics related to a specific problem. Hence, it highlights and aims at abstract representations of the knowledge and activities that govern a particular application domain, rather than the computing concepts.

Rational Software Architect is a modeling and development environment that uses the Unified Modeling Language (UML) for designing architecture for C++ and Java EE (JEE) applications and web services. Rational Software Architect is built on the Eclipse open-source software framework and includes capabilities focused on architectural code analysis, C++, and model-driven development (MDD) with the UML for creating applications and web services.

RUP hump

A RUP ‘hump’ is a plot of effort spent over time during a particular Rational Unified Process (RUP) discipline. The RUP hump chart consists of a collection of humps for all RUP disciplines. This diagram was created in 1993 during a workshop on architecture and process and was inspired by work by Grady Booch and Boehm. It has been part of the Rational Objectory Process after reviews by Dyrhage and Bylund and moved on to play a more important role in the RUP in 1998 when it served as the initial page for using the digital version of the process. Its final form was published by Philippe Kruchten in 1998. An older version as later used by Jacobson, Booch and Rumbaugh and an altered version was used by Royce.

Information technology architecture is the process of development of methodical information technology specifications, models and guidelines, using a variety of Information Technology notations, for example UML, within a coherent Information Technology architecture framework, following formal and informal Information Technology solution, enterprise, and infrastructure architecture processes. These processes have been developed in the past few decades in response to the requirement for a coherent, consistent approach to delivery of information technology capabilities. They have been developed by information technology product vendors and independent consultancies, based on real experiences in the information technology marketplace and collaboration amongst industry stakeholders, for example the Open Group. Best practice Information Technology architecture encourages the use of open technology standards and global technology interoperability. Information Technology (I.T) Architecture can also be called a high-level map or plan of the information assets in an organization, including the physical design of the building that holds the hardware.

The Entity-Control-Boundary (ECB), or Entity-Boundary-Control (EBC), or Boundary-Control-Entity (BCE) is an architectural pattern used in use-case driven object-oriented software design that structures the classes composing a software according to their responsibilities in the use-case realization.


  1. "A podcast interview with Grady Booch on Software Engineering Radio".
  2. ""The Promise, The Limits, The Beauty of Software" talk at Yahoo!". Archived from the original on 2007-06-01.
  3. "There is joy in software. Podcast".
  4. "Grady Booch On Architecture podcast series". Archived from the original on 2018-08-03. Retrieved 2010-08-05.
  5. "Zen and the Art of Architecture: the Innovation Interview with Grady Booch Part 1".
  6. "Zen and the Art of Architecture: the Innovation Interview with Grady Booch Part 2".
  7. "Zen and the Art of Architecture: the Innovation Interview with Grady Booch Part 3".
  8. Swaine, Michael (2007-03-09). "Dr. Dobb's Excellence in Programming Award". Dr. Dobb's Journal.
  9. Booch, Grady (2003-04-03). "Quote from interview: Grady Booch polishes his crystal ball". IBM . Retrieved 2007-01-16.
  10. Benjamin/Cummings (1983) ISBN   0-8053-0604-8.
  11. Pearson Education (1995) ISBN   0-8053-0594-7.
  12. Prentice Hall (1999) ISBN   978-0-201-57169-1.
  13. Prentice Hall (2000) ISBN   0-13-087014-5.
  14. Addison-Wesley (2004) ISBN   978-0-321-24562-5.
  15. Addison-Wesley (2005) ISBN   978-0-321-26797-9.
  16. Addison-Wesley (2007) ISBN   0-201-89551-X.
  17. "ACM: Fellows Award / Grady Booch". Archived from the original on 2012-05-27. Retrieved 2013-03-19.
  18. "Fellow Class of 2010". IEEE. Archived from the original on 2013-05-16. Retrieved 2013-03-19.
  19. "Grady Booch presented with BCS Lovelace Medal". BCS. 29 May 2012. Retrieved 11 December 2013.
  20. "Grady Booch | IEEE Computer Society" . Retrieved 2019-06-06.