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

  • Authors:

  • Rikard Land;Laurens Blankers;Stig Larsson;Ivica Crnkovic

  • Affiliations:

  • Mälardalen University, Sweden;Eindhoven University of Technology, The Netherlands;Mälardalen University, Sweden;Mälardalen University, Sweden

  • Venue:
  • WICSA '05 Proceedings of the 5th Working IEEE/IFIP Conference on Software Architecture
  • Year:
  • 2005

Quantified Score

Hi-index 0.00

Visualization

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.