Problem Reports and Change Requests
Section 08: Software Certification (DO-178C)
Definition
A problem report (PR) is a document that records a discrepancy, deficiency, or anomaly discovered in any software lifecycle data — including requirements, design, code, test cases, test results, or documentation. A change request (CR) is a formal request to modify a configuration item. DO-178C requires that all problems discovered during the software lifecycle be recorded in problem reports, that problem reports be analyzed for their impact, and that corrective actions be tracked to closure. Open problem reports at the time of certification must be evaluated for their safety impact and documented in the Software Accomplishment Summary (SAS). The problem reporting and change control system is a critical element of configuration management.
Where This Shows Up
Problem reports provide the trail of defect discovery and resolution that demonstrates the quality of the development and verification processes. A high number of open problem reports at certification, or a pattern of late-stage critical defect discoveries, may indicate process deficiencies. The certification authority reviews the status of problem reports as part of the certification audit, and the SAS must address any open PRs and their disposition.
Primary Sources
Defines problem reporting and change control requirements within the configuration management process.
Artifacts Produced
Document recording a discovered discrepancy in software lifecycle data, including description, impact analysis, corrective action, and closure status.
Document requesting a formal change to a configuration-controlled item, including rationale, impact analysis, and approval.
Related Terms
Need help navigating certification?
Understanding the terminology is the first step. If you need expert guidance on DO-178C, DO-254, ARP4754B, or any aspect of FAA, EASA, or TCCA certification, our team is here to help.