Discrepancy Reporting is a process that is established for tracking software, hardware, system, integration, test case, and facility problems in order to document, control, and test the changes required for problems found. Problems should be documented in a discrepancy reporting system at the time of discovery, rather than waiting until the problem is fully analyzed and the source understood. Establish a board to review and disposition corrective action(s) required. Tie the problems reported to the software/hardware change process.
Problems should be prioritized based on criticality (severity), for example: [1]
- Severity 1: Impact (must fix prior to software use in the actual system).
- Severity 2: Impact with known limitation documented in the system operator manual (in general, must fix prior to software use in the actual system).
- Severity 3: No impact, probable operational impact (must be fixed in next planned release or before operational need).
- Severity 4: No impact, no operational impact (could be lab problem).
- Severity 5: No impact, nuisance problem.
– See Engineering Change Proposal
– See Configuration Management
AcqLinks and References:
- [1] USAF Weapon Systems Software Management Guidebook – Aug 2011
- Mil-STD-498 “Software Development and Documentation” – 5 Dec 1994
- Software Development Plan Information Outline
- Website: MIL-STD-498 Software Documentation
Updated: 6/7/2018
