“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, configure, 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 specification does not define 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

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

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 Unified Modeling Language (UML) is a general-purpose visual modeling language that is used to specify, visualize, co…" by Ivar Jacobson?
Ivar Jacobson photo
Ivar Jacobson 6
Swedish computer scientist 1939

Related quotes

Grady Booch photo

“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, configure, 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 specification does not define 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 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, configure, 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 specification does not define 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

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

Martin Fowler photo

“The second problem [with using UML for the purposes of this book] is that the Unified Modeling Language concentrates on implementation modeling rather than conceptual modeling”

Martin Fowler (1963) British programmer

Source: Analysis Patterns: Reusable Object Models, 1997, p. 314

“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

“One of the distinct features of XP is the lack of any documentation whatsoever, except for the code itself. This is a contraposition to the modeling techniques like the Unified Modeling Language (UML), which strongly focus on documentation. XP takes an extreme position there, not even documenting the architecture of the system. Often, it is very difficult to extract the overall structure, behavior or interactions with the environment from the code. The code is a rather detailed and fragile representation of the system’s tasks. Even though the code contains all necessary information about the system, this information is often burdened with details and it is tedious to extract the aspects one is interested in. Therefore, it would be useful to have a more compact system representation. The UML does provide a number of notations that are suited for this purpose. However, the tools so far are not capable of supporting UML in such a manner that it can be well-integrated with the approach of Extreme Programming.”

Bernhard Rumpe (1967) German computer scientist

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

“What's the point of having metamodels, and why should you care? Because models must be stated in a way that yields a common understanding among all involved parties, we need a way to specify exactly what a model means. Metamodels allow you to do just that: They specify the concepts of the language you're using to specify a model.”

Stephen J. Mellor (1952) British computer scientist

Source: MDA Distilled. Principles of Model-Driven Architecture, 2003, p. 37.

“Models are used essentially for evaluation and prediction purposes as well as for the analysis and study of the different parts of the system so that the systems engineer or designer may arrive at sound engineering decisions regarding the system design.”

Harold Chestnut (1917–2001) American engineer

Source: Systems Engineering Tools, (1965), p. 113; As cited in: Alberto Ortiz (1992, p. 12-13)

Russell L. Ackoff photo

“The effectiveness of any model used to describe and understand behavior of a particular system as a whole ultimately depends on the degree to which that model accurately represents that system. Nevertheless, there have been and are situations in which application of deterministic or animate models to social systems have produced useful results for a short period of time. However, in a longer run, such mismatches usually result in less than desirable results because critical aspects of the social systems were omitted in the less complex model that was used.”

Russell L. Ackoff (1919–2009) Scientist

Ackoff (1999, p. 34) cited in: Michael C. Jackson (2000) Systems Approaches to Management. p. 234.
1990s

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

Related topics