12. Software Non-conformance or Defect Management Activity Overview

To make sure that all software non-conformances are addressed. Managing and tracking non-conformances, software problem reports, or software issues are critical steps to ensuring that software defects are flagged and handled properly.Severity is defined as the degree of impact a defect has on the development or operation of the software being tested.  A higher effect on the system functionality will lead to the assignment of higher severity to the bug. Severity indicates the seriousness of the defect in the software functionality.  These software severity levels should be defined and implemented clearly.

Software components that are used to build the software product (e.g., compilers) or become a part of the software (e.g., Operating Systems) can introduce unexpected defects in the delivered product.  Whenever non-conformances in these products are discovered, a thorough assessment is required to identify any other potential impacts.    

Understand why the high severity software non-conformance or defect occurred and make process changes to avoid additional high severity software non-conformances or defects.  To reduce software defects.

Frequency Of This Activity

The non-conformance and defect management activity is performed continuously during the life of the project. It gives the project team visibility into the remaining work to be performed. All tracked items must be resolved to a level where they have no adverse affects on the project. 

12.1 Related SWEs

• SWE-201 - Software Non-Conformances - 5.5.1 The project manager shall track and maintain software non-conformances (including defects in tools and appropriate ground software). 
• SWE-202 - Software Severity Levels - 5.5.2 The project manager shall define and implement clear software severity levels for all software non-conformances (including tools, COTS, GOTS, MOTS, OSS, reused software components, and applicable ground systems).
• SWE-203 - Mandatory Assessments for Non-Conformances - 5.5.3 The project manager shall implement mandatory assessments of reported non-conformances for all COTS, GOTS, MOTS, OSS, and/or reused software components.
• SWE-204 - Process Assessments - 5.5.4 The project manager shall implement process assessments for all high-severity software non-conformances (closed-loop process).

12.2 Related Work Products

• Defect management procedures
• 5.01 - CR-PR - Software Change Request - Problem Report - Minimum recommended content for the Software Change Request - Problem Report. 
• 7.08 - Maturity of Life Cycle Products at Milestone Reviews - This chart summarizes current guidance approved by the NASA Office of the Chief Engineer (OCE) for software engineering life cycle products and their maturity level at the various software project life cycle reviews.
• 7.09 - Entrance and Exit Criteria - This guidance provides the recommended life cycle review entrance and exit criteria for software projects and should be tailored for the project class.
• A.10 Software Peer Reviews and Inspections - defect management procedures are good candidates for a Peer Review

12.2.1 Related Process Asset Templates

12.3 Related Topics

12.4 Related SPAN Links