“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

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

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 "When software applications became larger and larger, people such as Shaw and Garlan coined the term software architectu…" by Erik Proper?
Erik Proper photo
Erik Proper 3
Dutch computer scientist 1967

Related quotes

“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

Grady Booch photo

“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

Barry Boehm photo

“Economic principles underlie the overall structure of the software lifecycle, and its primary refinements of prototyping, incremental development, and advancemanship. The primary economic driver of the life-cycle structure is the significantly increasing cost of making a software change or fixing a software problem, as a function of the phase in which the change or fix is made.”

Barry Boehm (1935) American software engineer

Source: Software engineering economics. (1984), p. 4

“The growing complexity of software is the motivation behind work on industrializing software development. In particular, current research in the area of model driven engineering (MDE) is primarily concerned with reducing the gap between problem and software implementation domains through the use of technologies that support systematic transformation of problem-level abstractions to software implementations. The complexity of bridging the gap is tackled through the use of models that describe complex systems at multiple levels of abstraction and from a variety of perspectives, and through automated support for transforming and analyzing models. In the MDE vision of software development, models are the primary artifacts of development and developers rely on computer-based technologies to transform models to running systems.”

Bernhard Rumpe (1967) German computer scientist

Source: Model-driven development of complex software: A research roadmap (2007), p. 37

Grady Booch photo

“The amateur software engineer is always in search of magic, some sensational method or tool whose application promises to render software development trivial. It is the mark of the professional software engineer to know that no such panacea exist.”

Grady Booch (1955) American software engineer

Grady Booch, ‎Robert A. Maksimchuk, ‎Michael W. Engle (2007) Object-Oriented Analysis and Design with Applications Chapter 6.

“The term Model-Driven Engineering (MDE) is typically used to describe software development approaches in which abstract models of software systems are created and systematically transformed to concrete implementations…. Full realizations of the MDE vision may not be possible in the near to medium-term primarily because of the wicked problems involved. On the other hand, attempting to realize the vision will provide insights that can be used to significantly reduce the gap between evolving software complexity and the technologies used to manage complexity.”

Bernhard Rumpe (1967) German computer scientist

Source: Model-driven development of complex software: A research roadmap (2007), p. 37: Abstract

“IT architecture is often assumed to follow business strategy, to align IT with the business's strategic objectives. Increasingly, though, many business strategies depend on specific underlying IT capabilities. To develop a synergy between business strategy and IT architecture, firms must develop organizational competencies in IT architecture. My research has identified four IT architectural stages, each with its own requisite competencies. The "application silo architecture stage" consists of IT architectures of individual applications. The "standardized technology architecture stage" has an enterprise-wide IT architecture that provides efficiencies through technology standardization. The "rationalized data architecture stage" extends the enterprise-wide IT standards to data and processes. And the "modular architecture stage" builds onto enterprise-wide global standards with loosely coupled IT components to preserve the global standards while enabling local differences. Each stage demands different organizational competencies to implement the architecture and prepare the firm to move to the next stage.”

Jeanne W. Ross (1958) American computer scientist

Jeanne W. Ross (2003) Creating a Strategic IT Architecture Competency: Learning in Stages. MIT Sloan Working Paper No. 4314-03, April 2003. Abstract

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)

“Software engineering concerns methods and techniques to develop large software systems. The engineering metaphor is used to emphasize a systematic approach to develop systems that satisfy organizational requirements and constraints.”

Hans van Vliet (1949) Dutch computer scientist

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

Richard Stallman photo

“The term "free software" has an ambiguity problem: an unintended meaning, "Software you can get for zero price," fits the term just as well as the intended meaning, "software which gives the user certain freedoms."”

Richard Stallman (1953) American software freedom activist, short story writer and computer programmer, founder of the GNU project

We address this problem by publishing a more precise definition of free software, but this is not a perfect solution; it cannot completely eliminate the problem. An unambiguously correct term would be better, if it didn't have other problems.
1990s, Why "Free Software" is better than "Open Source" (1998)

Related topics