“The essence of a software entity is a construct of interlocking concepts: [… ] I believe the hard part of building software to be the specification, design, and testing of this conceptual construct, not the labor of representing it and testing the fidelity of the representation.”

— Fred Brooks , No Silver Bullet

Page 182 (italics in source).
No Silver Bullet (1986)

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 essence of a software entity is a construct of interlocking concepts: [… ] I believe the hard part of building soft…" by Fred Brooks?

Fred Brooks 20

American computer scientist 1931

Related quotes

“The complexity of software is an essential property, not an accidental one. Hence, descriptions of a software entity that abstract away its complexity often abstracts away its essence.”

Fred Brooks No Silver Bullet

Page 183.
No Silver Bullet (1986)

“Almost 2000 years ago, the Roman architect Vitruvius recorded what makes a design good: durability (firmitas), utility (utilitas), and charm (venustas). These quality requirements still hold, for buildings as well as software systems. A well-designed system is easy to implement, is understandable and reliable, and allows for smooth evolution. Badly-designed systems may work at first, but they are hard to maintain, difficult to test, and unreliable.”

Hans van Vliet (1949) Dutch computer scientist

Source: Software Engineering: Principles and Practice, 2007, p. 279

“Software has to be designed by hackers who understand design, not designers who know a little about software. If you can't design software as well as implement it, don't start a startup.”

Paul Graham (1964) English programmer, venture capitalist, and essayist

"The Other Road Ahead" http://www.paulgraham.com/road.html, September 2001

“A subsystem is a set of classes (and possibly other subsystems) collaborating to fulfill a set of responsibilities. Although subsystems do not exist as the software executes, they are useful conceptual entities.”

Rebecca Wirfs-Brock (1953) American software engineer

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

“There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult.”

C. A. R. Hoare (1934) British computer scientist

The Emperor's Old Clothes
Context: There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult. It demands the same skill, devotion, insight, and even inspiration as the discovery of the simple physical laws which underlie the complex phenomena of nature.

“Objects are the real and conceptual things we find in the world around us. An object may be hardware, software, a concept (e. g., velocity), or even "flesh and blood." Objects are complete entities, i. e., they are not "simply information" or "simply information and actions." Software objects strive to capture as completely as possible the characteristics of the "real world" objects which they represent. Finally, objects are "black boxes," i. e., their internal implementations are hidden from the outside world, and all interactions with an object take place via a well-defined interface.”

Edward V. Berard

Source: Essays on object-oriented software engineering (1993), p. 335; as cited in Edward V. Berard (1995) " A Comparison of Object-Oriented Development Methodologies http://www.ipipan.gda.pl/~marek/objects/TOA/OOMethod/mcr.html". The Object Agency, Inc.