| < Day Day Up > |
|
This standard provides minimum requirements for the preparation and content of 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. The standard applies to the entire life cycle of critical software.
According to this standard the content of an SCM plan should be as follows:
Introduction. Describes the plan’s purpose, scope of application, key terms, and references.
SCM management. This identifies the responsibilities and authorities for accomplishing the planned activities. (Who?)
SCM activities. This identifies all activities to be performed in applying to the project. (What?)
SCM schedules. This identifies the required coordination of SCM activities with the other activities in the project. (When?)
SCM resources. This identifies tools and physical and human resources required for execution of the plan. (How?)
SCM plan maintenance. This identifies how the plan will be kept current while in effect.
This guide describes the application of CM of software engineering projects. The guide serves three groups of people: software developers, software managers, and those responsible for the preparation of SCM plans. Software CM consists of two major aspects: planning and implementation. This guide focuses on SCM planning and provides broad perspectives for the understanding of SCM.
Software developers can use this standard to determine how CM can be used to support the software engineering process. Management can determine how the SCM plan can be adjusted to the needs and resources of a project.
| < Day Day Up > |
|