Architecture-Driven Requirements Engineering

  • Wilco Engelsman
  • Henk Jonkers
  • Henry M. Franken
  • Maria-Eugenia Iacob
Part of the Lecture Notes in Business Information Processing book series (LNBIP, volume 28)


This paper presents an architecture driven requirements engineering method. We will demonstrate how to integrate requirements engineering in architecture design and we will demonstrate how to use enterprise architectures during solution realization projects. We will demonstrate how architecture can be used during problem investigation, solution specification and solution validation through an example application.


Requirements Engineering Goal Oriented Requirements Engineering Enterprise Architecture 


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Anton, A.I.: Goal-based requirements analysis. In: Proceedings of the Second International Conference on Requirements Engineering, pp. 136–144 (1996)Google Scholar
  2. 2.
    Aurum, A., Wohlin, C.: Engineering And Managing Software Requirements. Springer, Heidelberg (2005)CrossRefGoogle Scholar
  3. 3.
    Bray, I.K.: An Introduction to Requirements Engineering. Addison-Wesley, Reading (2002)Google Scholar
  4. 4.
    Bresciani, P., Perini, A., Giorgini, P., Giunchiglia, F., Mylopoulos, J.: Tropos: An agent-oriented software development methodology. Autonomous Agents and Multi-Agent Systems 8(3), 203–236 (2004)CrossRefGoogle Scholar
  5. 5.
    Cross, N.: Strategic knowledge exercised by outstanding designers. Strategic knowledge and concept formation III, pp. 17–30 (2001)Google Scholar
  6. 6.
    Iacob, M.E., Franken, H., Van den Berg, H.: Enterprise Architecture Handbook. Bizzdesign academy publishers (2007)Google Scholar
  7. 7.
    Jackson, M.: Software requirements & specifications: a lexicon of practice, principles and prejudices (1995)Google Scholar
  8. 8.
    Jacobson, I.: The use-case construct in object-oriented software engineering. Scenario-based Design: Envisioning Work and Technology in System Development, 309–338 (1995)Google Scholar
  9. 9.
    Jonkers, H., van Burren, R., Arbab, F., de Boer, F., Bonsangue, M., Bosma, H., ter Doest, H., Groenewegen, L., Scholten, J.G., Hoppenbrouwers, S., et al.: Towards a language for coherent enterprise architecture descriptions. In: Proceedings of Seventh IEEE International Enterprise Distributed Object Computing Conference, 2003, pp. 28–37 (2003)Google Scholar
  10. 10.
    Kotonya, G., Sommerville, I.: Requirements engineering with viewpoints. Software Engineering Journal 11(1), 5–18 (1996)CrossRefGoogle Scholar
  11. 11.
    Lankhorst, M.: Enterprise Architecture at Work: Modelling, Communication and Analysis. Springer, Heidelberg (2005)Google Scholar
  12. 12.
    Luipers, J.: White paper project start architectuur (in dutch). Sogeti internal reportGoogle Scholar
  13. 13.
    Mulholland, A., Macaulay, A.L.: Architecture and the integrated architecture framework. Whitepaper, Capgemini,
  14. 14.
    Samavi, R., Yu, E., Topaloglou, T.: Strategic reasoning about business models: a conceptual modeling approach. Information Systems and E-Business Management, pp. 1–28Google Scholar
  15. 15.
    Schoman, K., Ross, D.T.: Structured Analysis for requirements definition. IEEE Trans. on Software Engineering 3(1) (1977)Google Scholar
  16. 16.
    Sommerville, I., Sawyer, P., Viller, S.: Viewpoints for requirements elicitation: a practical approach. In: Proc. Third IEEE International Conference on Requirements Engineering (ICRE 1998) (1998)Google Scholar
  17. 17.
    The Standish The Open Group. TogafTM version 8.1.1 enterprise edition (2006),
  18. 18.
    van Lamsweerde, A.: Goal-oriented requirements engineering: a roundtrip form research to practice. In: Proceedings of 12th IEEE International Requirements Engineering Conference, 2004, pp. 4–7 (2004)Google Scholar
  19. 19.
    van Lamsweerde, A., Letier, E.: From object orientation to goal orientation: A paradigm shift for requirements engineering. In: Wirsing, M., Knapp, A., Balsamo, S. (eds.) RISSEF 2002. LNCS, vol. 2941, pp. 325–340. Springer, Heidelberg (2004)CrossRefGoogle Scholar
  20. 20.
    Wieringa, R.: Requirements Engineering: Frameworks for Understanding. Wiley, Chichester (1996)Google Scholar
  21. 21.
    Wieringa, R.: Requirements engineering: Problem analysis and solution specification (extended abstract). In: Koch, N., Fraternali, P., Wirsing, M. (eds.) ICWE 2004. LNCS, vol. 3140, pp. 13–16. Springer, Heidelberg (2004)CrossRefGoogle Scholar
  22. 22.
    Wieringa, R., Heerkens, H.: Requirements engineering as problem analysis: Methodology and guidelines. Technical report, University of Twente (2003)Google Scholar
  23. 23.
    Yu, E., Strohmaier, M., Deng, X.: Exploring Intentional Modeling and Analysis for Enterprise Architecture (2006)Google Scholar
  24. 24.
    Yu, E.S.K., Mylopoulos, J.: Understanding why in software process modelling, analysis, and design, pp. 159–168 (1994)Google Scholar
  25. 25.
    Zachman, J.A.: Enterprise Architecture: The Issue of the Century. Database Programming And Design 10, 44–53 (1997)Google Scholar
  26. 26.
    Zachman, J.A.: A Framework for Information Systems Architecture. IBM Systems Journal 38(2/3), 454–470 (1999)CrossRefGoogle Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2009

Authors and Affiliations

  • Wilco Engelsman
    • 1
  • Henk Jonkers
    • 1
  • Henry M. Franken
    • 1
  • Maria-Eugenia Iacob
    • 2
  1. 1.BiZZdesignEnschedethe Netherlands
  2. 2.School of Management and GovernanceUniversity of TwenteEnschedethe Netherlands

Personalised recommendations