Capability Guide: Verification and Assurance¶

Purpose¶

Convert requirement scope into executable verification evidence and assurance confidence signals.

Modules In Scope¶

• verification_validation_mgmt
• safety_assurance

When To Use This Guide¶

• creating or refactoring verification plans/cases
• troubleshooting result/defect data integrity
• preparing assurance evidence for release decisions

Verification-to-Assurance Flow¶

flowchart LR
    Scope["Requirement Scope"] --> Plan["Verification Plan"]
    Plan --> Activity["Activity"]
    Activity --> Case["Case and Set"]
    Case --> Result["Execution Result"]
    Result --> Defect["Defect"]
    Result --> Evidence["Assurance Evidence"]
    Evidence --> Claim["Assurance Confidence"]

Step-by-Step¶

1. Establish verification plan aligned to requirement baseline.
2. Create activities and cases with explicit linkage.
3. Execute cases and persist results.
4. Capture and triage defects.
5. Aggregate evidence for assurance views.
6. Verify confidence indicators before release governance.

Artifacts Produced¶

• verification plans/activities/cases/sets
• execution results and defect records
• assurance evidence/summary views

Data Integrity Rules¶

• case IDs must remain stable for historical comparability
• results must preserve requirement linkage context
• defect records should reference execution provenance

Validation Checklist¶

docker compose run --rm app sh -c "pytest verification_validation_mgmt/tests safety_assurance/tests -v"
./scripts/run_smoke_tests.sh

• case-result-defect chain remains queryable
• assurance views include latest relevant evidence
• imports/exports preserve linkage fidelity

Common Failure Modes¶