“Systems with unknown behavioral properties require the implementation of iterations which are intrinsic to the design process but which are normally hidden from view. Certainly when a solution to a well-understood problem is synthesized, weak designs are mentally rejected by a competent designer in a matter of moments. On larger or more complicated efforts, alternative designs must be explicitly and iteratively implemented. The designers perhaps out of vanity, often are at pains to hide the many versions which were abandoned and if absolute failure occurs, of course one hears nothing. Thus the topic of design iteration is rarely discussed. Perhaps we should not be surprised to see this phenomenon with software, for it is a rare author indeed who publicizes the amount of editing or the number of drafts he took to produce a manuscript.”

—  Fernando J. Corbató

"A Managerial View of the Multics System Development" http://www.multicians.org/managerial.html, Conference on Research Directions in Software Technology, Providence, Rhode Island, October 10-12, 1977 published in Research Directions in Software Technology (1978), P. Wegner (ed.), MIT Press, ISBN 0262230968, pp. 139-158. Also reprinted in Tutorial: Software Management, Donald J. Reifer (ed.), IEEE Computer Society Press, (1979, 1981, 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 "Systems with unknown behavioral properties require the implementation of iterations which are intrinsic to the design p…" by Fernando J. Corbató?
Fernando J. Corbató photo
Fernando J. Corbató 11
American computer scientist 1926–2019

Related quotes

“Experienced object designers explore the design space from many different angles. They refine ideas of how their system should respond while they are in the middle of building and discarding ideas about how their design should work. Getting a design to gel involves making assumptions, seeing how they play out, changing one’s mind or perspective slightly and re-iterating. Design is a difficult, involved task. It inherently is a non-linear process. Yet, we are asked to trace our design results back to system requirements. And, if we uncover some implications during design, we’d like to tune our system requirements to reflect necessary design compromises.”

Rebecca Wirfs-Brock (1953) American software engineer

Abstract
Designing scenarios: Making the case for a use case framework (1993)

Paul Graham photo

“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

“Responsibility-driven design specifies object behavior before object structure and other implementation considerations are determined. We have found that it minimizes the rework required for major design changes.”

Rebecca Wirfs-Brock (1953) American software engineer

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

Jef Raskin photo

“Once the product's task is known, design the interface first; then implement to the interface design.”

Jef Raskin book The Humane Interface

The Humane Interface (2001)

A. Wayne Wymore photo

“The problem of the design of a system must be stated strictly in terms of its requirements, not in terms of a solution or a class of solutions.”

A. Wayne Wymore (1927–2011) American mathematician

A Wayne. Wymore (2004) " The nature of research in systems engineering http://sse.stevens.edu/fileadmin/cser/2004/papers/211-Paper119.pdf"; As cited in: Eric David Smith (2006) Tradeoff Studies and Cognitive Biases. p. 31.

“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

“The objective of the Computer-Aided Design Project is to evolve a machine systems which will permit the human designer and the computer to work together on creative design problems.”

Douglas T. Ross (1929–2007) American computer scientist

Source: Computer-Aided Design: A Statement of Objectives (1960), p. iii: Abstract.

“Computer-aided design is not automatic design, although it must include many automatic design features. By automatic design we mean design procedures which are capable of being completely specified in a form which a computer can execute without human intervention.”

Douglas T. Ross (1929–2007) American computer scientist

Source: Computer-Aided Design: A Statement of Objectives (1960), p. 2.

Béla H. Bánáthy photo

“If solutions could be offered within the existing system, there would be no need to design. Thus designers have to transcend the existing system. Their task is to create a different system or devise a new one. That is why designers say they can truly define the problem only in light of the solution. The solution informs them as to what the real problem is.”

Béla H. Bánáthy (1919–2003) Hungarian linguist and systems scientist

Source: Systems Design of Education (1991), p. 20

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

Related topics