Engineering Traceability¶

Traceability in OpenSESA is implemented as linked module behavior, not an isolated feature.

Traceability Layers¶

flowchart TD
    Def["Definition Layer\nsysdef + sysarch + diagrams"]
    Control["Control Layer\ninterface + requirements"]
    Evidence["Evidence Layer\nverification + safety"]
    Governance["Governance Layer\nbaseline + impact + ops"]

    Def --> Control --> Evidence --> Governance

Detailed Trace Path¶

flowchart LR
    S["System Element"] --> I["Interface"]
    I --> R["Requirement"]
    R --> C["Verification Case"]
    C --> E["Execution Result"]
    E --> A["Assurance Evidence"]
    R --> B["Baseline Item"]
    B --> P["Impact Finding"]
    P --> O["Readiness Action"]

Traceability Capability Matrix¶

Step	Primary Module	Functionality	Linked Module
definition	`sysdef_mgmt`, `sysarch_mgmt`	structure and architecture context	`interface_mgmt`, `requirements_mgmt`
interface control	`interface_mgmt`, `project_interface_mgmt`	interface relationships and project mapping	`requirements_mgmt`
requirement trace	`requirements_mgmt`	requirement links/reviews/analysis	`verification_validation_mgmt`, `baseline_mgmt`
verification evidence	`verification_validation_mgmt`	case/result/defect capture	`safety_assurance`, `baseline_mgmt`
assurance mapping	`safety_assurance`	evidence-to-assurance interpretation	release stakeholders
release impact	`baseline_mgmt`, `impact_assessment`	baseline package impact evaluation	`ops_mgmt`
readiness execution	`ops_mgmt`	actions, milestones, dependencies	governance teams

# traceability-focused validation
docker compose run --rm app sh -c "pytest requirements_mgmt/tests verification_validation_mgmt/tests safety_assurance/tests -v"
docker compose run --rm app sh -c "pytest baseline_mgmt/tests impact_assessment/tests ops_mgmt/tests -v"

Audit-friendly usage

Keep trace links explicit when creating requirements, cases, and release candidate records so evidence paths remain queryable.