Authors:
  1. Quotes
  2. Authors
  3. F
  4. Fred Brooks
  5. Design

Fred Brooks Quotes about Design

All Fred Brooks Quotes Design quotes Effort Learning Management
Design work doesn't just satisfy requirements, it elicits them.

Design work doesn't just satisfy requirements, it elicits them.

Fred Brooks
Design Work, Design, Requirements

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
Believe, Essence, Design
"No Silver Bullet – Essence and Accident in Software Engineering". Paper by Fred Brooks, 1986.

Improving your process won't move you from good to great design. It'll move you from bad to average.

Fred Brooks
Moving, Average, Design

Consensus processes starve innovative design by eating the resource.

Fred Brooks
Design, Eating, Process

Conceptual integrity is the most important consideration in system design.

Fred Brooks
Integrity, Design, Important

Mediocre design provably wastes the world's resources, corrupts the environment, affects international competitiveness. Design is important.

Fred Brooks
Design, Important, World

Predictability and great design are not friends.

Fred Brooks
Design, Not Friends, Great Design

A little retrospection shows that although many fine, useful software systems have been designed by committees and built as part of multipart projects, those software systems that have excited passionate fans are those that are the products of one or a few designing minds, great designers.

Fred Brooks
Design, Mind, Fans
"No Silver Bullet – Essence and Accident in Software Engineering". Paper by Fred Brooks, 1986.

Software and hardware design is less different than software designers think, but more different than hardware designers think.

Fred Brooks
Thinking, Design, Different

A design style is defined by a set of microdecisions. A clear style reflects a consistent set. A clear style may not be a good style; a muddled one never is.

Fred Brooks
Design, Style, May

The term architecture is used here to describe the attributes of a system as seen by the programmer, i.e., the conceptual structure and functional behavior, as distinct from the organization of the data flow and controls, the logical design, and the physical implementation. i. Additional details concerning the architecture

Fred Brooks
Data, Organization, Design
"Architecture of the IBM System". IBM Journal of Research and Development, Volume 8, 1964.

You May Also Like: