Abstract:
This standard provides minimum requirements for preparation and content of Software Configuration Management (SCM) Plans. SCM Plans document the methods to be used for id...Show MoreScope:This standard provides minimum requirements for preparation and content of Software Configuration Management (SCM) Plans. SCM Plans document the methods to be used for id...Show More
Metadata
Abstract:
This standard provides minimum requirements for preparation and content of Software Configuration Management (SCM) Plans. SCM Plans document the methods to be used for identifying software product items, controlling and implementing changes, and recording and reporting change implementation status.
Scope:
This standard provides minimum requirements for preparation and content of Software Configuration Management (SCM) Plans. SCM Plans document the methods to be used for identifying software product items, controlling and implementing changes, and recording and reporting change implementation status. This standard applies to the entire life cycle of critical software; for example, where failure could impact safety or cause large financial or social losses. For noncritical software, or for software already developed, a subset of the requirements may be applied. This standard identifies those essential items that shall appear in all Software Configuration Management Plans. In addition to these items, the users of this standard are encouraged to incorporate additional items into the plan, as appropriate, to satisfy unique configuration management needs, or to modify the contents of specific sections to fully describe the scope and magnitude of the software configuration management effort. Where this standard is invoked for a project engaged in producing several software items, the applicability of the standard shall be specified for each of the software product items encompassed by the project. Examples are incorporated into the text of this standard to enhance clarity and to promote understanding. Examples are either explicitly identified as such, or can be recognized by the use of the verb may. Examples shall not be construed as mandatory implementations.
Date of Publication: 24 June 1983
Electronic ISBN:978-1-5044-0451-8
Persistent Link: https://ieeexplore.ieee.org/servlet/opac?punumber=7439687