In Model Driven Development (MDD), models replace software code as the development artifact. At the same time, requirements represent the information that is elaborated in models. However, despite the tight relationship between models and requirements, only a few MDD approaches provide the necessary methodological guidelines and tool support to explicitly facilitate this relationship. We analyze approaches for integrating requirements with models within MDD and highlight the common characteristics, benefits, and problems. Based on the analysis, we elicit a set of general properties that need to be fulfilled when considering the integration of requirements and models, and we assess the contribution of the considered approaches accordingly.


Model Driven Development MDD Model-Driven Engineering MDE Requirements 


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Aksit, M.: Systematic Analysis of Crosscutting Concerns in the Model-Driven Architecture Design Approach. In: Symposium on How Adaptable is MDA?, Twente, The Netherlands (2005) Google Scholar
  2. 2.
    Alencar, F., Marín, B., Giachetti, G., Pastor, O., Castro, J., Pimentel, J.H.: From i* requirements models to conceptual models of a model driven development process. In: Persson, A., Stirna, J. (eds.) PoEM 2009. Lecture Notes in Business Information Processing, vol. 39, pp. 99–114. Springer, Heidelberg (2009)CrossRefGoogle Scholar
  3. 3.
    de Almeida Ferreira, D., Rodrigues da Silva, A.: A Controlled Natural Language Approach for Integrating Requirements and Model-Driven Engineering. In: Fourth International Conference on Software Engineering Advances, ICSEA 2009, pp. 518–523 (2009) Google Scholar
  4. 4.
    Anquetil, N., Grammel, B., Galvao Lourenco da Silva, I., Noppen, J.A.R., Shakil Khan, S., Arboleda, H., Rashid, A., Garcia, A.: Traceability for Model Driven, Software Product Line Engineering. In: ECMDA Traceability Workshop Proceedings, Berlin, Germany, pp. 77–86. SINTEF, Norway (2008)Google Scholar
  5. 5.
    Anquetil, N., Kulesza, U., Mitschke, R., Moreira, A., Royer, J.C., Rummler, A., Sousa, A.: A Model-Driven Traceability Framework for Software Product Lines. Software and Systems Modeling 9, 427–451 (2010)CrossRefGoogle Scholar
  6. 6.
    Atkinson, C., Kuhne, T.: Model-Driven Development: A Metamodeling Foundation. IEEE Software 20(5), 36–41 (2003)CrossRefGoogle Scholar
  7. 7.
    Baum, L., Becker, M., Geyer, L., Molter, G.: Mapping Requirements to Reusable Components Using Design Spaces. In: Proc. of the IEEE Int’l Conference on Requirements Engineering, ICRE 2000, pp. 159–167. IEEE, Los Alamitos (2000)Google Scholar
  8. 8.
    Brito, I., Moreira, A.: Aspect-Oriented Software Development: an Overview. In: 5th International Conference on Enterprise Information Systems (ICEIS), Angers, France, pp. 531–534 (2003)Google Scholar
  9. 9.
    Bryant, B.R., Lee, B.S., Cao, F., Zhao, W., Gray, J.G., Burt, C.C., Raje, R.R., Olson, A.M., Auguston, M.: From Natural Language Requirements to Executable Models of Software Components. In: Proc. of the Monterey Workshop on Software Engineering for Embedded Systems: From Requirements to Implementation, pp. 51–58 (2003)Google Scholar
  10. 10.
    Bryant, B.R.: Object-Oriented Natural Language Requirements Specification. In: 23rd Australasian Computer Science Conference, ACSC 2000, pp. 24–30 (2000) Google Scholar
  11. 11.
    Chung, L., Nixon, B.A., Yu, E., Mylopoulos, J.: Non-Functional Requirements in Software Engineering. Springer, Heidelberg (1999)Google Scholar
  12. 12.
    Cysneiros, L., do Prado Leite, J.C.S.: Nonfunctional Requirements: from Elicitation to Conceptual Models. IEEE Transactions on Software Engineering 30(5), 328–350 (2004)CrossRefGoogle Scholar
  13. 13.
    Dardenne, A., van Lamsweerde, A., Fickas, S.: Goal Directed Requirements Acquisition. In: Science of Computer Programming, vol. 20, pp. 3–50. North-Holland, Amsterdam (1993)Google Scholar
  14. 14.
    Debnath, N., Leonardi, M.C., Mauco, M.V., Montejano, G., Riesco, D.: Improving Model Driven Architecture with Requirements Models. In: Fifth International Conference on Information Technology: New Generations, ITNG 2008. pp. 21–26 (2008) Google Scholar
  15. 15.
    Fatwanto, A., Boughton, C.: Analysis, Specification and Modeling of Functional Requirements for Translative Model-Driven Development. In: International Symposium on Knowledge Acquisition and Modeling, KAM 2008, pp. 859–863 (2008)Google Scholar
  16. 16.
    Fatwanto, A., Boughton, C.: Analysis, Specification and Modeling of Non-Functional Requirements for Translative Model-Driven Development. In: International Conference on Computational Intelligence and Security, CIS 2008, vol. 2, pp. 405–410 (2008) Google Scholar
  17. 17.
    Fatwanto, A., Boughton, C.: Concern-Oriented Model-Driven Development Framework. In: 19th Australian Conference on Software Engineering, ASWEC 2008, pp. 527–535 (2008) Google Scholar
  18. 18.
    Favre, J.M.: Towards a Basic Theory to Model Model Driven Engineering. In: 3rd Workshop on Software Model Engineering, WiSME 2004 (2004)Google Scholar
  19. 19.
    France, R., Rumpe, B.: Model-Driven Development Of Complex Software: A Research Roadmap. In: Future of Software Engineering, FOSE 2007, pp. 37–54. IEEE Computer Society, Washington, DC, USA (2007)Google Scholar
  20. 20.
    Fu, J., Bastani, F.B., Yen, I.-L.: Model-driven prototyping based requirements elicitation. In: Martell, C. (ed.) Monterey Workshop 2007. LNCS, vol. 5320, pp. 43–61. Springer, Heidelberg (2008)CrossRefGoogle Scholar
  21. 21.
    Gašević, D., Djurić, D., Devedićž, V.: Model Driven Engineering. In: Model Driven Engineering and Ontology Development, pp. 125–155. Springer, Heidelberg (2009)Google Scholar
  22. 22.
    Guelfi, N., Perrouin, G.: A flexible requirements analysis approach for software product lines. In: Sawyer, P., Heymans, P. (eds.) REFSQ 2007. LNCS, vol. 4542, pp. 78–92. Springer, Heidelberg (2007)CrossRefGoogle Scholar
  23. 23.
    Harmain, H.M., Gaizauskas, R.: CM-Builder: A Natural Language-Based Case Tool for Object-Oriented Analysis. Automated Software Engineering 10, 157–181 (2003)CrossRefGoogle Scholar
  24. 24.
    Henkel, M., Stirna, J.: Pondering on the key functionality of model driven development tools: The case of mendix. In: Forbrig, P., Günther, H. (eds.) BIR 2010. Lecture Notes in Business Information Processing, vol. 64, pp. 146–160. Springer, Heidelberg (2010)CrossRefGoogle Scholar
  25. 25.
    Ilieva, M.G., Ormandjieva, O.: Models Derived from Automatically Analyzed Textual User Requirements. In: Fourth International Conference on Software Engineering Research, Management and Applications, pp. 13–21 (2006) Google Scholar
  26. 26.
    Insfrán, E., Pastor, O., Wieringa, R.: Requirements Engineering-Based Conceptual Modeling. Requirements Engineering 7, 61–72 (2002)CrossRefGoogle Scholar
  27. 27.
    Jørgensen, J.B., Bossen, C.: Executable Use Cases: Requirements for a Pervasive Health Care System. IEEE Softw. 21(2), 34–41 (2004)CrossRefGoogle Scholar
  28. 28.
    Jørgensen, J., Tjell, S., Fernandes, J.M.: Formal Requirements Modeling with Executable Use Cases and Coloured Petri Nets. Innovations in Systems and Software Engineering 5, 13–25 (2009)CrossRefGoogle Scholar
  29. 29.
    Caskurlu, B.: Model driven engineering. In: Butler, M., Petre, L., Sere, K. (eds.) IFM 2002. LNCS, vol. 2335, p. 286. Springer, Heidelberg (2002)CrossRefGoogle Scholar
  30. 30.
    Lane, T.G.: Studying Software Architecture through Design Spaces and Rules. Tech. Rep. CMU/SEI-90-TR-18, Carnegie Mellon University (1990) Google Scholar
  31. 31.
    Ledeczi, A., Maroti, M., Bakay, A., Karsai, G., Garrett, J., Thomason, C., Nordstrom, G., Sprinkle, J., Volgyesi, P.: The Generic Modeling Environment. In: Workshop on Intelligent Signal Processing (2001)Google Scholar
  32. 32.
    Lindstrom, D.R.: Five Ways to Destroy a Development Project. IEEE Software 10(5), 55–58 (1993)CrossRefGoogle Scholar
  33. 33.
    Lucena, M., Castro, J., Silva, C., Alencar, F., Santos, E., Pimentel, J.: A model transformation approach to derive architectural models from goal-oriented requirements models. In: Meersman, R., Herrero, P., Dillon, T. (eds.) OTM 2009 Workshops. LNCS, vol. 5872, pp. 370–380. Springer, Heidelberg (2009)CrossRefGoogle Scholar
  34. 34.
    Martínez, A., Castro, J., Pastor, O., Estrada, H.: Closing the Gap between Organizational Modeling and Information System Modeling. In: The Sixth Workshop on Requirements Engineering (WER 2003) (2003) Google Scholar
  35. 35.
    Mazón, J.N., Pardillo, J., Trujillo, J.: A Model-Driven Goal-Oriented Requirement Engineering Approach for Data Warehouses. In: ER Workshops, pp. 255–264 (2007) Google Scholar
  36. 36.
    Mellor, S.J., Balcer, M.J.: Executable UML: a Foundation for Model-Driven Architecture. Addison-Wesley, Indianapolis (2002)Google Scholar
  37. 37.
    Mellor, S.J., Clark, A.N., Futagami, T.: Model-Driven Development. IEEE Software 20, 14–18 (2003)CrossRefGoogle Scholar
  38. 38.
    Montes, A., Pacheco, H., Estrada, H., Pastor, Ó.: Conceptual model generation from requirements model: A natural language processing approach. In: Kapetanios, E., Sugumaran, V., Spiliopoulou, M. (eds.) NLDB 2008. LNCS, vol. 5039, pp. 325–326. Springer, Heidelberg (2008)CrossRefGoogle Scholar
  39. 39.
    Moody, D.L., Shanks, G.G.: Improving the Quality of Data Models: Empirical Validation of a Quality Management Framework. Information Systems (IS) 28(6), 619–650 (2003)CrossRefGoogle Scholar
  40. 40.
    Navarro, E.: Architecture Traced from Requirements applying a Unified Methodology, PhD thesis, Computing Systems Department, UCLM (2007)Google Scholar
  41. 41.
    Navarro, E., Cuesta, C.E.: Automating the trace of architectural design decisions and rationales using a MDD approach. In: Morrison, R., Balasubramaniam, D., Falkner, K. (eds.) ECSA 2008. LNCS, vol. 5292, pp. 114–130. Springer, Heidelberg (2008)CrossRefGoogle Scholar
  42. 42.
    Object Management Group (OMG) Object Constraint Language (OCL) 2.0,
  43. 43.
    Object Management Group (OMG) Systems Modeling Language (SysML),
  44. 44.
    Overmyer, S., Benoit, L., Owen, R.: Conceptual Modeling Through Linguistic Analysis Using LIDA. In: Proceedings of the 23rd International Conference on Software Engineering, ICSE 2001, pp. 401–410 (May 2001) Google Scholar
  45. 45.
    Pastor, O., España, S., Panach, J.I., Aquino, N.: Model-Driven Development: Piecing Together the MDA Jigsaw. Informatik-Spektrum. Special issue on Modeling 31(5), 394–407 (2008)CrossRefGoogle Scholar
  46. 46.
    Pastor, O., Gómez, J., Insfrán, E., Pelechano, V.: The OO-Method Approach for Information Systems Modeling: from Object-Oriented Conceptual Modeling to Automated Programming. Information Systems 26(7), 507–534 (2001)CrossRefGoogle Scholar
  47. 47.
    do Prado Leite, J.C.S., Hadad, G.D.S., Doorn, J.H., Kaplan, G.N.: A Scenario Construction Process. Requirements Engineering 5, 38–61 (2000)CrossRefGoogle Scholar
  48. 48.
    dos Santos Soares, M., Vrancken, J.L.M.: Model-Driven User Requirements Specification Using SysML. JSW 3(6), 57–68 (2008)Google Scholar
  49. 49.
    Sanyal, A., Choudhury, S.: An Object-Oriented Conceptual Level Design for Web Data Model. In: Proceeding of International Conference on Methods and Models in Computer Science, ICM2CS 2009, pp. 1–6 (2009)Google Scholar
  50. 50.
    Sanyal, A., Basu, S.S., Choudhury, S.: A Requirement Framework for Enablement of Automatic Generation of Domain Model. In: 2010 International Conference on Computer Information Systems and Industrial Management Applications (CISIM), pp. 359–364 (2010) Google Scholar
  51. 51.
    Schmidt, D.C.: Model-Driven Engineering. Computer 39, 25–31 (2006)CrossRefGoogle Scholar
  52. 52.
    Selic, B.: The Pragmatics of Model-Driven Development. IEEE Software 20, 19–25 (2003)CrossRefGoogle Scholar
  53. 53.
    da Silva, A.R., Saraiva, J., Ferreira, D., Silva, R., Videira, C.: Integration of RE and MDD Paradigms: The ProjectIT Approach and Tools. IET Software 1(6), 294–314 (2007)CrossRefGoogle Scholar
  54. 54.
    Sánchez, P., Magno, J., Fuentes, L., Moreira, A., Araújo, J.: Towards MDD transformations from AO requirements into AO architecture. In: Gruhn, V., Oquendo, F. (eds.) EWSA 2006. LNCS, vol. 4344, pp. 159–174. Springer, Heidelberg (2006)CrossRefGoogle Scholar
  55. 55.
    Valderas, P., Pelechano, V.: Introducing Requirements Traceability Support in Model-Driven Development of Web Applications. Information and Software Technology 51(4), 749–768 (2009)CrossRefGoogle Scholar
  56. 56.
    Wieringa, R.: TRADE: Techniques for Requirements and Design Engineering of Software Systems. Tech. rep., Computer Science Department, University of Twente, Enschede, The Netherlands (1999)Google Scholar
  57. 57.
    Winkler, S., Pilgrim, J.: A Survey of Traceability in Requirements Engineering and Model-Driven Development. Softw. Syst. Model. 9, 529–565 (2010)CrossRefGoogle Scholar
  58. 58.
    Yu, E.S.K.: Modelling Strategic Relationships for Process Reengineering, PhD Thesis, University of Toronto, Toronto, Canada (1995)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2011

Authors and Affiliations

  • Iyad Zikra
    • 1
  • Janis Stirna
    • 1
  • Jelena Zdravkovic
    • 1
  1. 1.Department of Computer and Systems SciencesStockholm UniversityKistaSweden

Personalised recommendations