“Architecture is defined as the art and science of creating buildings. Systems engineering may be similarly defined as the art and science of creating systems.”

—  Derek Hitchins

Source: Advanced Systems Thinking, Engineering and Management (2003), p. 309; partly cited in: Kurt A. Richardson, Wendy J. Gregory, Gerald Midgley (2006) Systems Thinking and Complexity Science. p. 39

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 "Architecture is defined as the art and science of creating buildings. Systems engineering may be similarly defined as t…" by Derek Hitchins?
Derek Hitchins photo
Derek Hitchins 14
British systems engineer 1935

Related quotes

“System engineering is the art and science of creating effective systems, using whole system, whole life principles.”

Derek Hitchins (1935) British systems engineer

Derek Hitchins (1995) cited in: Herbert Negele (2000) Systems engineering--a key to competitive advantage for all industries. p,166

Gerrit Blaauw photo

“The architecture of a system can be defined as the functional appearance of the system to the user.”

Gerrit Blaauw (1924–2018) Dutch computer scientist

Blaauw (1972) cited in: Gerritt A Blaauw (1976) Digital system implementation. p. 6

“Enterprise engineering is rooted in both the organizational sciences and the information system sciences. In our current understanding, three concepts are paramount to the theoretical and practical pursuit of enterprise engineering: enterprise ontology, enterprise architecture, and enterprise governance.”

Erik Proper (1967) Dutch computer scientist

Preface
Advances in Enterprise Engineering II (2009)

“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

“Professionalism has no place in art, and hacking is art. Software Engineering might be science; but that's not what I do. I'm a hacker, not an engineer.”

Jamie Zawinski (1968) American programmer

http://phd.pp.ru/Texts/fun/signatures.txt
PP
RU
Texts
Signatures.

“Everyone knows what engineering is. All that's left is to define systems, and I'm not fool enough to do that.”

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

Source: Mathematicians are useful (1971), p. 1: Machol explains his definition of systems engineering.

Bran Ferren photo

“Art and design are not luxuries, nor somehow incompatible with science and engineering.”

Bran Ferren (1953) American technologist

To create for the ages, let's combine art and engineering, Bran, Ferren, January 23, 2018, www.ted.com, March 2014 https://www.ted.com/talks/bran_ferren_to_create_for_the_ages_let_s_combine_art_and_engineering,

“With increasing size and complexity of the implementations of information systems, it is necessary to use some logical construct (or architecture) for defining and controlling the interfaces and the integration of all of the components of the system.”

John Zachman (1934) American computer scientist

Source: A Framework for Information Systems Architecture, 1987, p. 276, cited in: CM Pereira (2004), "A method to define an Enterprise Architecture using the Zachman Framework". in: SAC '04 Proceedings of the 2004 ACM symposium on Applied computing. pp. 1366-1371

Russell L. Ackoff photo

“Doing philosophy was an opportunity to learn something new. I expected this to be an adjunct to my practice of architecture. But it turned out the other way. It turned out that the philosophy of science gave me the opportunity to design social systems, and I was more interested in people-oriented systems than in buildings. They were both design, but different kinds of design. I like creating things.”

Russell L. Ackoff (1919–2009) Scientist

Ackoff cited in: Carole Novak (2000) " Interview with Russell L. Ackoff http://www.ait.net/technos/tq_09/3ackoff.php". in: Technos Quartely. Fall 2000 Vol. 9 No. 3. This quote is the answer to the question, why Ackoff switched from architecture to philosophy in his graduate studies.
2000s

Gerrit Blaauw photo

“In computer design three levels can be distinguished: architecture, implementation and realisation; for the first of them, the following working definition is given: The architecture of a system can be defined as the functional appearance of the system to the user, its phenomenology.”

Gerrit Blaauw (1924–2018) Dutch computer scientist

Although the term architecture was introduced only ten years ago in computer technology (Buchholz), the concept of architecture is as old as the use of mechanism by man. When a child is taught to look at a clock, it is taught the architecture of the clock. It is told to observe the position of the short and the long hand and to relate these to the hours and the minutes. Once it can distinguish the architecture from the visual appearance, it can tell time as easily from a wrist watch as from the clock on the church tower.
The inner structure of a system is not considered by the architecture: we do not need to know what makes the clock tick, to know what time it is. This inner structure, considered from a logical point of view, will be called the implementation, and its physical embodiment the realisation.
Source: Computer architecture (1972), p. 154

Related topics