You are required to read and agree to the below before accessing a full-text version of an article in the IDE article repository.

The full-text document you are about to access is subject to national and international copyright laws. In most cases (but not necessarily all) the consequence is that personal use is allowed given that the copyright owner is duly acknowledged and respected. All other use (typically) require an explicit permission (often in writing) by the copyright owner.

For the reports in this repository we specifically note that

  • the use of articles under IEEE copyright is governed by the IEEE copyright policy (available at http://www.ieee.org/web/publications/rights/copyrightpolicy.html)
  • the use of articles under ACM copyright is governed by the ACM copyright policy (available at http://www.acm.org/pubs/copyright_policy/)
  • technical reports and other articles issued by M‰lardalen University is free for personal use. For other use, the explicit consent of the authors is required
  • in other cases, please contact the copyright owner for detailed information

By accepting I agree to acknowledge and respect the rights of the copyright owner of the document I am about to access.

If you are in doubt, feel free to contact webmaster@ide.mdh.se

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

Fulltext:


Authors:

Rikard Land, Laurens Blankers, Stig Larsson , Ivica Crnkovic

Research group:

Industrial Software Engineering

Publication Type:

Conference/Workshop Paper

Venue:

5th Working IEEE/IFIP Conference on Software Architecture, 2005. WICSA 2005.

Publisher:

IEEE

Abstract

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.

Bibtex

@inproceedings{Land960,
author = {Rikard Land and Laurens Blankers and Stig Larsson and Ivica Crnkovic},
title = {Architectural Concerns When Selecting an In-House Integration Strategy – Experiences from Industry},
pages = {274--275},
month = {November},
year = {2005},
booktitle = {5th Working IEEE/IFIP Conference on Software architecture, WICSA},
publisher = {IEEE},
url = {http://www.es.mdu.se/publications/960-}
}