SOLUTION of the asked question - 64624

Solution Detail
Price: $9.10
  • From: ,
  • Posted on: Mon 26 May, 2014
  • Request id: # 64574
  • Purchased: 1 time(s)
  • Average Rating: No rating
Request Description
Solution Description

The Integrating Component Architectures Process (ICAP) outlines a process that includes predicting interoperability conflicts among independent components, COTS included, based on architectural differences. Previously defined integration elements, along with a taxonomy of integration solutions based on these elements, direct movement through the process to an integration architecture for implementation. The ICAP predominantly falls into the elaboration phase of the Rational Unified Process, providing greater detail of the issues surrounding interoperability. We believe that such a development process will allow easier and more cost-effective maintenance and migration of legacy systems, as well as the use of COTS products in system development. Keywords Integration, Rational Unified Process, interoperability, taxonomy, COTS 1 INTRODUCTION COTS products are normally well tested and can provide a reliable system that meets the needs of the users. Recent developments in software engineering include the use of COTS products with custom or pre-existing software systems to enhance functionality. However, integrating the existing system with a COTS product has proven to be complicated and expensive since reuse is feasible only if existing components can be easily adapted for interoperability. Also it can be a formidable task to discover the correct solution to interoperability problems since published descriptions of these solutions often overlap or they may be language dependent. Fortunately, many of the interoperability problems can be predicted if the overall system is evaluated at the architectural level before implementation. Architectural analysis can detect potential conflicts and guide the developer towards the resolution of the problems. It can also reduce the cost and increase the stability of the system being integrated, as the use of ad hoc methods of integration during implementation are minimized. Although current accepted software engineering development processes exist that consider the inclusion of COTS products with a software system [1, 5], they do not provide a method to analyze components with respect to integrating COTS products with other systems. In this paper, we introduce a software design process that provides for the early architectural analysis of software systems and in turn provides a better method to integrate CO