CONCEPTS FOR MODELING ENTERPRISE ARCHITECTURES

Henk Jonkers, Marc Lankhorst, R. van Buuren, Stijn Hoppenbrouwers, Marcello Bonsangue, Leendert van der Torre

International Journal of Cooperative Information Systems · 2004 · 171 citations · 6 references

Concepts

TL;DR

Enterprise architecture descriptions provide insight, enable stakeholder communication, and guide complex change processes, yet no unified description language exists because each domain uses distinct modeling techniques, tools, and visualizations. The paper outlines an integrated enterprise architecture description language and studies concepts linking architectural domains. The language centers on concepts linking business, application, and technology levels—using services to relate behavioral aspects, interfaces to connect structural aspects, and realization relations for information aspects—while conforming to existing standards such as UML.

Abstract

A coherent description of enterprise architecture provides insight, enables communication among stakeholders and guides complicated change processes. Unfortunately, so far no enterprise architecture description language exists that fully enables integrated enterprise modeling, because for each architectural domain, architects use their own modeling techniques and concepts, tool support, visualization techniques, etc. In this paper, we outline such an integrated language and we identify and study concepts that relate architectural domains. In our language, concepts for describing the relationships between architecture descriptions at the business, application, and technology levels play a central role, related to the ubiquitous problem of business-ICT alignment, whereas for each architectural domain we conform to existing languages or standards such as UML. In particular, usage of services offered by one layer to another plays an important role in relating the behaviour aspects of the layers. The structural aspects of the layers are linked through the interface concept, and the information aspects through realization relations.

References

6