When and How to Use Multilevel Modelling

• Published in: ACM transactions on software engineering and methodology Vol. 24; no. 2; pp. 1 - 46
• Main Authors: Lara, Juan De, Guerra, Esther, Cuadrado, Jesús Sánchez
• Format: Journal Article
• Language: English
• Published: 01.12.2014
• Subjects: Applications programs; Computer programs; Metamodels; Modelling; Multilevel; Software development; Software engineering
• ISSN: 1049-331X; 1557-7392
• DOI: 10.1145/2685615

Model-Driven Engineering (MDE) promotes models as the primary artefacts in the software development process, from which code for the final application is derived. Standard approaches to MDE (like those based on MOF or EMF) advocate a two-level metamodelling setting where Domain-Specific Modelling Languages (DSMLs) are defined through a metamodel that is instantiated to build models at the metalevel below. Multilevel modelling (also called deep metamodelling ) extends the standard approach to metamodelling by enabling modelling at an arbitrary number of metalevels, not necessarily two. Proposers of multilevel modelling claim this leads to simpler model descriptions in some situations, although its applicability has been scarcely evaluated. Thus, practitioners may find it difficult to discern when to use it and how to implement multilevel solutions in practice. In this article, we discuss those situations where the use of multilevel modelling is beneficial, and identify recurring patterns and idioms. Moreover, in order to assess how often the identified patterns arise in practice, we have analysed a wide range of existing two-level DSMLs from different sources and domains, to detect when their elements could be rearranged in more than two metalevels. The results show this scenario is not uncommon, while in some application domains (like software architecture and enterprise/process modelling) pervasive, with a high average number of pattern occurrences per metamodel.