Enterprise architecture modelling—the issue of integration
Introduction
In current business practice, an integrated approach to business and IT is indispensable. Take for example a company that needs to assess the impact of introducing a new product in its portfolio. This may require defining additional business processes, hiring extra personnel, changing the supporting applications, and augmenting the technological infrastructure to support the additional load of these applications. Perhaps this may even require a change of the organisational structure.
Transferring new information technology to practice requires that a company has a clear, integrated vision on the relation between its business and IT. Without such a vision, the IT infrastructure will never adequately support the business, and vice versa, the business will not optimally profit from IT developments. A vast amount of literature has been written on the topic of strategic alignment, underlining the significance of both ‘soft’ and ‘hard’ components of an organisation [12], for example, distinguish between organisational strategy and organisational infrastructure on the one hand, and IT strategy and IT infrastructure on the other hand. Achieving alignment between business and IT requires an integrated approach to all aspects of the enterprise. Organisational effectiveness is not obtained by local optimisations, but is realised by well-orchestrated interaction of organisational components [27].
Enterprise architecture is an important instrument to address this company-wide integration. It is a coherent whole of principles, methods and models that are used in the design and realisation of the enterprise's organisational structure, business processes, information systems, and infrastructure [1]. However, in practice, these domains are not approached in an integrated way. Every domain speaks its own language, draws its own models, and uses its own techniques and tools. Communication and decision making across domains is seriously impaired. Although some commercially available tools provide the comprehensive functionality needed to develop and maintain enterprise architecture [11], in general tools provide partial support, do not integrate with other tools and cannot be sufficiently configured for the enterprise's context [13].
To create such an integrated perspective on enterprise architecture, one needs both a description technique for architectural models and tool support to realise this in practice. It would not be realistic to suppose that companies will throw their existing design practice and tools overboard and replace these by an entirely new approach. Rather, enterprise modelling should focus on bringing together already existing techniques and integrating these at the appropriate level of abstraction.
In this paper, we present an enterprise modelling language that captures the complexity of architectural domains and their relations, and we describe the design of an integrated enterprise architecture workbench that acts both as a modelling environment for this language and as an infrastructure for integrating with existing modelling languages and tools. These results stem from the ArchiMate project, an applied research project on enterprise architecture (http://archimate.telin.nl).
Section snippets
The ArchiMate modelling language
In many modern ICT-intensive organisations, several types of architects and architectures can be found. The technical ICT-related disciplines already have a somewhat longer architectural tradition, although the distinction between architecture and design is not always sharp. Application architects, for example, describe the relations between the many software applications used within the enterprise, as well as the global internal structure of these applications. Presently, the Unified Modelling
The ArchiMate workbench for model integration
To provide architects with concrete support in modelling and integrating enterprise architectures, a modelling language is not enough. The next step we have taken is to provide a software architecture and prototype for a workbench for the enterprise architect that acts both as a modelling environment for the ArchiMate language and as an infrastructure for integrating with existing modelling languages and tools [24]. First, we present a number of tool integration aspects. Next, we show the
Related work
A wide variety of organisation and process modelling languages are currently in use. The conceptual domains that are covered differ from language to language. In many languages, the relations between domains are not clearly defined. Some of the most popular languages are proprietary to a specific software tool. Relevant languages in this category include the ebXML set of standards for XML-based electronic business [47], developed by OASIS and UN/CEFACT, IDEF [14], originating from the US
Conclusions and future work
In this paper we have outlined both a language and an integration workbench for modelling enterprise architectures. The modelling language brings together the many separate architectural descriptions for specific architectural domains. Since separate languages and their corresponding approaches are deeply embedded in organisations, it is not recommendable to develop an entirely new language. Therefore, our new language builds upon successful and widely adopted languages such as UML.
The concepts
Acknowledgements
This paper results from the ArchiMate project (http://archimate.telin.nl/), a research initiative that aims to provide concepts and techniques to support enterprise architects in the visualisation, communication and analysis of integrated architectures. The ArchiMate consortium consists of ABN AMRO, Stichting Pensioenfonds ABP, the Dutch Tax and Customs Administration, Ordina, Telematica Instituut, Centrum voor Wiskunde en Informatica, Katholieke Universiteit Nijmegen, and the Leiden Institute
References (30)
- et al.
Handbook on enterprise architecture
(2003) - et al.
The unified modeling language user guide
(1999) - Creasy PN, Ellis, G.A Conceptual graph approach to conceptual schema integration. In: Proceedings of the ICCS'93,...
- Eertink H, Janssen W, Oude Luttighuis P, Teeuw W, Vissers C.A Business process design language. In: Proceedings of the...
- et al.
Business modeling with UML: business patterns at work
(2000) Model driven architecture: applying MDA to enterprise computing
(2003)- et al.
Design patterns: elements of reusable object-oriented software
(1995) - Garlan D, Monroe RT, Wile D. ACME: an architecture description interchange language. In: Proceedings of the CASCON '97,...
Selecting architecture modeling tools
(2003)- et al.
Strategic alignment: leveraging information technology for transforming organizations
IBM Syst J
(1993)
Integration definition for function modeling (IDEF0) draft
IEEE Std 1471-2000: IEEE recommended practice for architectural description of software-intensive systems
Information technology—open distributed processing—reference model–enterprise language
Cited by (128)
Digital transformation of agriculture: A new integrated modeling framework for arable farm enterprises
2023, Computers and Electronics in AgricultureCriteria for selecting an Enterprise Modelling Method Students’ Perspectives on ArchiMate and 4EM
2023, Enterprise Modelling and Information Systems ArchitecturesThe Use of Unmanned Aerial Vehicles in Healthcare Logistic: Risks and Opportunities
2023, Lecture Notes on Data Engineering and Communications TechnologiesStrategic alignment of enterprise architecture management–how portfolios of control mechanisms track a decade of enterprise transformation at Commerzbank
2023, European Journal of Information SystemsConcepts for Modeling Smart Cities: An ArchiMate Extension
2022, Business and Information Systems Engineering