Integrating Configuration Management and Software Deployment

As the development and use of component-based software becomes increasingly pervasive, the need arises for tools that support the controlled evolution of independently developed components—both at development and at deployment time. Traditionally, such tools have been separate: configuration management tools are used during the development of a software product and deployment tools are used to install, update, and reconfigure a software product once it is out in the field. This position paper first presents an argument why this separation is inadequate for component-based software. Then, it presents a set of requirements for an integrated system that intimately combines configuration management and software deployment functionality to support the evolution of component-based software in a unified manner.

[1]  Ed Bailey.  Maximum RPM , 1997 .

[2]  Richard N. Taylor,et al.  A highly-extensible, XML-based architecture description language , 2001, Proceedings Working IEEE/IFIP Conference on Software Architecture.

[3]  David S. Rosenblum,et al.  Design and evaluation of a wide-area event notification service , 2001, TOCS.

[4]  Richard S. Hall,et al.  A cooperative approach to support software deployment using the Software Dock , 1999, Proceedings of the 1999 International Conference on Software Engineering (IEEE Cat. No.99CB37002).

[5]  Susan A. Dart,et al.  Spectrum of Functionality in Configuration Management Systems , 1990 .

[6]  Reidar Conradi,et al.  Version models for software configuration management , 1998, CSUR.