Our research program aims at finding and testing method components for deciding on and implementing organizational splits and mergers. We tested a method to timely detect design & migration issues of a Post Merger Integration. Using actors from Enterprise Ontology as organization building blocks for two large operationally merging airliners, experts systematically listed per actor (a) its organizational implementations, (b) its Quality of Business and (c) its IT implementations. The drafted DEMO Construction Model appeared to be the first neutral and shared language for describing the essence of the business. Also the results needed for decision making (a) were experienced as a necessary and sufficient validation of operational integrity and (b) were delivered fast, yielding a high Return On Modeling Effort.

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

Abstract. The discipline of Enterprise Engineering aims for enterprises to operate as a unified and integrated whole. This discipline therefore adopts the mission to develop theories, models, methods and other artifacts for the analysis, design, implementation and governance of enterprises in a theoretically rigorous and practically relevant manner. The Enterprise Engineering Manifesto postulates the dualities of concepts function/construction perspective, blackbox/white-box models and subjective/objective as being opposed to each other in one-on-one relationships.Illustrated by the Pizzeria case, it becomes clear (a) that functions can be defined objectively, and (b) that a valuation perspective should be added that truly focuses on the relationship between a system and its stakeholders. These insights can support building stronger bridges between management and organization sciences -traditionally stronger in functional approaches -and information systems science, and computer science -traditionally stronger in constructional approaches.

No abstract

No abstract