This paper discusses whether method construction can serve as a core approach to organizational engineering. Based on a discussion of fundamental scientific positions in general and approaches to information systems research in particular, appropriate conceptualizations of 'method' and 'method construction' are presented. These conceptualizations are then discussed regarding their capability of supporting organizational engineering.

Over the past few decades, the way in which enterprises have performed their business and organizational changes at the level of information systems has for the most part been incomplete and / or unsystematic. Fundamental IT innovations have therefore coincided with the development of heterogeneous application landscapes which are more or less inconsistent with the business and / or process architecture. Explicit management of the application architecture, which forms the interface between the business and the technical view on the information system, is necessary to recreate and preserve consistency. Based on a requirements analysis for enterprise application architecture management and a discussion of related work from literature and practice, this paper proposes processes that are based on three case studies. The proposed processes are evaluated in respect of the specified requirements. Requirements management C-I Architecture development C-II C-IV Architecture conformity check Architecture communication C-III Define IT strategy C-I.1 Record operational requirements C-I.2 Communicate architecture artifacts C-IV.1 Check architecture conformity of projects Use existing architecture artifacts C-II.1 R5 R10 R5, R6 R5, R10 Identify need for action for the architecture C-I.3 R8 Evaluate need for action C-I.4 R4, R6 R5 Develop/adapt architecture artifacts C-II.2

No abstract

No abstract

No abstract