REQUIREMENTS FOR AUTOMATED ENTERPRISE ARCHITECTURE MODEL MAINTENANCE - A Requirements Analysis based on a Literature Review and an Exploratory Survey

Matthias Farwick, Berthold Agreiter, Ruth Breu, Steffen Ryll, Karsten Voges, Inge Hanschke

2011

Abstract

Enterprise Architecture Management (EAM) is the practice of modeling the business and IT artifacts in an enterprise and relating them with each other. By documenting these interdependencies between business and the supporting IT, strategic decisions can be made towards a planned and consolidated enterprise architecture that matches the business needs. However, enterprise architecture models can grow very large, thus making the manual creation and maintenance of these models a difficult and time consuming task. From this, we derived the three research questions of this paper: (i) Which related work exists on the maintenance of EA models, and does it refer to automation techniques? (ii) Is EA maintenance automation demanded by practitioners? If yes, (iii) What are the requirements for such an automation method and tool? In this paper we tackle these questions by conducting a literature analysis on EA literature from research and practice. In addition, we present the results of a survey among EA practitioners we conducted to find out current maintenance practices. We then describe a collection of requirements for an automated EA maintenance method and tool, that we derived from the results of the survey, the findings in the literature review and our own experience as EA consultants. Finally, we present several success evaluation criteria for an automated EA maintenance solution.

References

  1. Ambler, S. W. (2010). Enterprise architecture survey results. http://www.ambysoft.com/surveys/stateOfITUn Breu, R. (2010). Ten principles for living models - a manifesto of change-driven software engineering. In 4th International Conference on Complex, Intelligent and Software Intensive Systems (CISIS-2010).
  2. Buckl, S., Dierl, T., Matthes, F., Ramacher, R., and Schweda, C. (2008). Current and future tool support for ea management. In Proceedings of Workshop MDD, SOA und IT-Management (MSI 2008), Oldenburg, Gito.
  3. Buckl, S., Ernst, A., Matthes, F., and Schweda, C. (2009a). An information model for managed application landscape evolution. Journal of Enterprise Architecture, 5(1):12-26.
  4. Buckl, S., Ernst, A. M., Lankes, J., Matthes, F., and Schweda, C. M. (2009b). State of the art in enterprise architecture management. Technical report, Chair for Informatics 19, Technical University Munich, Germany.
  5. Buckl, S., Matthes, F., and Schweda, C. M. (2010). Future Research Topics in Enterprise Architecture Management-A Knowledge Management Perspective, pages 1-11. Springer.
  6. Chief Information Officers Council (2007). FEA Consolidated Reference Model Document Version 2.3.
  7. Dam, H. K., Le, L.-S., and Ghose, A. (2010). Supporting change propagation in the evolution of enterprise architectures. In 2010 14th IEEE International Enterprise Distributed Object Computing Conference, pages 24-33. IEEE.
  8. De Boer, F.S., Bonsangue, M., Groenewegen, L., Stam, A., Stevens, S., and Van Der Torre, L. (2005). Change impact analysis of enterprise architectures. In Information Reuse and Integration, Conf, 2005. IRI-2005 IEEE International Conference on., pages 177-181. IEEE.
  9. DMTF (2010). Configuration management database (cmdb) federation specification - dsp0252 1.0.1.
  10. Farwick, M., Agreiter, B., Breu, R., Ha andring, M., Voges, K., and Hanschke, I. (2010). Towards living landscape models: Automated integration of infrastructure cloud in enterprise architecture management. In Cloud Computing (CLOUD), 2010 IEEE 3rd International Conference on, pages 35-42.
  11. Fischer, R., Aier, S., and Winter, R. (2007). A federated approach to enterprise architecture model maintenance. Enterprise Modelling and Information Systems Architectures, 2(2):14-22.
  12. Hafner, M. and Winter, R. (2008). Processes for enterprise application architecture management. In Hawaii International Conference on System Sciences, Proceedings of the 41st Annual. IEEE.
  13. Hanschke, I. (2009). Strategic IT Management: A Toolkit for Enterprise Architecture Management. Springer.
  14. IEEE Computer Society (2000). Ieee recommended practice for architectural description of software intensive systems (ieee std 1471-2000).
  15. Konstantinou, A. and Yemini, Y. (2009). A2A: An architecture for autonomic management coordination. Integrated Management of Systems, Services, Processes and People in IT, pages 85-98.
  16. Kumar, A., Raghavan, P., Ramanathan, J., and Ramnath, R. (2008). Enterprise interaction ontology for change impact analysis of complex systems. In 2008 IEEE AsiaPacific Services Computing Conference, pages 303- 309. Ieee.
  17. Lankhorst, M. (2005). Enterprise Architecture at Work: Modelling, Communication and Analysis. Springer, Berlin.
  18. Moser, C., Junginger, S., Brückmann, M., , and Schöne, K. (2009). Some process patterns for enterprise architecture management. In Proceedings, Workshop on Patterns in Enterprise Architecture Management (PEAM2009), Bonn, pages 19-30.
  19. OGC (2007). ITIL Lifecycle Publication Suite Books, 2nd impression. TSO.
  20. Saat, J., Winter, R., Franke, U., Lagerstroem, R., and Ekstedt, M. (2011). Analysis of it/business alignment situations as a precondition for the design and engineering of situated it/business alignment solutions. In Proc. Hawaii International Conference on System Sciences (HICSS-44).(January 2011).
  21. Tanner, A. and Feridun, M. (2009). Fusio: Semantic integration of systems management and enterprise information. Technical report, IBM Research GmbH Zurich Research Laboratory.
  22. ter Doest, H. and Lankhorst, M. (2004). Tool support for enterprise architecture-a vision. Technical report, Telematica Instituut, Enschede.
  23. The Open Group (2009). The Open Group Architecture Framework (TOGAF) version 9.
  24. US Department of Defense (2010). The DoDAF Architecture Framework Version 2.02.
  25. Wilson, C. (2010). Gartner - magic quadrant for enterprise architecture tools.
  26. Winter, K., Buckl, S., Matthes, F., and Schweda, C. (2010). Investigating the state-of-the-art in enterprise architecture management methods in literature and practice. In MCIS 2010 Proceedings.
  27. Winter, R. and Fischer, R. (2007). Essential layers, artifacts, and dependencies of enterprise architecture. Journal of Enterprise Architecture, pages 1-12.
  28. Zachman, J. A. (1987). A framework for information systems architecture. IBM Systems Journal, 26(3):276- 292.
Download


Paper Citation


in Harvard Style

Farwick M., Agreiter B., Breu R., Ryll S., Voges K. and Hanschke I. (2011). REQUIREMENTS FOR AUTOMATED ENTERPRISE ARCHITECTURE MODEL MAINTENANCE - A Requirements Analysis based on a Literature Review and an Exploratory Survey . In Proceedings of the 13th International Conference on Enterprise Information Systems - Volume 4: ICEIS, ISBN 978-989-8425-56-0, pages 325-337. DOI: 10.5220/0003429203250337


in Bibtex Style

@conference{iceis11,
author={Matthias Farwick and Berthold Agreiter and Ruth Breu and Steffen Ryll and Karsten Voges and Inge Hanschke},
title={REQUIREMENTS FOR AUTOMATED ENTERPRISE ARCHITECTURE MODEL MAINTENANCE - A Requirements Analysis based on a Literature Review and an Exploratory Survey},
booktitle={Proceedings of the 13th International Conference on Enterprise Information Systems - Volume 4: ICEIS,},
year={2011},
pages={325-337},
publisher={SciTePress},
organization={INSTICC},
doi={10.5220/0003429203250337},
isbn={978-989-8425-56-0},
}


in EndNote Style

TY - CONF
JO - Proceedings of the 13th International Conference on Enterprise Information Systems - Volume 4: ICEIS,
TI - REQUIREMENTS FOR AUTOMATED ENTERPRISE ARCHITECTURE MODEL MAINTENANCE - A Requirements Analysis based on a Literature Review and an Exploratory Survey
SN - 978-989-8425-56-0
AU - Farwick M.
AU - Agreiter B.
AU - Breu R.
AU - Ryll S.
AU - Voges K.
AU - Hanschke I.
PY - 2011
SP - 325
EP - 337
DO - 10.5220/0003429203250337