“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

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

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 "Whereas object-oriented analysis typically focuses upon one specific problem at a time, domain analysis seeks to identi…" by Grady Booch?

Grady Booch 35

American software engineer 1955

Edward V. Berard

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

“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

“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 (1955) American software engineer

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

“[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.

“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

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

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

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

“Designed as a companion volume to the acclaimed Object-Oriented Analysis, this book focuses on the middle part of the software lifecycle: the activity of design. It shows readers how to apply object-oriented design, and how to tailor and expand the method to suit specific organization and project needs. Readers will explore the major issues in OOD; the role of OOD in the systems lifecycle; how to use graphical notation; strategies for creating design; and hints for evaluating the efficiency of a design created with OOD. For software engineers and other users undertaking real-world systems development projects and designing overall software architecture for systems will find this reference approach to improving systems design indispensable.”

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

Abstract.
Object-oriented design (1991)

“To us, analysis is the study of a problem domain, leading to a specification of externally observable behavior; a complete, consistent, and feasible statement of what is needed; a coverage of both functional and quantified operational characteristics”

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

e.g. reliability, availability, performance
Source: Object-oriented design (1991), p. 18.

“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.”

Help us to complete the source, original and additional information

Grady Booch 35

Related quotes

Related topics