Adopting model driven software development in industry: a case study at two companies

Model Driven Software Development (MDD) is a vision of software development where models play a core role as primary development artifacts. Its industrial adoption depends on several factors, including possibilities of increasing productivity and quality by using models. In this paper we present a case study of two companies willing to adopt the principles of MDD. One of the companies is in the process of adopting MDD while the other withdrew from its initial intentions. The results provide insights into the differences in requirements for MDD in these organizations, factors determining the decision upon adoption and the potentially suitable modeling notation for the purpose of each of the companies. The analysis of the results from this case study, supported by the conclusions from a previous case study of a successful MDD adoption, show also which conditions should be fulfilled in order to increase the chances of succeeding in adopting MDD.

[1]  Tore Dybå,et al.  Evidence-Based Software Engineering for Practitioners , 2005, IEEE Softw..

[2]  Robert B. Grady,et al.  Key lessons in achieving widespread inspection use , 1994, IEEE Software.

[3]  Jens Knodel,et al.  An Efficient Migration to Model-driven Development (MDD) , 2005, Electron. Notes Theor. Comput. Sci..

[4]  Stephen J. Mellor,et al.  MDA Distilled Principles Of Model-Driven Architecture , 2004 .

[5]  Alan W. Brown.  An Introduction to Model Driven Architecture - Part 1; MDA and Today's Systems , 2004 .

[6]  Lars Lundberg,et al.  Software development productivity on a new platform: an industrial case study , 2005, Inf. Softw. Technol..

[7]  Jean Jourdan,et al.  Practical Experiences in the Application of MDA , 2002, UML.

[8]  Miroslaw Staron,et al.  Improving Modeling with UML by Stereotype-based Language Customization , 2005 .

[9]  Daniel M. Russell,et al.  Model-driven development within a legacy system: an industry experience report , 2005, 2005 Australian Software Engineering Conference.

[10]  Miroslaw Staron,et al.  An Industrial Case Study on the Choice Between Language Customization Mechanisms , 2006, PROFES.

[11]  Colin Atkinson,et al.  Concepts for comparing modeling tool architectures , 2005, MoDELS'05.

[12]  Krzysztof Czarnecki,et al.  Generative Programming , 2001, ECOOP Workshops.

[13]  Claes Wohlin,et al.  Experimentation in software engineering: an introduction , 2000 .

[14]  Richard V. McCarthy,et al.  Does UML make the grade? Insights from the software development community , 2005, Inf. Softw. Technol..

[15]  A. Evans,et al.  Building families of languages for model-driven system development , 2003 .

[16]  Dave A. Thomas,et al.  MDA: revenge of the modelers or UML utopia? , 2004, IEEE Software.

[17]  Xml Web Java,et al.  Model Driven Development for J 2 EE Utilizing a Model Driven Architecture ( MDA ) Approach Productivity Analysis June 2003 Java , 2003 .

[18]  Miroslaw Staron,et al.  Factors Determining Effective Realization of MDA in Industry , 2004 .

[19]  Stuart Kent,et al.  Model Driven Engineering , 2002, IFM.

[20]  Jack Greenfield.  Software Factories: Assembling Applications with Patterns, Models, Frameworks and Tools , 2004, GPCE.

[21]  Miroslaw Staron,et al.  Case Study on a Process of Industrial MDA Realization -- Determinants of Effectiveness , 2004, Nord. J. Comput..

[22]  Ivan Porres,et al.  A toolkit for model manipulation , 2003, Software & Systems Modeling.

[23]  James Miller.  Statistical significance testing--a panacea for software technology experiments? , 2004, J. Syst. Softw..