loading...
 This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Fifth Working IEEE/IFIP Conference on Software Architecture (WICSA'05)
Architectural Concerns When Selecting an In-House Integration Strategy - Experiences from Industry
Pittsburgh, Pennsylvania
November 06-November 10
ISBN: 0-7695-2548-2
Rikard Land, M?lardalen University, Sweden
Laurens Blankers, Eindhoven University of Technology, The Netherlands
Stig Larsson, M?lardalen University, Sweden
Ivica Crnkovic, M?lardalen University, Sweden
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.
Citation:
Rikard Land, Laurens Blankers, Stig Larsson, Ivica Crnkovic, "Architectural Concerns When Selecting an In-House Integration Strategy - Experiences from Industry," wicsa, pp.274-275, Fifth Working IEEE/IFIP Conference on Software Architecture (WICSA'05), 2005
Usage of this product signifies your acceptance of the Terms of Use.