“There are four distinct bases on which a system-design book might be organized. First are the chronological phases through which the system-design effort passes, such as organization and preliminary design. Second are the logical steps such as analysis of the single thread (operation on a single input) and high traffic (methods of handling multiplex inputs). Third are the parts of the system, such as communications and displays. Fourth are the tools of system design, such as information theory and queueing theory.”

—  Robert E. Machol

Source: System Engineering (1957), p. 8

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 "There are four distinct bases on which a system-design book might be organized. First are the chronological phases thro…" by Robert E. Machol?
Robert E. Machol photo
Robert E. Machol 24
American systems engineer 1917–1998

Related quotes

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)

Fred Brooks photo

“… the organization chart will initially reflect the first system design, which is almost surely not the right one [… ] as one learns, he changes the design [… ]. Management structures also need to be changed as the system changes…”

Fred Brooks (1931) American computer scientist

The Mythical Man-Month: Essays on Software Engineering (1975, 1995)

“The basic functional elements of any automatic control system: sensing, converting, storing, communicating, computing, programming, regulating, actuating, and display (Chestnut, 1967). Many kinds of systems in being, speculated about, or even intuited, ranging from computers, most factory processes, communication systems, road networks, automatic farms, etc., have structures which can be invoked as zero-order matches to proposed sets of throughputs, especially for single- thread designs. This method of structuring is related closely to analogical design, of which a special form is called synectics.”

Arthur D. Hall (1925–2006) American electrical engineer

Source: Metasystems Methodology, (1989), p. 191

“Models are used essentially for evaluation and prediction purposes as well as for the analysis and study of the different parts of the system so that the systems engineer or designer may arrive at sound engineering decisions regarding the system design.”

Harold Chestnut (1917–2001) American engineer

Source: Systems Engineering Tools, (1965), p. 113; As cited in: Alberto Ortiz (1992, p. 12-13)

“Every large-scale system is an information system. The automatic factory, the vehicular-traffic system, any military system- in the design of all these systems, primary attention should be given to the flow of information about the elements of the system.”

Robert E. Machol (1917–1998) American systems engineer

Source: System Engineering (1957), p. 316

“Formulating consists of determining the system inputs, outputs, requirements, objectives, constraints. Structuring the system provides one or more methods of organizing the solution, the method of operation, the selection of parts, and the nature of their performance requirements. It is evident that the processes of formulating a system and structuring it are strongly related.”

Harold Chestnut (1917–2001) American engineer

Source: Systems Engineering Tools, (1965), Systems Engineering Methods (1967), p. 70

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

“Within the past ten years there have appeared with increasing frequency books, articles, conferences, and monograms dealing with system engineering, system analysis, system design, the systems approach, the design of systems, system theory, and problems of systems engineering. The number of publications and the stature of their authors does not allow the dismissal of the subject as a passing fad. The breadth of engineering activity involved in even a cursory examination of recent publications is of interest… It is therefore obvious that whatever Systems Engineering may or may not be, it is non-sectarian and encompasses activities that are of concern in all phases of engineering. On the other hand undergraduate college offerings akin to Systems Engineering are rather limited and even graduate programs are not extensive.”

Allen B. Rosenstein (1920–2018) American systems engineers

Source: Systems engineering and Modern Engineering Design (1965), p. 1.

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

“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

Related topics