Page History
| Alias | ||
|---|---|---|
|
...
| id | tabs-1 |
|---|
1. Requirements
3.5.1 The project shall document the software maintenance plans in a Software Maintenance Plan document.
1.1 Notes
The requirement for the content of a Software Maintenance Plan is defined in Chapter 5 [of NPR 7150.2, NASA Software Engineering Requirements, Section 5.1.4].
1.2 Applicability Across Classes
Class G is labeled with "P (Center)." This means that an approved Center-defined process which meets a non-empty subset of the full requirement can be used to achieve this requirement.
| applicable | ||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||
|
| Div | ||
|---|---|---|
| ||
2. RationalePer NPR 7150.2, "Planning for operations, maintenance, and retirement must be considered throughout the software life cycle. Operational concepts and scenarios are derived from customer requirements and validated in the operational or simulated environment. Software maintenance activities sustain the software product after the product is delivered to the customer until retirement...The Software Maintenance Plan provides insight into the method, approach, responsibility, and processes to be followed for maintenance of software and its associated documentation." |
...
| id | tabs-3 |
|---|
3. Guidance
The software maintenance plan describes operations, maintenance, and retirement activities (see the guidance in this Handbook for SWE-075). The maintenance plan is typically a separate plan, but may be part of another project document such as the Software Management Plan (SMP). For existing processes that may be used during operations, maintenance, and retirement, the maintenance plan may simply reference existing project documents that describe those processes.
One key goal of the software maintenance plan is to document the plans for maintaining a piece of software, especially in the case that an organization assumes responsibility for maintaining a piece of software developed by another organization. The maintenance plan is not intended, however, to require updates to other planning documents from the software development life cycle, such as the software development plan. The maintenance plan becomes the planning document for the maintenance phase of the software life cycle.
The maintenance plan generally has minimal content at the beginning of a project and becomes more complete and mature as the software life-cycle proceeds. This handbook provides the recommended maturity of the maintenance plan at major milestone reviews (see 7.8 - Maturity of Life Cycle Products at Milestone Reviews).
See SWE-105 in this Handbook for guidance on required maintenance plan contents, but consider the following topics as well when developing the maintenance plan, as appropriate for the particular project:
Operations
...
Maintenance
...
Retirement
...
Other
...
Once the maintenance plan is created, it is peer reviewed and reviewed at project milestone reviews such as the Mission Concept Review (MCR), Software Requirements Review (SwRR), Mission Definition Review (MDR), etc. (see Topic 7.8 - Maturity of Life Cycle Products at Milestone Reviews in this Handbook).
| Note |
|---|
Consult Center Process Asset Libraries (PALs) for Center-specific guidance related to documenting the maintenance plan. |
Additionally, guidance related to maintenance plans may be found in the following related requirements in this handbook:
Plan Operations, Maintenance, Retirement | |
Implement Operations, Maintenance and Retirement Activities | |
Software Maintenance Plan |
| Div | ||
|---|---|---|
| ||
4. Small ProjectsFor projects with limited staff or budgets, consider adapting a maintenance plan from a similar project making sure to update the plan to reflect the current project's operations, maintenance, and retirement plans. The contents of a maintenance plan can also be addressed as sections in another project document and is not required to be in a separate document. |
| Div | |||
|---|---|---|---|
| |||
5. Resources
|
...
| id | tabs-6 |
|---|
6. Lessons Learned
The NASA Lesson Learned database contains the following lessons learned related to maintenance planning:
...
