Extending enterprise architecture modelling with business goals and requirements

Enterprise Information Systems

Volumn 5, Issue 1, 2011, Pages 9-36

  Engelsmana, Wilco ^a,b   Quartelc, Dick ^c   Jonkersa, Henk ^a   van Sinderen, Marten ^b  

^a BiZZdesign   (Netherlands)

^b UNIVERSITY OF TWENTE   (Netherlands)

^c Novay   (Netherlands)

Author keywords

Business IT alignment; Enterprise architecture; Goal modelling; Requirements engineering; Stakeholder concerns

Indexed keywords

ANALYSIS TECHNIQUES; BUSINESS GOALS; BUSINESS-IT ALIGNMENT; ENTERPRISE ARCHITECTURE; ENTERPRISE MODELLING; GOAL MODELLING; MODELLING TECHNIQUES; OPEN GROUP ARCHITECTURE FRAMEWORKS; REQUIREMENTS MODELLING; STAKEHOLDER CONCERNS;

ALIGNMENT; ARCHITECTURE; HIGH LEVEL LANGUAGES; MOTIVATION; REQUIREMENTS ENGINEERING;

INDUSTRY;

EID: 78650298012     PISSN: 17517575     EISSN: 17517583     Source Type: Journal    
DOI: 10.1080/17517575.2010.491871     Document Type: Article

References (35)

1. Antón, A.I., 1996. Goal-based requirements analysis. In: Proceedings of the second international conference on requirements engineering. Washington, DC: IEEE Computer Society, 136-144.
2. Braun, C. and Winter, R., 2005. A comprehensive enterprise architecture metamodel and its implementation using a metamodeling platform. In: Proceedings of the workshop in enterprise modelling and information systems architectures. EMISA, 64-79.
3. Brooks, F., 1986. No silver bullet: essence and accidents of software engineering. IEEE Computer, 20 (4), 10-19.
4. Business Rules Group, 2008. The business motivation model - business governance in a volatile world [online]. Release 1.3. Available from: http://www.businessrulesgroup.org/bmm.shtml [Accessed 27 May 2010].
5. Dardenne, A., van Lamsweerde, A., and Fickas, S., 1993. Goal-directed requirements acquisition. Science of Computer Programming, 20, 3-50.
6. Dijkman, R.M., Quartel, D.A.C., and van Sinderen, M.J., 2008. Consistency in multiviewpoint design of enterprise information systems. Information and Software Technology (IST), 50 (7-8), 737-752.
7. Dietz, J., 2001. DEMO: towards a discipline of organization engineering. European Journal of Operational Research, 128 (2), 351-363.
8. Engelsman, W., et al. 2009. Architecture-driven requirements engineering. In: E. Proper, F. Harmsen, and J.L.G. Dietz, eds. Advances in enterprise engineering II, Volume 28 of lecture notes in business information processing. Berlin. Berlin, Heidelberg: Springer, 134-154.
9. Finkelstein, A., et al. 1991. Viewpoint oriented software development: methods and viewpoints in requirements engineering. Lecture Notes in Computer Science, 490, 29-54.
10. Gordijn, J., Yu, E., and van der Raadt, B., 2006. e-Service Design using i* and e3 value modeling. IEEE Software, 23 (3), 26-33.
11. ISO, 1998. ISO/IEC 10746-3. The information technology - open distributed processing - reference model: architecture. Geneva: ISO.
12. ISO, 2007. ISO/IEC 42010. Systems and software engineering - recommended practice for architectural description of software-intensive systems. Geneva: ISO.
13. Jacobson, I., 1995. The use-case construct in object-oriented software engineering. In: J.M. Carroll, ed. Scenario-based design: envisioning work and technology in system development. New York: John Wiley & Sons, 309-338.
14. Jonkers, H., et al. 2004. Concepts of modeling enterprise architectures. International Journal of Cooperative Information Systems, 13, 257-287.
15. Kurpjuweit, S. and Winter, R., 2009. Concern-oriented business architecture engineering. In: Proceedings of 24th annual ACM symposium on applied computing (SAC), Honolulu, Hawaii, New York: ACM, 265-272.
16. Lagerström, R., et al. 2009. Enterprise meta modeling methods - combining a stakeholderoriented and a causality-based approach. In: T. Halpin and et al., eds. Enterprise, businessprocess and information systems modeling. Lecture notes in business information processing, Berlin/Heidelberg: Springer, 381-393.
17. Lankhorst, M., et al. 2005. Enterprise architecture at work: modelling, communication and analysis. New York: Springer.
18. Lindstrom, A., 2006. On the syntax and semantics of architectural principles. In: Proceedings of the 39th Hawaii international conference on system sciences. Washington, DC: IEEE Computer Society.
19. Mulholland, A. and Macaulay, A.L., 2006. Architecture and the integrated architecture framework. Capgemini: White Paper.
20. Nuseibeh, B., Kramer, J., and Finkelstein, A., 1994. A framework for expressing the relationships between multiple views in requirements specifications. IEEE Transactions on Software Engineering, 20 (10), 760-773.
21. Op't Land, M. and Proper, H.A., 2007. Impact of principles on enterprise engineering. In: H. Österle, J. Schelp, and R. Winter, eds. Proceedings of the 15th European conference on information systems. St Gallen, Switzerland: University of St Gallen.
22. Respect-IT, 2007. A KAOS tutorial, V1.0 [online]. Available from: http://www.objectiver.com/fileadmin/download/documents/KaosTutorial.pdf [Accessed 27 May 2010].
23. Samavi, R., Yu, E., and Topaloglou, T., 2008. Strategic reasoning about business models: a conceptual modeling approach. Information Systems and E-Business Management, 7 (2), 1-28.
24. Schoman, K. and Ross, D.T., 1977. Structured analysis for requirements definition. IEEE Transactions on Software Engineering, 3 (1), 363-386.
25. Sommerville, I., Sawyer, P., and Viller, S., 1998. Viewpoints for requirements elicitation: a practical approach. In: Proceedings of the third IEEE international conference on requirements engineering (ICRE 98). Washington, DC: IEEE Computer Society, 74-81.
26. Sowa, J.F. and Zachman, J.A., 1992. Extending and formalizing the framework for information systems architecture. IBM Systems Journal, 31 (3), 590.
27. Sparx Systems, 2008. MDG technology for Zachman framework user guide [online]. Available from: http://www.sparxsystems.com.au/downloads/pdf/ZFUserGuide.pdf [Accessed 27 May 2010].
28. Stelzer, D., 2009. Enterprise architecture principles: literature review and research directions. In: S. Aier, J. Schelp, and M. Schö nherr, eds. Pre-proceedings of the 4th workshop on trends in enterprise architecture research, Stockholm, Sweden, 23 November 2009, 21-35.
29. van Bommel, P., et al. 2007. Architecture principles - a regulative perspective on enterprise architecture. In: M. Reichert, S. Strecker, and K. Turowski, eds. Enterprise modelling and information systems architectures (EMISA2007), no. 119 in lecture notes in informatics. Bonn, Germany: Gesellschaft fur Informatik, 47-60.
30. van Lamsweerde, A., 2000. Requirements engineering in the year 00: a research perspective. In: ICSE 000: proceedings of the 22nd international conference on Software engineering. New York, NY, USA:ACM Press, 5-19.
31. van Lamsweerde, A., 2001. Goal oriented requirements engineering: a guided tour. In: Proceedings of the 5th IEEE international symposium on requirements engineering (RE 2001). Washington, DC: IEEE Computer Society, 249-262.
32. van Lamsweerde, A., Darimont, R., and Letier, E., 1998. Managing conflicts in goal-driven requirements engineering. IEEE Transactions on Software Engineering. Special Issue on Inconsistency Management in Software Development, 24 (11), 908-926.
33. Wieringa, R., 2004. Requirements engineering: problem analysis and solution specification [extended abstract]. Lecture Notes in Computer Science, 3140, 13-16.
34. Yu, E., 1997. Towards modelling and reasoning support for early-phase requirements engineering. In: Proceedings of the 3rd IEEE international symposium on requirements engineering (RE097), 6-8 January. Washington, DC: IEEE Computer Society, 226-235.
35. Yu, E., Strohmaier, M., and Deng, X., 2006. Exploring intentional modeling and analysis for enterprise architecture. In: Proceedings of the EDOC 2006 workshop on trends in enterprise architecture research (TEAR 2006). Washington, DC: IEEE Computer Society.