A METHOD FOR BUSINESS CAPABILITY DEPENDENCY ANALYSIS

Andreas Freitag, Aneta Nowobilska, Christopher Schulz, Florian Matthes

Abstract

Business capabilities are a key element of a modern Enterprise Architecture Management (EAM) approach. They are the core component of a business architecture and essential for communication between business and IT. There is an enormous interest among academics and practitioners reflected in a growing number of publications on definition, use cases, and experiences from case studies. However, due to the innovative character of business capability approaches, many issues have not been subject to structured research yet. One topic that has not been addressed so far, is the analysis of dependencies between business capabilities, which is a crucial aspect for the integration of new business capabilities. This paper presents a three-phase method to systematically identify dependences between business capabilities and to other elements of the Enterprise Architecture (EA). We built this method on the assignment of the business entities to business capabilities. Based on existing visualizations, we developed a business entity map and an information ownership map to support the analysis. We applied a design science approach to develop the method which has been tested during application in the three companies. Additionally, we illustrate the method with a case study from the telecommunication industry.

References

  1. Aier, S., Riege, C., and Winter, R. (2008). Unternehmensarchitektur - Literaturüberblick und Stand der Praxis. Wirtschaftsinformatik, 50(4):292-304.
  2. Barker, I. (2005). What is information architecture? KM Column, (April).
  3. Barroero, T., Motta, G., and Pignatelli, G. (2010). Business Capabilities Centric Enterprise Architecture, volume 326, pages 32-43. Springer, Boston, USA.
  4. Bernard, S. A. (2005). An Introduction to Enterprise Architecture. AuthorHouse, Bloomington, USA, 2nd edition.
  5. Berneaud, M. (2009). Der Unterschied liegt in der IT. GIGeldinstitute, page 3.
  6. BOC-Group (2009). Business Capability Management.
  7. Bredemeyer, D., Malan, R., Krishnan, R., and Lafrenz, A. (2003). Enterprise Architecture as Business Capabilities Architecture.
  8. Brits, J.-P., Botha, G., and Herselman, M. (2007). Conceptual Framework for Modeling Business Capabilities. In Proceedings of the 2007 Informing Science and IT Education Joint Conference, pages 151-170.
  9. Buckl, S., Matthes, F., and Schweda, C. M. (2011). Information model building blocks.
  10. Cherbakov, L., Galambos, G., Harishankar, R., Kalyana, S., and Rackham, G. (2005). Impact of service orientation at the business level. IBM Systems Journal, 44(4):653-668.
  11. Cullen, A., Orlov, L. M., Radjou, N., Hoppermann, J., Peyret, H., and Sessions, L. (2006). Enterprise Architecture's Role In IT-Enabled Business Innovation.
  12. Dama International (2009). The DAMA Guide to The Data Management Body of Knowledge. Technics Publications, Bradley Beach, USA, 1st edition.
  13. Data Governance Institute (2010). Assigning Data Ownership.
  14. Engels, G., Hess, A., Humm, B., Juwig, O., Lohmann, M., Richter, J.-P., Voß, M., and Willkomm, J. (2008). Quasar Enterprise: Anwendungslandschaften serviceorientiert gestalten. Dpunkt Verlag, Heidelberg, Germany, 1st edition.
  15. Evernden, R. and Evernden, E. (2003). Third Generation Information Architecture. Communication of the ACM, 46(3):95-98.
  16. Freitag, A. and Helbig, R. (2009). Finanzplanung und steuerung von Unternehmensarchitekturen. Controlling-Portal.
  17. Giaglis, G. M. (2001). A taxonomy of business process modeling and information systems modeling tech ... International Journal of Flexible Manufacturing Systems, 13(2):209-228.
  18. Hevner, A. R., March, S. T., Park, J., and Ram, S. (2004). Design science in information systems research. MIS Quarterly, 28(1):75-105.
  19. Homann, U. (2006). A Business-Oriented Foundation for Service Orientation.
  20. International Organization For Standardization (2007). ISO/IEC 42010:2007 Systems and software engineering - Recommended practice for architectural description of software-intensive systems.
  21. Keller, W. (2006). IT-Unternehmensarchitektur. Von der Geschäftsstrategie zur optimalen IT-Unterstützung. Dpunkt Verlag, Heidelberg, Germany, 1st edition.
  22. Keller, W. (2009). Using Capabilities in Enterprise Architecture Management.
  23. Klinkmüller, C., Ludwig, A., Franczyk, B., and Kluge, R. (2010). Visualising Business Capabilities in the Context of Business Analysis, volume 47, pages 242-253. Springer, Berlin/Heidelberg, Germany.
  24. König, W., Beimborn, D., Martin, S. F., and Homann, U. (2005). Capability Map : Eine alternative Darstellungsweise für Unternehmensprozesse aus ressourcenorientierter Sicht. SCS-European Publishing House.
  25. Lankes, J., Matthes, F., and Wittenburg, A. (2005). Softwarekartographie als Beitrag zum Architekturmanagement, pages 305-330. GITO-Verlag.
  26. March, S. T. and Smith, G. F. (1995). Design and natural science research on information technology. Decision Support Systems, 15:251-266.
  27. Matthes, F., Buckl, S., Leitel, J., and Schweda, C. M. (2008). Enterprise Architecture Management Tool Survey 2008. Chair for Informatics 19 (sebis), Technische Universität München, München, Germany.
  28. McDavid, D. W. (1999). A standard for business architecture description. IBM Systems Journal, 38(1):12-31.
  29. Niemann, K. D. (2008). From Enterprise Architecture to IT Governance: Elements of Effective IT Management. Vieweg Verlag, Wiesbaden, Germany, 1st edition.
  30. Ross, J. W., Weill, P., and Roberts, D. C. (2006). Enterprise Architecture as Strategy: Creating a Foundation for Business Execution. Mcgraw-Hill Professional, 1st edition.
  31. Schöenherr, M. (2009). Towards a Common Terminology in the Discipline of Enterprise Architecture, pages 400- 413. Lecture Notes in Computer Science. Springer, Berlin, Heidelberg, Germany.
  32. Scott, J., Cullen, A., and An, M. (2010). The Anatomy Of A Capability Map.
  33. The Open Group (2009). TOGAF ”Enterprise Edition” Version 9.
  34. Toms, E. G. (2002). Information interaction: Providing a framework for information architecture. Journal of the American Society for Information Science and Technology, 53(10):855-862.
  35. Weber, U. and Schmidtmann, V. (2008). Differentiate. Der neue strategische Imperativ für den CIO.
  36. Webster, J. and Watson, R. T. (2002). Analyzing the Past to Prepare for the Future: Writing a Literature Review. MIS Quarterly, 26(2):xiii--xxiii.
  37. White, S. A. (2004). Introduction to BPMN. BP Trends.
Download


Paper Citation


in Harvard Style

Nowobilska A., Schulz C., Matthes F. and Freitag A. (2011). A METHOD FOR BUSINESS CAPABILITY DEPENDENCY ANALYSIS . In Proceedings of the Second International Conference on Innovative Developments in ICT - Volume 1: INNOV, ISBN 978-989-8425-67-6, pages 11-20. DOI: 10.5220/0004471100110020


in Bibtex Style

@conference{innov11,
author={Aneta Nowobilska and Christopher Schulz and Florian Matthes and Andreas Freitag},
title={A METHOD FOR BUSINESS CAPABILITY DEPENDENCY ANALYSIS},
booktitle={Proceedings of the Second International Conference on Innovative Developments in ICT - Volume 1: INNOV,},
year={2011},
pages={11-20},
publisher={SciTePress},
organization={INSTICC},
doi={10.5220/0004471100110020},
isbn={978-989-8425-67-6},
}


in EndNote Style

TY - CONF
JO - Proceedings of the Second International Conference on Innovative Developments in ICT - Volume 1: INNOV,
TI - A METHOD FOR BUSINESS CAPABILITY DEPENDENCY ANALYSIS
SN - 978-989-8425-67-6
AU - Nowobilska A.
AU - Schulz C.
AU - Matthes F.
AU - Freitag A.
PY - 2011
SP - 11
EP - 20
DO - 10.5220/0004471100110020