Software Engineering

301
17.7 
Reviews, milestones, and baselines
●
  Inspection of the software test plan
●
  Inspection of the requirements traceability matrix
●
  Inspection of the post-development process concept documents
●
  Inspection of the nomenclature register
Software quality inspections should be conducted to ensure that organizations 
are complying with established policies and procedures. Software audits should be 
conducted prior to the SRR to ensure the available software specifications provide 
a consistent and traceable framework for evaluating software requirements against 
project and technical plans and stakeholder needs and expectations. The following 
audits should be conducted:
1. 
Software requirements audit
—traces stakeholder needs to the specified require-
ments in the software specifications through the operational model to the 
preliminary functional and physical architectures. The source for derived 
requirements should be associated with the engineering analysis or trade study 
that recognized the implied need. Derived requirements must be included within 
the requirements traceability matrix.
2. 
Software test audit
—traces software test cases or scenarios to the operational 
model data processing transactions and software requirements each scenario 
will exercise. The test cases should be properly reflected in the requirements 
traceability matrix.
3. 
Corrective action audit
—traces each software problem report, change request, 
or proposal to its trade-study report and corrective action plan. Ensures that 
the corrective action is properly reflected in the operational model, software 
requirements specifications, functional and physical architectures, and associ-
ated architectural artifacts affected by the action.