The Impact of Integrating Agile Software Development and Model-Driven Development: A Comparative Case Study

  • Hessa AlfraihiEmail author
  • Kevin Lano
  • Shekoufeh Kolahdouz-Rahimi
  • Mohammadreza Sharbaf
  • Howard Haughton
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 11150)


Agile and Model-Driven Development integration (Agile MDD) is of significant interest to researchers who want to leverage the best of both worlds. Currently, there is no clear evidence or proof for the real impact of such integration. As a first step in this direction, this paper reports an empirical investigation on the impact of integrating Agile and Model-Driven Development on the quality of software systems. To this end, we developed a financial application using Agile MDD, which is further contrasted with three other independent versions of the same application developed using different approaches: Agile method, MDD method, and traditional (manually-coded) method, respectively. We also compared the functionality of the systems and a variety of technical debt metrics measuring the quality of the code and its design. Based on the case study results, we have found that the use of Agile MDD shows some improvements in the product quality and efficiency.


Agile development Model-driven development Agile model-driven development integration Case study Financial applications 


  1. 1.
    Alfraihi, H., Lano, K.: The integration of agile development and model driven development: a systematic literature review. In: Proceedings of the 5th International Conference on Model-Driven Engineering and Software Development, MODELSWARD (2017)Google Scholar
  2. 2.
    Alfraihi, H., Lano, K.: A process for integrating agile software development and model-driven development. In: 3rd Flexible MDE Workshop (FlexMDE) Co-located with ACM/IEEE 20th International Conference on Model Driven Engineering Languages & Systems (MoDELS 2017), CEUR Workshop Proceedings, Austin, TX, USA, pp. 412–417. (2017)Google Scholar
  3. 3.
    Atkinson, C., Kuhne, T.: Model-driven development: a metamodeling foundation. IEEE Softw. 20(5), 36–41 (2003)CrossRefGoogle Scholar
  4. 4.
    Basili, V.R.: Software modeling and measurement: the goal/question/metric paradigm. Technical report (1992)Google Scholar
  5. 5.
    Beck, K.: Extreme Programming Explained: Embrace Change. Addison-Wesley Professional, Boston (2000)Google Scholar
  6. 6.
    Burden, H., Hansson, S., Zhao, Y.: How MAD are we? empirical evidence for model-driven agile development. In: Proceedings of XM 2014, 3rd Extreme Modeling Workshop, Valencia, Spain, vol. 1239, pp. 2–11. CEUR (2014)Google Scholar
  7. 7.
    Davis, M., Lo, V.: Infectious defaults. Quant. Financ. 1(4), 382–387 (2001)CrossRefGoogle Scholar
  8. 8.
    Fowler, M.: The new methodology. Wuhan Univ. J. Nat. Sci. 6(1), 12–24 (2001). MarCrossRefGoogle Scholar
  9. 9.
    Hammarlid, O.: Aggregating sectors in the infectious defaults model. Quan. Financ. 4(1), 64–69 (2004)CrossRefGoogle Scholar
  10. 10.
    He, X., Avgeriou, P., Liang, P., Li, Z.: Technical debt in MDE: a case study on GMF/EMF-based projects. In: Proceedings of the ACM/IEEE 19th International Conference on Model Driven Engineering Languages and Systems, pp. 162–172. ACM (2016)Google Scholar
  11. 11.
    Knippers, D.: Agile software development and maintainability. In: 15th Twente Student Conference (2011)Google Scholar
  12. 12.
    Kolovos, D.S., Paige, R.F., Polack, F.A.C.: The epsilon transformation language. In: Vallecillo, A., Gray, J., Pierantonio, A. (eds.) ICMT 2008. LNCS, vol. 5063, pp. 46–60. Springer, Heidelberg (2008). Scholar
  13. 13.
    Lano, K.: Agile Model-Based Development Using UML-RSDS. CRC Press, Boca Raton (2017)Google Scholar
  14. 14.
    Lano, K., Rahimi, S.K., Sharbaf, M., Alfraihi, H.: Technical debt in model transformation specifications. In: Theory and Practice of Model Transformations (2018)CrossRefGoogle Scholar
  15. 15.
    MacDonald, A., Russell, D., Atchison, B.: Model-driven development within a legacy system: an industry experience report. In: Proceedings of 2005 Australian Software Engineering Conference, pp. 14–22. IEEE (2005)Google Scholar
  16. 16.
    Marinescu, R.: Assessing technical debt by identifying design flaws in software systems. IBM J. Res. Dev. 56(5), 9:1–9:13 (2012)CrossRefGoogle Scholar
  17. 17.
    Mellor, S.J., Clark, T., Futagami, T.: Model-driven development: guest editors’ introduction. IEEE Softw. 20(5), 14–18 (2003)CrossRefGoogle Scholar
  18. 18.
    Michie, D.: Memo functions and machine learning. Nature 218(5136), 19 (1968)CrossRefGoogle Scholar
  19. 19.
    Moser, R., Abrahamsson, P., Pedrycz, W., Sillitti, A., Succi, G.: A case study on the impact of refactoring on quality and productivity in an agile team. In: Meyer, B., Nawrocki, J.R., Walter, B. (eds.) CEE-SET 2007. LNCS, vol. 5082, pp. 252–266. Springer, Heidelberg (2008). Scholar
  20. 20.
    Nyström, A.: Agile solo-defining and evaluating an agile software development process for a single software developer (2011)Google Scholar
  21. 21.
    Pagotto, T., Fabri, J.A., Lerario, A., Gonçalves, J.A.: Scrum solo: software process for individual development. In: 2016 11th Iberian Conference on Information Systems and Technologies (CISTI), pp. 1–6. IEEE (2016)Google Scholar
  22. 22.
    Schwaber, K., Beedle, M.: Agile Software Development with Scrum. Prentice Hall, Agile Software Development (2002)zbMATHGoogle Scholar
  23. 23.
    Seaman, C., Guo, Y.: Measuring and monitoring technical debt. In: Advances in Computers, vol. 82, pp. 25–46. Elsevier, UK (2011)Google Scholar
  24. 24.
    Staron, M., Durisic, D., Rana, R.: Improving measurement certainty by using calibration to find systematic measurement error—a case of lines-of-code measure. In: Madeyski, L., Śmiałek, M., Hnatkowska, B., Huzar, Z. (eds.) Software Engineering: Challenges and Solutions. AISC, vol. 504, pp. 119–132. Springer, Cham (2017). Scholar
  25. 25.
    Steinberg, D., Budinsky, F., Merks, E., Paternostro, M.: EMF: Eclipse Modeling Framework, 2nd edn. Pearson Education, London (2008)Google Scholar
  26. 26.
    Yin, R.K.: Case study research: design and methods. SAGE 2003(181), 15 (2003)Google Scholar
  27. 27.
    Zhang, Y., Patel, S.: Agile model-driven development in practice. IEEE Softw. 28(2), 84–91 (2011)CrossRefGoogle Scholar

Copyright information

© Springer Nature Switzerland AG 2018

Authors and Affiliations

  • Hessa Alfraihi
    • 1
    • 3
    Email author
  • Kevin Lano
    • 1
  • Shekoufeh Kolahdouz-Rahimi
    • 2
  • Mohammadreza Sharbaf
    • 2
  • Howard Haughton
    • 1
  1. 1.Department of InformaticsKing’s College LondonLondonUK
  2. 2.Department of Software EngineeringUniversity of IsfahanIsfahanIran
  3. 3.Department of Information SystemsPrincess Nourah bint Abdulrahman UniversityRiyadhSaudi Arabia

Personalised recommendations