“MDA per se is relaxed about exactly what models it transforms, so long as the modeling language in which the models are expressed can be defined.”

—  Stephen J. Mellor

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

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 "MDA per se is relaxed about exactly what models it transforms, so long as the modeling language in which the models are…" by Stephen J. Mellor?
Stephen J. Mellor photo
Stephen J. Mellor 13
British computer scientist 1952

Related quotes

“In the bad old days before MDA, (conceptual) models served only to facilitate communication between customers and developers and act as blueprints for construction. Nowadays, MDA establishes the infrastructure for defining and executing transformations between models of various kinds.”

Stephen J. Mellor (1952) British computer scientist

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

Grady Booch photo

“The development of the Model Driven Architecture (MDA) standards by the Object Management Group”

Grady Booch (1955) American software engineer

OMG
The Limits of Software

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

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

“I know that I disagree with many other UML experts, but there is no magic about UML. If you can generate code from a model, then it is programming language. And UML is not a well-designed programming language.
The most important reason is that it lacks a well-defined point of view, partly by intent and partly because of the tyranny of the OMG standardization process that tries to provide everything to everybody. It doesn't have a well-defined underlying set of assumptions about memory, storage, concurrency, or almost anything else. How can you program in such a language?
The fact is that UML and other modelling language are not meant to be executable. The point of models is that they are imprecise and ambiguous. This drove many theoreticians crazy so they tried to make UML "precise", but models are imprecise for a reason: we leave out things that have a small effect so we can concentrate on the things that have big or global effects. That's how it works in physics models: you model the big effect (such as the gravitation from the sun) and then you treat the smaller effects as perturbation to the basic model (such as the effects of the planets on each other). If you tried to solve the entire set of equations directly in full detail, you couldn't do anything.”

James Rumbaugh (1947) Computer scientist, software engineer

James Rumbaugh in Federico Biancuzzi and Shane Warden eds. (2009) Masterminds of Programming. p. 339; cited in " Quote by James Rumbaugh http://www.ptidej.net/course/cse3009/winter13/resources/james" on ptidej.net. Last updated 2013-04-09 by guehene; Rumbaugh is responding to the question: "What do you think of using UML to generate implementation code?"

“CIMOSA provides a Reference Architecture (known as the CIMOSA cube) from which particular enterprise architectures can be derived. This Reference Architecture and the associated enterprise modelling framework are based on a set of modelling constructs, or generic building blocks, which altogether form the CIMOSA modelling languages.”

Peter Bernus (1949) Hungarian-Australian computer scientist

Peter Bernus, Kai Mertins, Günter Schmidt (1998) Handbook on Architectures of Information Systems. p. 244

Russell L. Ackoff photo

“The word model is used as a noun, adjective, and verb, and in each instance it has a slightly different connotation. As a noun "model" is a representation in the sense in which an architect constructs a small-scale model of a building or a physicist a large-scale model of an atom. As an adjective "model" implies a degree or perfection or idealization, as in reference to a model home, a model student, or a model husband. As a verb "to model" means to demonstrate, to reveal, to show what a thing is like.”

Russell L. Ackoff (1919–2009) Scientist

Source: 1960s, Scientific method: optimizing applied research decisions, 1962, p. 108 as cited in: Charles West Churchman, Richard O. Mason (1976) World modeling: a dialogue. p. 23.

Edward Fredkin photo

“Cellular automata are now being used to model varied physical phenomena normally modelled by wave equations, fluid dynamics, Ising models, etc. We hypothesize that there will be found a single cellular automaton rule that models all of microscopic physics; and models it exactly. We call this field DM, for digital mechanics.”

Edward Fredkin (1934) American physicist and computer scientist, a pioneer of digital physics

[An informational process based on reversible universal cellular automata, Physica D: Nonlinear Phenomena, 45, 1–3, September 1990, 254–270, https://www.sciencedirect.com/science/article/pii/016727899090186S, 10.1016/0167-2789(90)90186-S]

James Martin (author) photo

“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

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

Related topics