Findings
The ten findings, in order
Each finding names its requirements and the clause from the standards you ticked, and asks the requirement owner or the reviewer a question. None of them rules on the product or the project.
- 1 Requirement with no parentan unexpected blank parent: a requirement below the top level of the paste, not flagged derived, whose parent cell is empty (a confirmed top-level requirement, a flagged derived one and a parent outside this export are their own states, never this finding)
- 2 No verification method or no linked verificationa requirement below the top level with a blank verification method, or with no linked test or verification ID in either paste; where every child is verified and passing, or an analysis, inspection, review or simulation carries a recorded justification, it is asked as a question for that justification, never counted as a break
- 3 Verification failed, blocked or not runa linked verification whose latest result is failed, blocked, not run, inconclusive, deferred or passed with a deviation, or has no result row
- 4 Changed after its last passing verificationa requirement whose revision differs from the revision its latest pass was run against (when both are pasted), or else whose last-changed date is strictly later than the date of its latest passing verification
- 5 Test that traces to no requirementa test or verification in the results that no requirement links and that names no requirement in the paste; where the results carry a test type, regression, exploratory, infrastructure, robustness, qualification and smoke tests are shown apart by type and never raise it
- 6 Derived requirement not identified as derivedwith DO-178C ticked: a requirement below the top level with no parent and no derived flag
- 7 Parent outside this export, or an ID used twicea parent ID that no requirement in the paste carries (outside this export, or not an ID at all: an export cannot tell the two apart), or one requirement ID on more than one row (never merged)
- 8 Wording that may not be verifiableonly when requirement text is pasted: a word or phrase from the published list (TBD, as appropriate, user-friendly, sufficient and the rest), word-bounded
- 9 Design validation not recordeda user need or stakeholder requirement with a blank validation cell, where the paste has a validation column or ISO 13485 is ticked
- 10 Safety-rated requirement with no hazard or risk linkonly when the paste carries a hazard, risk or safety goal column: a requirement with a safety rating above QM, DAL E or class A whose link cell is blank
Not a finding, by design: whether a verification method is adequate for a safety rating. That is the assessor's judgement. Instead, safety-rated requirements sort first everywhere and the rating shows on every line.