Modeling Maturity Levels is a classification system defined by
Anneke Kleppe
Anneke is a Dutch language, Dutch and Low German language, Low German female diminutive given name, meaning ''little Anna'' or ''little Anne'', i.e., ''Annie'', an alternate pet or endearing form of Anna (name), Anna. The given name and later surna ...
and
Jos Warmer
Jos is a city in the north central region of Nigeria. The city has a population of about 900,000 residents based on the 2006 census. Popularly called "J-Town", it is the administrative capital and largest city of Plateau State.
During British ...
in their book
MDA Explained
MDA, mda, or ''variation'', may refer to:
Places
* Moldova, a country in Europe with the ISO 3166-1 country code MDA Politics
* Meghalaya Democratic Alliance (2018), ruling coalition government in the Indian State of Meghalaya led by National P ...
Addison-Wesley
Addison-Wesley is an American publisher of textbooks and computer literature. It is an imprint of Pearson PLC, a global publishing and education company. In addition to publishing books, Addison-Wesley also distributes its technical titles through ...
. The levels characterize the role of modeling in a software project.
The concept shows resemblance to the way software processes are rated with the
Capability Maturity Model The Capability Maturity Model (CMM) is a development model created in 1986 after a study of data collected from organizations that contracted with the U.S. Department of Defense, who funded the research. The term "maturity" relates to the degree of ...
.
There are 6 levels
;Level 0: No Specification: the specification of software is not written down. It is kept in the minds of the developers
;Level 1: Textual Specification: the software is specified by a natural language text (be it English or Chinese or something else), written down in one or more documents
;Level 2: Text with Models: a textual specification is enhanced with several models to show some of the main structures of the system
;Level 3: Models with Text: the specification of software is written down in one or more models. In addition to these models, natural language text is used to explain details, the background, and the motivation of the models, but the core of the specifications lies in the models.
;Level 4: Precise Models: the specification of the software is written down in one or more models. Natural language can still be used to explain the background and motivation of the models, but it takes on the same role as comments in source code.
;Level 5: Models only: the models are precise and detailed enough to allow complete code generation. The code generators at this level have become as trustworthy as compilers, therefore no developer needs to even look at the generated code.
References
*T. Mettler
Thinking in terms of design decisions when developing maturity models International Journal of Strategic Decision Sciences, 1(4), 2010, pp. 76-87.
*T. Mettler, P. Rohner, and R. Winter
Towards a Classification of Maturity Models in Information Systems Management of the Interconnected World, in: A. D'Atri, M. De Marco, A.M. Braccini, and F. Cabiddu (Eds.), Berlin, Heidelberg: Physica, 2010, pp. 333-340.
*Anneke Kleppe and Jos Warmer in their book MDA Explained Addison-Wesley
*Book
MDA Explained: The Model Driven Architecture : Practice and Promise" by Anneke G. Kleppe, Jos B. Warmer, Wim Bast Publisher: Addison-Wesley Professional, Release Date: April 2003,
External links
Getting Started with Modeling Maturity Levels
Unified Modeling Language
Maturity models
{{uml-stub