Configuration management (CM) is the regulation of the way in which a software product evolves during the development and maintenance phases of the product lifecycle. It is the process by which the individual components of a software system are identified so that any changes to the configuration of these components can be systematically traced and therefore controlled throughout the complete span of the development cycle. CM thus forms the basis for product and project measurement.
This How To Guide is based in large part on ANSI/IEEE 1042.
S C O P E
This How To Guide describes the application of configuration management (CM) principles to the management of software development projects. CM consists of two major aspects; planning and implementation.
For those planning software configuration management activities, this standard provides guide-lines into the aspects which must be considered.
For those implementing software configuration management disciplines can use the sample Configuration Management Plan attached.
This How To Guide outlines the essential concepts of CM, including libraries and tools.
O B J E C T I V E S
To achieve the above, the objective of a project manager will be the identification and establishment of baselines; the review, approval, and control of changes to the project components; the tracking and reporting of such changes; the reviews of the evolving product; the control of documentation; and the control of the interfaces to the clients and supplier.
However it should be noted that this How To Guide specifies the minimum requirements, and therefore the project manager has the option where required, to expand and supplement as necessary for the development of specific project activities.
In specific terms, the objective of CM procedures are to provide methods for:
Obtaining approval to implement a modification
Ensuring that modifications are correctly integrated through formal change control pro-cedures
Controlling the identification of development status
Ensuring that nonconforming software is identified and segregated
Contribution to IS Quality. A structured and comprehensive approach to software design is known to be a major factor contributing to Information Systems Quality. Adequate configuration management is however often not performed, contributing to a higher number of software defects which impact the real and perceived quality of the software, as well as leading to time and expense being spent on rework and higher maintenance costs.
How to Write Configuration Management Plans is a plain-English, procedural guide to developing CM Plans that are both systematic and comprehensive. It contains detailed instructions and templates.
Software Configuration Management Standard
How to Write Software Configuration Management Plans
Publication date: 21/04/2011
Plain English How To Guide based in large part on ANSI/IEEE 1042
El vendedor asume toda la responsabilidad de esta entrada.