How face the top MDE adoption problems

Model Driven Engineering (MDE) refers to the creation and manipulation of models in the end-to-end application lifecycle. When adopting a model-based development approach many challenges arise, some of these are related to the immaturity of the methods and tools that support this paradigm. This paper presents an exploratory case study developed to analyze how the renowned MDE technology solutions contribute to face the adoption problems. The case study consisted of developing a Web application for an incident management process based on ITIL (Information Technology Infrastructure Library) using tools from three different MDE approximations: MDA, MDSD, and BPM. As a result of our study, we suggest different strategies to help practitioners face the top MDE adoption problems.

[1]  Miroslaw Staron,et al.  Adopting model driven software development in industry: a case study at two companies , 2006, MoDELS'06.

[2]  Parastoo Mohagheghi,et al.  Where Is the Proof? - A Review of Experiences from Applying MDE in Industry , 2008, ECMDA-FA.

[3]  Javier Pérez,et al.  Estrategias para la Definición de una Técnica de Modelado para Arquitecturas de Referencia , 2009, CIbSE.

[4]  Gabor Karsai,et al.  Applying a Model Transformation Taxonomy to Graph Transformation Technology , 2006, GRaMoT@GPCE.

[5]  Francisco Curbera,et al.  Web Services Business Process Execution Language Version 2.0 , 2007 .

[6]  Marlon Dumas,et al.  Case Study : BPMN to BPEL Model Transformation , 2008 .

[7]  Victor R. Basili,et al.  Bridging the Gap between Business Strategy and Software Development , 2007, ICIS.

[8]  Juan Bernardo Quintero,et al.  Estudio Comparativo de Técnicas de Modelado de Negocio , 2008, CIbSE.

[9]  Juan Bernardo Quintero,et al.  Marco de Referencia para la Evaluación de Herramientas basadas en MDA , 2007, CIbSE.

[10]  Daniel Calegari,et al.  Estado del arte de lenguajes y herramientas de transformación de modelos , 2009 .

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

[12]  Ruzanna Chitchyan,et al.  A Survey of Analysis and Design Approaches , 2005 .

[13]  Timothy C. Lethbridge,et al.  Problems and Opportunities for Model-Centric vs. Code-Centric Development: A Survey of Software Prof , 2010 .

[14]  Grady Booch.  El Lenguaje Unificado de Modelado , 2006 .

[15]  Bernhard Rumpe,et al.  Model-driven Development of Complex Software : A Research Roadmap , 2007 .

[16]  Jos Warmer,et al.  The object constraint language , 1998 .

[17]  Linda Northrop.  Software Product Lines Essentials , 2008 .

[18]  Markus Völter,et al.  Model-Driven Software Development: Technology, Engineering, Management , 2006 .

[19]  Krzysztof Czarnecki,et al.  Feature-based survey of model transformation approaches , 2006, IBM Syst. J..

[20]  Sergiu M. Dascalu,et al.  Tools for MDA Software Development: Evaluation Criteria and Set of Desirable Features , 2008, Fifth International Conference on Information Technology: New Generations (itng 2008).

[21]  J. Oldevik,et al.  An Empirical Study of the UML Model Transformation Tool ( UMT ) , 2004 .