“The object-oriented paradigm is useful when building software systems where there is a hierarchy defined as a ranking or ordering of abstractions.”

—  Grady Booch

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

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 "The object-oriented paradigm is useful when building software systems where there is a hierarchy defined as a ranking o…" by Grady Booch?
Grady Booch photo
Grady Booch 35
American software engineer 1955

Related quotes

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

Alan Kay photo

“Possibly the only real object-oriented system in working order. (About Internet)”

Alan Kay (1940) computer scientist

2010 for Computerworld Australia http://www.computerworld.com.au/article/352182/z_programming_languages_smalltalk-80/
2010s

“Extreme Programming is the most prominent new, light-weight (or agile) methods, defined to contrast the current heavy-weight and partially overloaded object-oriented methods. It focuses on the core issues of software technology. One of its principles is not to rely on diagrams to document a system.”

Bernhard Rumpe (1967) German computer scientist

Source: Executable Modeling with UML. A vision or a Nightmare (2002), p. 697

Ed Yourdon photo

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

“Object-oriented programming increases the value of these metrics by managing this complexity. The most effective tool available for dealing with complexity is abstraction. Many types of abstraction can be used, but encapsulation is the main form of abstraction by which complexity is managed in object-oriented programming.
Programming in an object-oriented language, however, does not ensure that the complexity of an application will be well encapsulated. Applying good programming techniques can improve encapsulation, but the full benefit of object-oriented programming can be realized only if encapsulation is a recognized goal of the design process.”

Rebecca Wirfs-Brock (1953) American software engineer

Source: Object-oriented design: a responsibility-driven approach (1989), p. 71

“The software architecture of a system or a family of systems has one of the most significant impacts on the quality of an organization's enterprise architecture. While the design of software systems concentrates on satisfying the functional requirements for a system, the design of the software architecture for systems concentrates on the nonfunctional or quality requirements for systems. These quality requirements are concerns at the enterprise level. The better an organization specifies and characterizes the software architecture for its systems, the better it can characterize and manage its enterprise architecture. By explicitly defining the systems software architectures, an organization will be better able to reflect the priorities and trade-offs that are important to the organization in the software that it builds.”

Scott W. Ambler (1966) Canadian software engineer/consultant/author

James McGovern, Scott W. Ambler and M. E Stevens (2004) A Practical Guide to Enterprise Architecture. p. 35

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

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

Ervin László photo

“The systems view of nature and man is clearly non- anthropocentric, but it is not non-humanistic for all that. It allows us to understand that man is one species of system in a complex and embracing hierarchy of nature, and at the same time it tells us that all systems have value and intrinsic worth. They are goal-oriented, self-maintaining, and self-creating expressions of nature's penchant for order and adjustment. The status of man is not lessened by admitting the amoeba as his kin, nor by recognizing that sociocultural systems are his supersystems. Seeing himself as a connecting link in a complex natural hierarchy cancels man's anthropocentrism, but seeing the hierarchy itself as an expression of self-ordering and self-creating nature bolsters his self-esteem and encourages his humanism.”

Ervin László (1932) Hungarian musician and philosopher

Source: Introduction to Systems Philosophy (1972), p. 118.

“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

Related topics