Concepts for Modeling Enterprise Architectures

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.

Landscape Maps for Enterprise Architectures

“…We propose to use landscape maps as a presentation format (modality) of enterprise architecture models expressed in the ArchiMate language [5,6]. However, our approach is not restricted to this particular modeling language.…”

Role of Semantic Web in the Changing Context of Enterprise Collaboration

“…The information is generally stored in a shared resource repository, consisting of massive information resources (e.g., electronic documents, multimedia data and so on) and processed and managed by multiple information systems providing relevant services and functionalities (Jonkers, et al 2004). However during the termination stage of a virtual enterprise, the shared information is no longer needed in its shared form.…”

Applying Enterprise Architecture to Business Networks

“…In practice these domains are mostly not approached in an integrated way. Every domain speaks its own language, draws its own models, and uses its own techniques and tools [Jonkers et al, 2004].…”

“…Applying any type of these management mechanisms requires an indispensable integrated approach to business and IT [Jonkers et al, 2004]. For example, adopting a certain type of management can require defining additional business processes, assigning new roles or deploying new resources.…”

“…Österle et al [2001] identified aspects of the business layer which capture organizational knowledge through organization resources, roles, processes and services. However, some of these artifacts, such as internal having full access to all involved organizational artifacts in the business networks in order to make them transparent to both internal and external stakeholders [Jonkers et al, 2004].…”