engleski

Architectural Concerns When Selecting an In-House Integration Strategy – Experiences from Industry

Consider the scenario where two or more software systems have been developed in-house, for different purposes. Over time, the systems have been evolved to contain more functionality, until a point where there is some overlap in functionality and purpose. The same situation occurs, only more drastically, as a result of company acquisitions and mergers. A new system combining the functionality of the existing systems would improve the situation both from an economical and maintenance point of view, and from the point of view of users, marketing and customers. To investigate this problem of in-house integration, we carried out a multiple case study, consisting of nine integration projects in six organizations from different domains (here labelled A-F). For details on methodology, a presentation of the data sources, and the complete copied out interviews, see [3]. Elsewhere we have analyzed the case study data from a process point of view [4], and discussed the possibilities for reuse in this context [2] ; the present paper investigates issues of importance to an industrial architect [5] and focuses on how to select a high-level integration strategy.

data sources; industrial architect; high-level integration

nije evidentirano