Grady Booch quote: “The adoption of the Precise Action Semantics for the Unified Modeling Language specification by the OMG in November of …”

“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

“In its current form UML is designed to support a wide variety of different modelling techniques and formalisms. This is evident, for example, in the state machine formalism which allows both Moore and Mealy formalism with hierarchical states including concurrent sub-states and both synchronous and asynchronous calling semantics. The result of this is not only that almost any state modelling style can be supported but also that many combinations of elements have no defined execution semantics. It is now widely recognised within the UML community, however, that considerable benefit can be gained by forming subsets of the UML with well defined execution semantics. Such subsets can form an “executable UML” which would enable the simulation, execution, testing and ultimately translation of UML models into target code. As part of this movement, work is progressing under the auspices of the OMG towards the definition of “profiles” that define such subsets and towards the more detailed definition of the contents of “actions” including a more precise definition of the execution semantics of UML models.”

Stephen J. Mellor (1952) British computer scientist

Mellor and Ian Wilkie (1999). A mapping from Shlaer-Mellor to UML http://www.ooatool.com/docs/SMUML99.pdf. Technical report, Projtech Inc. and Kennedy Carter Limited, 1999.

“I was astonished to be invited to what became the meeting that originated the Agile Manifesto because my work had always been based around building models… The other signatories were kind enough, back in 2001, to write the manifesto using the word “software” (which can include executable models), not “code” (which is more specific.) As such I felt able, in good conscience, to become a signatory to the Manifesto while continuing to promote executable modeling. Ten years on we have a standard action language for agile modeling.”

Stephen J. Mellor (1952) British computer scientist

Mellor (2011) " A Personal Reflection on Agile Ten Years On http://www.infoq.com/articles/personal-reflection-agile-ten-years-mellor" in: InfoQ, Feb 11, 2011.

“Conceptual graphs are system of logic based on the existential graphs of Charles Sanders Peirce and the semantic networks of artificial intelligence. The purpose of the system is to express meaning in a form that is logically precise, humanly readable, and computationally tractable. With their direct mapping to language, conceptual graphs can serve as an intermediate language for translating computer-oriented formalisms to and from natural languages. With their graphic representation, they can serve as a readable, but design and specification language.”

John F. Sowa (1940) artificial intelligence researcher

Source: Conceptual graphs for knowledge representation, 1993, p. 3-51. cited in: Bernhard Ganter, Gerd Stumme, Rudolf Wille (2005) Formal Concept Analysis: Foundations and Applications. p. 87

“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

“In the interest of scientific work, more and more formulations in the unified language of unified science are becoming increasingly precise. No term of unified science, however, is free from imprecision, since all terms are based on terms that are essential for protocol statements, whose imprecision must be immediately obvious to everyone.”

Otto Neurath (1882–1945) austrian economist, philosopher and sociologist

Source: 1930s, "Protocol Statements" (1932), p. 91

“I learnt the truth last November — on the third of November, to be precise — and I remember every instant since.”

Fyodor Dostoyevsky book The Dream of a Ridiculous Man

Source: The Dream of a Ridiculous Man (1877), I
Context: I gave up caring about anything, and all the problems disappeared.
And it was after that that I found out the truth. I learnt the truth last November — on the third of November, to be precise — and I remember every instant since.

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

“I assume that a precisely defined, verifiable, executable, and translatable UML is a Good Thing and leave it to others to make that case… In the summer of 1999, the UML has definitions for the semantics of its components. These definitions address the static structure of UML, but they do not define an execution semantics. They also address (none too precisely) the meaning of each component, but there are "semantic variation points" which allow a component to have several different meanings. Multiple views are defined, but there is no definition of how the views fit together to form a complete model. When alternate views conflict, there is no definition of how to resolve them. There are no defined semantics for actions…
To determine what requires formalization, the UML must distinguish clearly between essential, derived, auxiliary, and deployment views. An essential view models precisely and completely some portion of the behavior of a subject matter, while a derived view shows some projection of an essential view…
All we need now is to make the market aware that all this is possible, build tools around the standards defined by the core, executable UML, and make it so…”

Stephen J. Mellor (1952) British computer scientist

Mellor in Andy Evans et al. (1999) " Advanced methods and tools for a precise UML http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.115.2039&rep=rep1&type=pdf." UML’99—The Unified Modeling Language. Springer Berlin Heidelberg. p. 709-714.

“The adoption of the Precise Action Semantics for the Unified Modeling Language specification by the OMG in November of 2001”

Help us to complete the source, original and additional information

Grady Booch 35

Related quotes

Related topics