No abstract

After a period where implementation speed was more important than integration, consistency and reduction of complexity, architectural considerations have become a key issue of information management in recent years again. Being a traditional area of architecture models and architecture management, IT architecture has been extended by additional coverage and additional applications (like IT/business alignment) to develop into enterprise architecture (EA). EA is now widely accepted as an essential mechanism for ensuring transparency, consistency, compliance and ultimately flexibility/agility in companies and public agencies.Although standardization efforts (e.g. Open Group's TOGAF) and regulations (e.g. Clinger-Cohen Act of the U.S.A.) contribute to a growing common body of knowledge about EA models, EA applications and EA management, there is still a considerable amount of debate in academia as well as in practice. A wide range of potential EA application scenarios, EA project types, EA management goals, EA scope, and EA modeling approaches leads to a plethora of different proposals and case experiences.Regarding EA modeling, the variety of artifacts from business to software and IT infrastructure leads to a different understanding which artifacts, attributes and dependencies should be represented using which meta models on which level of detail. Regarding EA applications, it is not clear yet which EA scenarios result from a company's (or agency's) EA context and EA goals, and how the respective EA representations should be systematically engineered in a certain scenario. Regarding R. Winter

No abstract

No abstract

No abstract

No abstract

No abstract

No abstract