<?xml version="1.0" encoding="UTF-8"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
<title>EMISAJ Vol. 02 - 2007</title>
<link href="http://dl.gi.de/handle/20.500.12116/3471" rel="alternate"/>
<subtitle/>
<id>http://dl.gi.de/handle/20.500.12116/3471</id>
<updated>2026-07-21T14:21:26Z</updated>
<dc:date>2026-07-21T14:21:26Z</dc:date>
<entry>
<title>Integrating Architectural Models - Symbolic, Semantic and Subjective Models in Enterprise Architecture</title>
<link href="http://dl.gi.de/handle/20.500.12116/3485" rel="alternate"/>
<author>
<name>Arbab, Farhad</name>
</author>
<author>
<name>de Boer, Frank</name>
</author>
<author>
<name>Bonsangue, Marcello</name>
</author>
<author>
<name>Lankhorst, Marc</name>
</author>
<author>
<name>Proper, Erik</name>
</author>
<author>
<name>van der Torre, Leendert</name>
</author>
<id>http://dl.gi.de/handle/20.500.12116/3485</id>
<updated>2017-09-15T09:26:16Z</updated>
<published>2007-01-01T00:00:00Z</published>
<summary type="text">Integrating Architectural Models - Symbolic, Semantic and Subjective Models in Enterprise Architecture
Arbab, Farhad; de Boer, Frank; Bonsangue, Marcello; Lankhorst, Marc; Proper, Erik; van der Torre, Leendert
The diversity of architectural models in enterprise architecture poses a problem to their integration. Without such integration the effectiveness of these models in the process of architecting enterprises diminishes. In this paper we make a distinction between three classes of models. We will illustrate how the distinctions can be used for model integration within the architectural approach. Symbolic models express properties of architec-tures of systems, semantic models interpret the symbols used in symbolic models, and subjective models are purposely abstracted conceptions of a domain. Building on results obtained in the ArchiMate project, we il-lustrate how symbolic models can be integrated using an architectural language, how integrated models can be updated using the distinction between symbolic models and their visualization, and how semantic models can be integrated using a new kind of enterprise analysis called semantic analysis.
</summary>
<dc:date>2007-01-01T00:00:00Z</dc:date>
</entry>
<entry>
<title>Modelling of Cross-Organizational Business Processes - Current Methods and Standards</title>
<link href="http://dl.gi.de/handle/20.500.12116/3489" rel="alternate"/>
<author>
<name>Ziemann, Jörg</name>
</author>
<author>
<name>Matheis, Thomas</name>
</author>
<author>
<name>Freiheit, Jörn</name>
</author>
<id>http://dl.gi.de/handle/20.500.12116/3489</id>
<updated>2017-08-28T18:53:05Z</updated>
<published>2007-01-01T00:00:00Z</published>
<summary type="text">Modelling of Cross-Organizational Business Processes - Current Methods and Standards
Ziemann, Jörg; Matheis, Thomas; Freiheit, Jörn
Not only since the upcoming of Service-oriented Architectures the modelling of cross-organizational business processes is a heavily investigated field comprising dozens of standards based on different concepts. New techniques on the implementation site, e.g. Web Service orchestration and choreography, further extended the possibilities and requirements on such standards. To systematically order and present a comprehensive state of the art of relevant methods and standards this paper first describes requirements that occur in cross-organizational business processes both for concepts and modelling languages. Then the most important state of the art concepts for modelling cross-organizational processes are described. Based on the requirements defined before and the presented concepts, selected modelling languages are analysed.
</summary>
<dc:date>2007-01-01T00:00:00Z</dc:date>
</entry>
<entry>
<title>Generating Visualizations of Enterprise Architectures using Model Transformations</title>
<link href="http://dl.gi.de/handle/20.500.12116/3487" rel="alternate"/>
<author>
<name>Buckl, Sabine</name>
</author>
<author>
<name>Ernst, Alexander M.</name>
</author>
<author>
<name>Lankes, Josef</name>
</author>
<author>
<name>Matthes, Florian</name>
</author>
<author>
<name>Schweda, Christian M.</name>
</author>
<author>
<name>Wittenburg, André</name>
</author>
<id>http://dl.gi.de/handle/20.500.12116/3487</id>
<updated>2017-08-28T18:53:05Z</updated>
<published>2007-01-01T00:00:00Z</published>
<summary type="text">Generating Visualizations of Enterprise Architectures using Model Transformations
Buckl, Sabine; Ernst, Alexander M.; Lankes, Josef; Matthes, Florian; Schweda, Christian M.; Wittenburg, André
Giving account to the importance of enterprise architecture (EA) modeling, we identify issues in visualization handling that we came across during an extensive survey of existing tools for EA management. We then point to the fundamental principles of software cartography, an approach for EA modeling, including a method for the automatic creation of visualizations based on EA models. This approach is based on model transformations, which link the data to be visualized and their graphical representation, thereby circumventing the error-prone and time-consuming task of manual creation of the visual models. A brief overview of a prototypic implementation of this approach illustrates the practical applicability for visual modeling and documenting EA.
</summary>
<dc:date>2007-01-01T00:00:00Z</dc:date>
</entry>
<entry>
<title>A Federated Approach to Enterprise Architecture Model Maintenance</title>
<link href="http://dl.gi.de/handle/20.500.12116/3488" rel="alternate"/>
<author>
<name>Fischer, Ronny</name>
</author>
<author>
<name>Aier, Stephan</name>
</author>
<author>
<name>Winter, Robert</name>
</author>
<id>http://dl.gi.de/handle/20.500.12116/3488</id>
<updated>2017-08-28T18:53:05Z</updated>
<published>2007-01-01T00:00:00Z</published>
<summary type="text">A Federated Approach to Enterprise Architecture Model Maintenance
Fischer, Ronny; Aier, Stephan; Winter, Robert
Enterprise architecture is gaining acceptance as an approach to manage change and foster IT/business alignment by (1) propagating strategy and process changes to the software and infrastructure level, by (2) supporting consistent business transformation enabled by technology innovations, and by (3) decoupling business-oriented and technology-oriented architectures. Due to constant change in business as well as in technology, enterprise architecture management is a permanent process rather than a one-time effort. To keep enterprise architecture models up-to-date, a well-engineered maintenance concept including processes, roles and schedules is needed. This paper discusses the shortcomings of existing approaches to enterprise architecture model maintenance, proposes a federated approach, and reports on its implementation at a large financial service provider.
</summary>
<dc:date>2007-01-01T00:00:00Z</dc:date>
</entry>
</feed>
