Key Features for a Successful Model-Driven Development Tool

Beatriz Marín, Andrés Salinas, Juan Morandé, Giovanni Giachetti, Jose De la Vara


The main focus of Software Engineering discipline is to establishing methods and processes for the effective and efficient development of software projects. One of the most relevant paradigms for achieving this goal is Model-Driven Development (MDD). MDD uses models at different abstraction levels to automatically generate software products by means of model-transformations. However, one of the main issues related to the development of MDD technologies is the lack of standardization in terms of the features that need to be considered to support the current industry needs. This difficults the comparison of existing technologies since there are not a reference point for the creation of new MDD approaches with their corresponding supporting tools. This paper analyses these industry needs through an exploratory study. From the results obtained, it states the main features that must be supported by MDD tools. In addition, this paper presents an analysis about the presence or absence of these features in a set of industrial MDD tools.


  1. Balogh, A. & Varró, D. 2006. Advanced Model Transformation Language Constructs in the VIATRA2 Framework. ACM Symposium on Applied Computing - Model Transformation Track (SAC 2006). Dijon: ACM Press.
  2. Berson, A. 1996. Client/server architecture, McGraw-Hill.
  3. Conradi, R., Mohagheghi, P., Arif, T., Hegde, L. C., Bunde, G. A. & Pedersen, A. 2003. Object-Oriented Reading Techniques for Inspection of UML Models - An Industrial Experiment. 17th ECOOP. Springer.
  4. Dias Neto, A. C., Subramanyan, R., Vieira, M. & Travassos, G. H. 2007. A survey on model-based testing approaches: a systematic review. 1st ACM international workshop on Empirical assessment of software engineering languages and technologies (WEASELTech 7807). NY, USA: ACM.
  5. Egyed, A. 2006. Instant Consistency Checking for the UML. 28th ICSE. Shangai, China: ACM.
  6. Epsilon. 2010. (Online).
  7. Garber, L. 2012. Tangible User Interfaces: Technology You Can Touch. IEEE Computer, 45, 15-18.
  8. IEEE 1984. IEEE 830 Guide to Software Requirements Specifications.
  9. ISO/IEC 2001. ISO/IEC 9126-1, Software Eng. - Product Quality - Part 1: Quality model.
  10. ISO/IEC 2003. ISO/IEC 20926, Software Engineering - IFPUG 4.1 Unadjusted Functional Size Measurement Method - Counting Practices Manual.
  11. ISO/IEC 2011. ISO/IEC 19761, Software Engineering - COSMIC - A Functional Size Measurement Method.
  12. Kitchenham, B. & Pfleeger, S. 1996. Software Quality: The Elusive Target. IEEE Software, 13, 12-21.
  13. Lange, C. & Chaudron, M. 2004. An Empirical Assessment of Completeness in UML Designs. 8th Conf. on Empirical Assessment in Software Eng. (EASE). IEEE.
  14. Marín, B., Pastor, O. & Abran, A. 2010. Towards an accurate functional size measurement procedure for conceptual models in an MDA environment. Data & Knowledge Engineering, 69, 472-490.
  15. Marín, B., Pereira, J., Giachetti, G., Hermosilla, F. & Serral, E. 2013. A General Framework for the Development of MDD Projects. 1st International Conference on Model-Driven Engineering and Software Development - MODELSWARD 2013. Barcelona - Spain: SciTePress.
  16. OMG 2003. MDA Guide Version 1.0.1. In: JOAQUIN MILLER & MUKERJI, J. (eds.).
  17. OMG 2006. Object Constraint Language 2.0 Specification.
  18. OMG 2007a. UML 2.1.2 Infrastructure Specification.
  19. OMG 2007b. XMI 2.1.1 Specification.
  20. OMG 2010. UML 2.3 Superstructure Specification.
  21. Paige, R. F. & Varró, D. 2012. Lessons learned from building model-driven development tools. Software & Systems Modeling, 11, 527-539.
  22. Pastor, O., Gómez, J., Insfrán, E. & Pelechano, V. 2001. The OO-Method Approach for Information Systems Modelling: From Object-Oriented Conceptual Modeling to Automated Programming. Information Systems, 26, 507-534.
  23. Pastor, O., Hayes, F. & Bear, S. 1992. OASIS: An ObjectOriented Specification Language. Int. Conference on Advanced Information Systems Engineering (CAiSE). Manchester, UK.
  24. Reenskaug, T. 2003. The Model-View-Controller (MVC), Its Past and Present. University of Oslo.
  25. Schmidt, D. 2006. Model Driven Engineering. IEEE Computer, 39, 25-31.
  26. Selic, B. 2003. The Pragmatics of Model-Driven Development. IEEE Software, 20, 19-25.
  27. Travassos, G., Shull, F., Fredericks, M. & Basili, V. 1999. Detecting Defects in Object-Oriented Designs: Using Reading Techniques to Increase Software Quality. OOPSLA' 99. Denver, CO, USA.
  28. Vos, T. E., Baars, A. I., Lindlar, F., Kruse, P. M., Windisch, A. & Weneger, J. 2010. Industrial Scaled Automated Structural Testing with the Evolutionary Testing Tool. Third International Conference on Software Testing, Verification and Validation (ICST). IEEE Computer Society.

Paper Citation

in Harvard Style

Marín B., Salinas A., Morandé J., Giachetti G. and De la Vara J. (2014). Key Features for a Successful Model-Driven Development Tool . In Proceedings of the 2nd International Conference on Model-Driven Engineering and Software Development - Volume 1: MODELSWARD, ISBN 978-989-758-007-9, pages 541-548. DOI: 10.5220/0004723705410548

in Bibtex Style

author={Beatriz Marín and Andrés Salinas and Juan Morandé and Giovanni Giachetti and Jose De la Vara},
title={Key Features for a Successful Model-Driven Development Tool},
booktitle={Proceedings of the 2nd International Conference on Model-Driven Engineering and Software Development - Volume 1: MODELSWARD,},

in EndNote Style

JO - Proceedings of the 2nd International Conference on Model-Driven Engineering and Software Development - Volume 1: MODELSWARD,
TI - Key Features for a Successful Model-Driven Development Tool
SN - 978-989-758-007-9
AU - Marín B.
AU - Salinas A.
AU - Morandé J.
AU - Giachetti G.
AU - De la Vara J.
PY - 2014
SP - 541
EP - 548
DO - 10.5220/0004723705410548