“Object-oriented analysis is a method of analysis that examines requirements from the perspective of the classes and objects found in the vocabulary of the problem domain.”

—  Grady Booch

Source: Object-oriented design: With Applications, (1991), p. 37

Adopted from Wikiquote. Last update June 3, 2021. History

Help us to complete the source, original and additional information

Do you have more details about the quote "Object-oriented analysis is a method of analysis that examines requirements from the perspective of the classes and obj…" by Grady Booch?
Grady Booch photo
Grady Booch 35
American software engineer 1955

Related quotes

Grady Booch photo

“In object-oriented analysis, we seek to model the world by identifying the classes and objects that form the vocabulary of the problem domain, and in object-oriented design, we invent the abstractions and mechanisms that provide the behavior that this model requires.”

Grady Booch (1955) American software engineer

Source: Object-oriented design: With Applications, (1991), p. 141

Grady Booch photo

“Whereas object-oriented analysis typically focuses upon one specific problem at a time, domain analysis seeks to identify the classes and objects that are common to all applications within a given domain, such as missile avionics systems, compilers, or accounting software.”

Grady Booch (1955) American software engineer

Source: Object-oriented design: With Applications, (1991), p. 142

Ed Yourdon photo

“[Object-oriented analysis is] the challenge of understanding the problem domain and then the system's responsibilities in that light.”

Ed Yourdon (1944–2016) American software engineer and pioneer in the software engineering methodology

Source: Object-oriented design (1991), p. 8-9; as cited in: Elisa Bertino, ‎Susan Urban (1994) Object-Oriented Methodologies and Systems. p. 160.

“Object-oriented domain analysis seeks to identify reusable items localized around objects e. g., classes, instances, systems of interacting objects, and kits.”

Edward V. Berard

Source: Essays on object-oriented software engineering (1993), p. 185

“OOA - Object-Oriented Analysis - is based upon concepts that we first learned in kindergarten: objects and attributes, wholes and parts, classes and members.”

Peter Coad (1953) American software entrepreneur

Peter Coad & Ed Yourdon (1991, p. 1); cited in: Sten Carlsson and Benneth Christiansson. (1999) " The Concept of Object and its Relation to Human Thinking: Some Misunderstandings Concerning the Connection between Object-Orientation and Human Thinking http://www.vits.org/publikationer/dokument/289.pdf." Informatica, Lith. Acad. Sci. 10.2. p. 147-160.

Ed Yourdon photo

“OOA - Object-Oriented Analysis - is based upon concepts that we first learned in kindergarten: objects and attributes, wholes and parts, classes and members.”

Ed Yourdon (1944–2016) American software engineer and pioneer in the software engineering methodology

Source: Object-oriented design (1991), p. 1; cited in: Sten Carlsson and Benneth Christiansson. (1999) " The Concept of Object and its Relation to Human Thinking: Some Misunderstandings Concerning the Connection between Object-Orientation and Human Thinking http://www.vits.org/publikationer/dokument/289.pdf." Informatica, Lith. Acad. Sci. 10.2. p. 147-160.

“Object-oriented methods tend to focus on the lowest-level building block: the class and its objects.”

Peter Coad (1953) American software entrepreneur

Source: Object-oriented patterns. (1992), p. 152

Grady Booch photo

“In a quality object-oriented software system, you will find many classes that speak the language of the domain expert”

Grady Booch (1955) American software engineer

Source: Object Solutions: Managing the Object-Oriented Project. (1996), p. 39; as cited in: Journal of Database Management. Vol 10-11. p. 33

Ivar Jacobson photo

“The control objects model functionality that is not naturally tied to any other object… We do not believe that the best (most stable) systems are built by only using objects that correspond to real-life entities, something that many other object-oriented analysis and design techniques claim… Behavior that we place in control objects will, in other methods, be distributed over several other objects, making it hard to change this behavior.”

Ivar Jacobson (1939) Swedish computer scientist

Source: Object-Oriented Software Engineering: A Use Case Driven Approach (1992), p. 133 as cited in: " Object Oriented Software Engineering: A Use Case Driven Approach Ivar Jacobson, et al. (1992) http://tedfelix.com/software/jacobson1992.html", Book review by Ted Felix on tedfelix.com, 2006.

Ivar Jacobson photo

“The analysis model will not be a reflection of what the problem domain looks like… The reason is simply to get a more maintainable structure where changes will be local and thus manageable. We thus do not model reality as it is, as object orientation is often said to do, but we model the reality as we want to see it and to highlight what is important in our application.”

Ivar Jacobson (1939) Swedish computer scientist

Source: Object-Oriented Software Engineering: A Use Case Driven Approach (1992), p. 185: cited in: " Object Oriented Software Engineering: A Use Case Driven Approach Ivar Jacobson, et al. (1992) http://tedfelix.com/software/jacobson1992.html", Book review by Ted Felix on tedfelix.com, 2006.

Related topics