Conference Paper

Managing change in component-based systems: A state-based approach.

Authors:
To read the full-text of this research, you can request a copy directly from the authors.

No full-text available

Request Full-text Paper PDF

To read the full-text of this research,
you can request a copy directly from the authors.

Article
The potential benefits of evolving legacy systems to COTS-based component architectures are well documented These include rapid non-intrusive modernization through the use of COTS sojiware components, and signzQicantly reduced post maintenance costs. However, the hype has not translated to a corresponding increase in the migration of legacy systems to COTS-based architectures. There are two main reasons for this. First, many legacy systems provide adequate core functionality. For this type of legacy system, replacement may not be the most cost-effective solution. Secondly, there is a general lack of scalable methods and tools that support COTS-based evolution of legacy systems. This paper describes our experience in using a component-based method to evolve a legacy system.
Conference Paper
Full-text available
Commercial off-the-shelf (COTS) software components promise benefits in terms of greater productivity, reduced time to market and reliability. However, their blackbox nature poses significant challenges assessing and managing the impact of change. We propose an approach to help developers to understand the impact of change. It relies on the use of a COTS component- oriented development process and an architecture description language (ADL) for documenting component system architectures; both elements contributing to create a combined approach to impact analysis in COTS-based system.
Conference Paper
Traditional software engineering change management approaches are inadequate for addressing the unique challenges presented by the component-based systems. Current change management techniques view the system under development as a collection of mutable subcomponents, known to the developer and whose interrelationships and development histories are described in a change management system. This contrasts with a component-based view of a system comprising potentially many interconnected, immutable, black-box components. This contrast represents the fundamentally different change management tasks associated with component-based development. We propose a novel architecture-centric approach that combines a process model with a dedicated ADL to provide a framework for change impact analysis.
ResearchGate has not been able to resolve any references for this publication.