Concepts for comparing modeling tool architectures

As model-driven development techniques grow in importance so do the capabilities and features of the tools that support them, especially tools that allow users to customize their modeling language. Superficially, many modeling tools seem to offer similar functionality, but under the surface there are important differences that can have an impact on tool builders and users depending on the tool architecture chosen. At present, however, there is no established conceptual framework for characterizing and comparing different tool architectures. In this paper we address this problem by first introducing a conceptual framework for capturing tool architectures, and then — using this framework — discuss the choices available to designers of tools. We then compare and contrast the main canonical architectures in use today.

[1]  Matthias Jarke,et al.  Telos: representing knowledge about information systems , 1990, TOIS.

[2]  Colin Atkinson,et al.  Model-Driven Development: A Metamodeling Foundation , 2003, IEEE Softw..

[3]  Jack Greenfield,et al.  Software factories: assembling applications with patterns, models, frameworks and tools , 2004, OOPSLA '03.

[4]  Brian Henderson-Sellers,et al.  Templates and Resources in Software Development Methodologies , 2005, J. Object Technol..

[5]  Matthias Jarke,et al.  ConceptBase: Managing Conceptual Models about Information Systems , 2006, Handbook on Architectures of Information Systems.

[6]  Jean Bézivin,et al.  Towards a precise definition of the OMG/MDA framework , 2001, Proceedings 16th Annual International Conference on Automated Software Engineering (ASE 2001).