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

James McGovern, Scott W. Ambler and M. E Stevens (2004) A Practical Guide to Enterprise Architecture. p. 35

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 software architecture of a system or a family of systems has one of the most significant impacts on the quality of …" by Scott W. Ambler?

Scott W. Ambler2

Canadian software engineer/consultant/author 1966

Hans van Vliet (1949) Dutch computer scientist

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

“When software applications became larger and larger, people such as Shaw and Garlan coined the term software architecture. This notion of architecture deals with the key design principles underlying software artefacts. In the 1980s and 1990s, people became aware that the development of information technology (IT) should be done in conjunction with the development of the context in which it was used. This led to the identification of the so-called business/IT alignment problem. Solving the business/IT alignment problem requires enterprises to align human, organizational, informational, and technological aspects of systems. Quite early on, the term architecture was also introduced as a means to further alignment, and thus analyzes and solves business? IT alignment problems, Recently, the awareness emerged that alignment between business an IT is not enough, there are many more aspects in the enterprise in need of alignment. This has led to the use of the term architecture at the enterprise level: enterprise architecture.”

Erik Proper (1967) Dutch computer scientist

Martin Op 't Land, Erik Proper (2009) Enterprise Architecture: Creating Value by Informed Governance. p. 26-27

“Every software system needs to have a simple yet powerful organizational philosophy (think of it as the software equivalent of a sound bite that describes the system's architecture)… [A] step in [the] development process is to articulate this architectural framework, so that we might have a stable foundation upon which to evolve the system's function points.”

Grady Booch (1955) American software engineer

Source: Object-oriented design: With Applications, (1991), p. 320

“While it is becoming increasingly obvious that the fundamental architecture of a system has a profound Influence on the quality of its human factors, the vast majority of human factors studies concern the surface of hardware (keyboards, screens) or the very surface of the software”

Lewis M. Branscomb (1926) physicist and science policy advisor

command names, menu formats
L.M. Branscomb, J.C. Thomas (1984) "Ease of use: a system design challenge". in: IBM Systems Journal. Vol 23.3, Sept 1984. Pages 224-235

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

“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

“In computer design three levels can be distinguished: architecture, implementation and realisation; for the ﬁrst of them, the following working deﬁnition 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

“Enterprise architecture (EA) promotes the belief that an enterprise, as a complex system, can be designed or improved in an orderly fashion achieving better overall results than ad-hoc organisation and design. EA is a co-operative effort of designers, analysts and managers and uses enterprise models in the process… enterprise models carry meaning. This resulted in requirements for the enterprise engineering process, which—if not met—can limit the viability of the process. The analysis of the same factors resulted in requirements for improved Enterprise Modelling Tools.”

Peter Bernus (1949) Hungarian-Australian computer scientist

Peter Bernus (2003) "Enterprise models for enterprise architecture and ISO9000: 2000." Annual Reviews in Control 27.2 : 211-220.

“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

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

Gene Amdahl (1922–2015) American physicist

Gene Amdahl, Gerrit Blaauw, and Fred Brooks (1964) " Architecture of the IBM System http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.72.7974&rep=rep1&type=pdf." in: IBM Journal of Research and Development Vol 8 (2) p. 87-101

Help us to complete the source, original and additional information

Scott W. Ambler2

Related quotes

Related topics