Abstract
Most of the participants in ESSI projects dealt with configuration management purely in a practical manner, working with tools and procedures from various commercial vendors to solve their immediate problems. However, we believe that standards are an appropriate way to organise and define configuration management processes generally. To that end, it can be said that Software Configuration Management is a control discipline within the software project. Configuration Management should be used throughout a product’s life cycle, in development as well as during the maintenance process until the product is withdrawn. Three objectives should be considered in Software Configuration Management:
-
Establish and maintain the integrity of a software product during its life cycle.
-
Control the evolution of a software product.
-
Facilitate the visibility of a product.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2001 Springer-Verlag Berlin Heidelberg
About this chapter
Cite this chapter
Cuevas, G., Rementeria, S. (2001). Significant Results. In: Haug, M., Olsen, E.W., Cuevas, G., Rementeria, S. (eds) Managing the Change: Software Configuration and Change Management. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-56614-1_12
Download citation
DOI: https://doi.org/10.1007/978-3-642-56614-1_12
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-540-41785-9
Online ISBN: 978-3-642-56614-1
eBook Packages: Springer Book Archive