• Keine Ergebnisse gefunden

Patterns in Enterprise Architecture Management

N/A
N/A
Protected

Academic year: 2022

Aktie "Patterns in Enterprise Architecture Management"

Copied!
1
0
0

Wird geladen.... (Jetzt Volltext ansehen)

Volltext

(1)

Patterns in Enterprise Architecture Management (PEAM 2009)

Florian Matthes, Alexander Ernst Technische Universität München

{matthes,ernst}@in.tum.de

There is a growing interest in academia and industry to identify, collect, document and exchange best practices in the management of very large software application landscapes in a structured manner. This workshop addresses European researchers and practitioners with experience in enterprise architecture management topics. The goal of the workshop is to improve this knowledge exchange by using an integrating pattern-based approach.

An enterprise architecture management pattern (EAM pattern) is a general, reusable solution to a common problem in a given context which identifies driving forces, known usages and consequences. It can be specified on different levels of abstraction and detail, e.g. as a framework for enterprise architectures, as a method for enterprise modeling, or as a reference model. EAM patterns address social, technical and economic issues in a balanced manner.

17

Referenzen

ÄHNLICHE DOKUMENTE

Both, researchers and practitioners, argue that risk indicators will play an important role in risk management, since they provide direct information on the current risk situation

the university staff, who conducts the lecture, organizes, and evaluates the projects conducted at the industry partner, the practitioners from industry providing the problem to

Related Patterns: For the assignment of lifecycle states any of the aforementioned data acquisition/maintenance process patterns might be used. An example for applying this

It thus resolves the need for unified service provision with both the need for integrating legacy back-office applications and the organizational subdivision by having a separate

The software change project cost analysis pattern following the CompactForm [Tr09] in the current paper is built up using the following lynchpins; Problem for providing the

In this paper we have motivated the necessity to enrich today’s static EA models that focus on the static complexity arising from dependencies between the elements of the enter-

First, on request by the EA team, the respective data owner delivers updated model data of its specialized architecture as specified in the data delivery contract (activity 2)..

Thus, we propose several types of agent, namely, the enterprise agent representing an individual enterprise , the broker agent, which is the initiator of the VE (creation phase),