“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

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

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 "Software engineering concerns methods and techniques to develop large software systems. The engineering metaphor is use…" by Hans van Vliet?

Hans van Vliet 5

Dutch computer scientist 1949

Bernhard Rumpe (1967) German computer scientist

Source: Executable Modeling with UML. A vision or a Nightmare (2002), p. 697

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

“This report summarizes the activities of the M. I. T. Computer-Aided Design (CAD) Project from 1 December 1959 through 3 May 1967 in the development of a generalized 'system of software systems' for generating specialized problem-solving systems using high-level language techniques and advanced computer graphics. Known as the AED Approach (for Automated Engineering Design) the Project results are applicable not only to mechanical design, as an extension of earlier development of the APT System for numerical control, but to arbitrary scientific, engineering, management, and production systems as well.”

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

D.T. Ross & John Erwin Ward (1968). Investigations in computer-aided design for numerically controlled production http://dspace.mit.edu/bitstream/handle/1721.1/755/FR-0351-19563962.pdf?sequence=1. Electronic Systems Laboratory, Electrical Engineering Dept., Massachusetts Institute of Technology. p. iii Abstract.

“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 signiﬁcantly 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

“A new concept and a new method were needed. The concept from the engineering standpoint is the evolution of the engineering scientist, i. e., the scientific generalist who maintains a broad outlook. The method is that of the team approach. On large-scale-system problems, teams of scientists and engineers, generalists as well as specialists, exert their joint efforts to find a solution and physically realize it.
We are led to the concept of the system-design team, a small group of engineers or scientists, to lead a large project and organize the system effort. Such men have been variously called engineering scientists, system engineers, system analysts, or large-scale-system designers. The technique has been variously called the systems approach or the team development method. It is toward this man and his teammates that these discussions are directed. With the realization that not enough can be learned in all the required fields to make him a specialist, enough is introduced to make him aware of the language and problems of the specialist. This generalist is a new quantity in the engineering world, and his education must be begun.”

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

Source: System Engineering (1957), p. 8

“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

“There are two fundamental ways of (re-)engineering information systems. The “formal driven” approach is based on the goal of developing and implementing a technical correct running system. The “content driven” approach is based on the goal of developing and implementing an organizational correct running system. By using reference models, content and technology can be combined in a new way”

August-Wilhelm Scheer (1941) German business theorist

Source: ARIS architecture and reference models for business process management (2000), p. 376.

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

“Throughout the software life cycle, there are many decision situations involving limited resources in which software engineering economics techniques provide useful assistance.”

Barry Boehm (1935) American software engineer

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

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

Help us to complete the source, original and additional information

Hans van Vliet 5

Related quotes

Related topics