“Structured design does not scale up well for extremely complex systems, and this method is largely inappropriate for use with object-based and object-oriented programming languages.”

—  Grady Booch

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

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 "Structured design does not scale up well for extremely complex systems, and this method is largely inappropriate for us…" by Grady Booch?
Grady Booch photo
Grady Booch35
American software engineer 1955

Related quotes

“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

Grady Booch photo

“Object-oriented design is a method of design encompassing the process of object-oriented decomposition and a notation for depicting both logical and physical as well as static and dynamic models of the system under design.”

Grady Booch (1955) American software engineer

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

“If there is ever a science of programming language design, it will probably consist largely of matching languages to the design methods they support.”

Robert Floyd (1936–2001) American computer scientist

The Paradigms of Programming (1979)

“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

“Like structured design, the term object-oriented design (OOD) means different things to different people. For example, OOD has been used to imply such things as”

Edward V. Berard

The design of individual objects, and/or the design of the individual methods contained in those objects
The design of an inheritance (specialization) hierarchy of objects
The design of a library of reusable objects
The process of specifying and coding of an entire object-oriented application
The term nonformal is used to describe approaches to OOD that are not well defined, step-by-step, or repeatable, such as those that emphasize the design of individual objects, specialization (inheritance) hierarchies, and libraries of objects...
Abstract
Object‐Oriented Design (2002)

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.

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)

“In order to better understand object-oriented methodologies in general, it helps to understand the people who make up the "object-oriented community" itself. Far from being monolithic, there is a great deal of diversity within this community. Many object-oriented people, for example, seem to focus almost entirely on programming language issues. They tend to cast all discussions in terms of the syntax and semantics of their chosen object-oriented programming language. These people find it impossible (for all intents and purposes) to discuss any software engineering activity (e. g., analysis, design, and testing) without direct mention of some specific implementation language.
Outside of producing executable "prototypes", people who emphasize programming languages seldom have well-defined techniques for analyzing their clients' problems or describing the overall architecture of the software product. A great deal of what they do is intuitive. If they happen to have a natural instinct/intuition for good analysis or good design, their efforts on small-to-medium, non-critical projects can result in respectable software solutions.”

Edward V. Berard

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

“Object-oriented programming languages support encapsulation, thereby improving the ability of software to be reused, refined, tested, maintained, and extended. The full benefit of this support can only be realized if encapsulation is maximized during the design process.
We argue that design practices which take a data-driven approach fail to maximize encapsulation because they focus too quickly on the implementation of objects. We propose an alternative object-oriented design method which takes a responsibility-driven approach. We show how such an approach can increase the encapsulation by deferring implementation issues until a later stage.”

Rebecca Wirfs-Brock (1953) American software engineer

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

“Recently, I have had conversations with a number of people who were attempting their first object-oriented project. Most of these people claimed to be using “use cases” in their object-oriented analysis and design approaches. However, listening to them describe their projects, it became quite apparent to me that there is a great deal of confusion regarding the definition, context, and use of use cases. This confusion can (and often does) lead to poorly-designed systems.”

Edward V. Berard

Edward V. Berard (1996) " Be Careful With" Use Cases http://www.tao.com/pub/html/use_case.html" The Object Agency, Inc.

Related topics