The project team baselines the maintenance plan before it is implemented to ensure that the team carrying out the operations, maintenance, and retirement activities executes only the approved plan. Software Assurance personnel are responsible for assuring that these activities are carried out per the baselined maintenance plan.
There are fewer reasons for the maintenance plan to require revision than plans used for the earlier life-cycle phases, but keep the following in mind as a non-exhaustive list of events that could cause the maintenance plan to require updating:
- Changes in resource levels, availability (e.g., tools, facilities, personnel).
- In response to new or revised risks.
- Budget changes.
- Changes in stakeholders/stakeholder needs.
- Changes in processes used for operations, maintenance, retirement (e.g, reporting processes, review processes, record keeping processes).
As with other project documents, updates to the Software Maintenance Plan are reviewed and approved before being implemented.
Consult Center Process Asset Libraries (PALs) for Center-specific guidance related to implementing operations, maintenance, and retirement.
For NPR 7120.5 projects, this Handbook provides the recommended maturity of the Software Maintenance Plan at major milestone reviews (see Maturity of Life cycle Products at Milestone Reviews). Additionally, guidance related to operations, maintenance, and retirement planning may be found in the following related requirements in this Handbook:
Software Plans (Execute Planning)
Document Maintenance Plan
Plan Operations, Maintenance, Retirement
Software Maintenance Plan