Barry Boehm quote: “The stagewise and waterfall models. As early as 1956, experience on large software systems such as the Semi-Automated G…”

Barry Boehm (1935) American software engineer

As early as 1956, experience on large software systems such as the Semi-Automated Ground Environment (SAGE) had led to the recognition of these problems and to the development of a stagewise model to address them.
Source: A spiral model of software development and enhancement. (1988), p. 63

“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

“Model Driven Architecture is a style of enterprise application development and integration, based on using automated tools to build system independent models and transform them into efficient implementations.”

Grady Booch (1955) American software engineer

Attributed to Grady Booch in: Tarek M. Sobh (2008) Advances in Computer and Information Sciences and Engineering. p. 457

“Information engineering has been defined with the reference to automated techniques as follows: An interlocking set of automated techniques in which enterprise models, data models and process models are built up in a comprehensive knowledge-base and are used to create and maintain data-processing systems.”

James Martin (author) (1933–2013) British information technology consultant and writer

Source: Information Engineering (1989), p. viii

“Creating a modeling language that is also an executable language has long been a goal of the software community. Many years ago, in 1968 to be exact, while working with software components to successfully develop a telecommunications system, we created a modeling language that was the forerunner to UML. To model components we used sequence diagrams, collaboration diagrams, and state transition diagrams (a combination of state charts and activity diagrams). Our modeling language then seamlessly translated the component models into code. Each code component was in its turn compiled into an executable component that was deployed in our computer system. The computer system was a component management system—thus we had "components all the way down."”

Stephen J. Mellor (1952) British computer scientist

Source: Executable Uml: A Foundation for Model-Driven Architecture, 2002, p. xxiii: Foreword.

“The Unified Modeling Language (UML) is a general-purpose visual modeling language that is used to specify, visualize, construct, and document the artifacts of a software system. It captures decisions and understanding about systems that must be constructed. It is used to understand, design, browse, conﬁgure, maintain, and control information about such systems. It is intended for use with all development methods, lifecycle stages, application domains, and media. The modeling language is intended to unify past experience about modeling techniques and to incorporate current software best practices into a standard approach. UML includes semantic concepts, notation, and guidelines. It has static, dynamic, environmental, and organizational parts. It is intended to be supported by interactive visual modeling tools that have code generators and report writers. The UML speciﬁcation does not deﬁne a standard process but is intended to be useful with an iterative development process. It is intended to support most existing object-oriented development processes.”

James Rumbaugh (1947) Computer scientist, software engineer

James Rumbaugh, Ivar Jacobson & Grady Booch (1998) The Unified Modeling Language Reference Manual. p. 1

“The Uniﬁed Modeling Language (UML) is a general-purpose visual modeling language that is used to specify, visualize, construct, and document the artifacts of a software system. It captures decisions and understanding about systems that must be constructed. It is used to understand, design, browse, conﬁgure, maintain, and control information about such systems. It is intended for use with all development methods, lifecycle stages, application domains, and media. The modeling language is intended to unify past experience about modeling techniques and to incorporate current software best practices into a standard approach. UML includes semantic concepts, notation, and guidelines. It has static, dynamic, environmental, and organizational parts. It is intended to be supported by interactive visual modeling tools that have code generators and report writers. The UML speciﬁcation does not deﬁne a standard process but is intended to be useful with an iterative development process. It is intended to support most existing object-oriented development processes.”

Grady Booch (1955) American software engineer

James Rumbaugh, Ivar Jacobson, & Booch (1999) The Unified Modeling Language Reference Manual. p. 1

“The Uniﬁed Modeling Language (UML) is a general-purpose visual modeling language that is used to specify, visualize, construct, and document the artifacts of a software system. It captures decisions and understanding about systems that must be constructed. It is used to understand, design, browse, conﬁgure, maintain, and control information about such systems. It is intended for use with all development methods, lifecycle stages, application domains, and media. The modeling language is intended to unify past experience about modeling techniques and to incorporate current software best practices into a standard approach. UML includes semantic concepts, notation, and guidelines. It has static, dynamic, environmental, and organizational parts. It is intended to be supported by interactive visual modeling tools that have code generators and report writers. The UML speciﬁcation does not deﬁne a standard process but is intended to be useful with an iterative development process. It is intended to support most existing object-oriented development processes.”

Ivar Jacobson (1939) Swedish computer scientist

James Rumbaugh, Ivar Jacobson, & Grady Booch (1999) The Unified Modeling Language Reference Manual. p. 1.

“To explain their occult and mystical experiences, magicians are forced to develop models beyond the scope of materialistic or religious systems.”

Peter J. Carroll (1953) British occultist

Source: Liber Null & Psychonaut (1987), p. 151
Context: Physical processes alone will never completely explain the existence of the universe, life, and consciousness. Religious answers are just wishful thinking and wanton fabrication cast over a bottomless pit of ignorance. To explain their occult and mystical experiences, magicians are forced to develop models beyond the scope of materialistic or religious systems.

“In all engineering disciplines nowadays, software engineering excluded, there exists an established engineering process to develop a system, which is accompanied by a number of suited modeling description techniques. Software engineering, being a rather new field, has not as yet established any clear methodical guidance or a fully standardized modeling notation.”

Bernhard Rumpe (1967) German computer scientist

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

“The stagewise and waterfall models. As early as 1956, experience on large software systems such as the Semi-Automated Ground Environment (SAGE) had led to the recognition of these problems and to the development of a stagewise model to address them.”

Help us to complete the source, original and additional information

Barry Boehm 18

Related quotes

Related topics