Software Engineering

15.4 
Document V&V results
The V&V findings must be reported. Software design defects must be identified 
and isolated to the offending structural configuration elements. These defects must 
be analyzed to establish a corrective action plan. Each V&V task must be recorded 
and summarized in V&V reports. The record of each V&V task should provide suf-
ficiently detailed information to enable the refurbishment of the defective design  
elements. V&V reports should include the following information, at a minimum:
●
  Identification of the architectural elements being evaluated.
●
  Identification of the relationships among the participating elements.
●
  The approach to conducting the V&V task.
●
  The findings that resulted from the investigation.
●
  Recommendations of the V&V participants.
The final report for each V&V task should be uniquely identified and entered 
into a logbook to record the V&V task identifier, title, time of task conduct, and 
the identifier and date of the report that summarized the findings. The V&V find-
ings must be published and distributed to the software organizations affected by 
the results. The findings must clearly identify the defective elements of the soft-
ware architecture, the defect uncovered, and the recommended course of action to 
be taken to resolve the defect. The course of action to refurbish a defective design 
element must be consistent with the state of the software development effort, the 
severity of the defect, and the ability of the defect to be resolved within the current 
project schedule. Defects that cannot be resolved before the release of the software 
product must be avoided with a workaround that prevents inadvertent user encoun-
ters. Workarounds must be sanctioned by the approval of a waiver to the require-
ment not being fulfilled at the time of software release.

---

This page intentionally left blank

---