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

Software Systems In-House Integration Strategies: Merge or Retire - Experiences from Industry

Fulltext:


Authors:


Publication Type:

Conference/Workshop Paper

Venue:

Fifth Conference on Software Engineering Research and Practice in Sweden (SERPS)

Publisher:

Mälardalen University


Abstract

When an organization faces different types of collaboration, for example after a company merger, there is a need to consolidate the existing in-house developed software. A main challenge is to select a suitable strategy, such as merging the systems, evolve one of the existing systems to be able to retire others, or start a new development effort in order to retire the existing systems. This should arguably be done at a high abstraction level, i.e. architectural level. In order to investigate how a strategy should be chosen, we have performed a multiple case study, consisting of nine integration projects. Two major concerns have been found that can be used to exclude some strategies: 1) architectural compatibility, and 2) what we have labeled ‘retireability’, i.e. all considerations influencing whether or not the existing systems can be allowed to be retired.

Bibtex

@inproceedings{Land886,
author = {Rikard Land and Laurens Blankers and Stig Larsson and Ivica Crnkovic},
title = {Software Systems In-House Integration Strategies: Merge or Retire - Experiences from Industry},
pages = {21--30},
month = {October},
year = {2005},
booktitle = {Fifth Conference on Software Engineering Research and Practice in Sweden (SERPS)},
publisher = {M{\"a}lardalen University},
url = {http://www.es.mdh.se/publications/886-}
}