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

Component Configuration Management

Fulltext:


Authors:

Magnus Larsson, Ivica Crnkovic

Publication Type:

Conference/Workshop Paper

Venue:

ECOOP Conference, Workshop on Component Oriented Programming Nice, France

Abstract

Component-based programming is nowadays widely recognized approach in software development. Still there are many open problems related to both technical and non-technical aspects of the components. In this paper, we point out the problem of component identification. Since the components are usually binary units deployed in the system at run-time, we do not have the same insight to their characteristics as for software units that we manage at development time. This problem could be solved if the components had built in this information together with the binary code, which can be achieved by defining a standardized identification interface. As such interfaces do not exist in standard component models today, this concept is possible to use only with components built in-house. For external components, extensive tests can, to some extent, compensate the lack of information. To perform an efficient and yet a successful testing we must limit the number of test cases. Which parts of our system can be affected by introduction of a component, or by its updating? We can answer this if we can keep track of changes introduced in the system and their impact on the system. These problems are similar to the problems at development-time solved by Software Configuration Management (SCM) disciplines. In this paper we point out these problems and make proposals for their utilization at run-time using SCM principles.

Bibtex

@inproceedings{Larsson202,
author = {Magnus Larsson and Ivica Crnkovic},
title = {Component Configuration Management},
month = {June},
year = {2000},
booktitle = {ECOOP Conference, Workshop on Component Oriented Programming Nice, France},
url = {http://www.es.mdu.se/publications/202-}
}