Requirements–Design–Evaluation Traceability Matrix
Full traceability is documented here from environment-derived requirements through design features to evaluation measures. Requirements are drawn from Chapter 2 and Chapter 3. Design features are instantiated in Chapters 5 to 8. Evaluation measures are operationalised in Chapter 4 and tested in Chapter 10. Governance structures are provided by the Environment-Derived Requirements Register and the Environmental Grounding Dossier. Every requirement maps to at least one design feature and one evaluation measure. No orphaned requirement, feature, or measure exists in this matrix. In summary, the matrix links all three tiers of the thesis’s design science logic — problem, solution, and evaluation — into a single auditable chain. Requirement and feature specifications in the first two tables are extended in the final section by evaluation measure specifications.
Requirement-to-Feature-to-Measure Linkages
Req. ID | Feature ID | Measure ID | Proposition | Chapter Anchors | Evidence Object |
— | — | — | — | — | — |
ER-01 | DF-05A-01 | EM-4W-01 | P1 | Ch5 schema serialisation; Ch4 evaluation strategy | EVID-P1-INTERPRETABILITY |
ER-01 | DF-07C-01 | EM-09-01 | P3 | Ch7 encoding/parsing; Ch9 interpretability results | EVID-P3-REPLAY |
ER-02 | DF-06B-01 | EM-4W-02 | P2 | Ch6 interaction rules; Ch4 validity/reliability | EVID-P2-CHECK-SCOPE |
ER-02 | DF-07C-02 | EM-09-02 | P3 | Ch7 formal core; Ch9 modular fit | EVID-P3-INVARIANTS |
ER-03 | DF-05A-02 | EM-09-03 | P5 | Ch5 ambiguity analysis; Ch9 workflow efficiency | EVID-P5-BURDEN |
ER-04 | DF-05A-03 | EM-09-01 | P1 | Ch5 standards schema; Ch9 standards interpretability | EVID-P1-SDA-TRACE |
ER-05 | DF-06B-02 | EM-09-02 | P2 | Ch6 module interfaces; Ch9 modular-fit | EVID-P2-LOCAL-GLOBAL |
ER-05 | DF-08D-01 | EM-4W-03 | P4 | Ch8 procedural pipeline; Ch4 data pipelines | EVID-P4-VARIATION |
ER-06 | DF-08D-02 | EM-09-04 | P4 | Ch8 pre-vetted library; Ch9 discussion of results | EVID-P4-EXCEPTION-BUDGET |
Design Feature Specifications
Each design feature below is located in the chapter indicated and satisfies the listed environment requirements. Artefact type and mechanism identify the design object category and primary addressing mechanism. Constraints and trade-offs columns record the design decisions that bound each feature.
Feature ID | Chapter | Artefact Type | Mechanism | Req. IDs | Constraints | Trade-offs |
— | — | — | — | — | — | — |
DF-05A-01 | 5 | Construct | Interface | ER-01 | Standards semantics must be serialisable and versionable | Higher modelling discipline required upfront |
DF-05A-02 | 5 | Method | Invariant | ER-03 | Ambiguity categories must remain stable across cases | Reduced flexibility for ad hoc labelling |
DF-05A-03 | 5 | Model | Interface | ER-04 | Accessibility semantics must bind to traceable entities | Additional schema complexity |
DF-06B-01 | 6 | Model | Interface | ER-02 | Module contracts must declare valid interactions | Contract maintenance overhead |
DF-06B-02 | 6 | Method | Trigger | ER-05 | Trigger logic must remain finite and explicit | Edge cases require escalation policy |
DF-07C-01 | 7 | Method | Transformation | ER-01 | Replayability must be deterministic within declared bounds | Stricter parser and test-harness constraints |
DF-07C-02 | 7 | Construct | Invariant | ER-02 | Formal core invariants must be executable | Harder onboarding for non-technical readers |
DF-08D-01 | 8 | Instantiation | Trigger | ER-05 | Generated outputs must preserve rule traceability | Throughput may reduce under heavy validation |
DF-08D-02 | 8 | Method | Interface | ER-06 | Library governance requires explicit exception classes | Governance friction for rapid experimentation |
Evaluation Measure Specifications
Each evaluation measure below is operationalised in the chapter indicated. The metric definition, baseline definition, unit, and threshold columns document the measurement protocol established in Chapter 4. The data source column identifies the evidence stream consumed in Chapter 10.
Measure ID | Chapter | Metric Definition | Baseline Definition | Unit | Threshold | Data Source |
— | — | — | — | — | — | — |
EM-4W-01 | Ch4w | Interpretation divergence for matched regulatory obligations | Synchronous artefact workflow divergence | Divergence rate | Lower than baseline with practical significance | Ch4w protocol logs |
EM-4W-02 | Ch4w | Local-to-global verification scope ratio per transformation event | Scope ratio under non-modular workflow | Ratio | Local scope dominates under bounded edits | Change-trace logs |
EM-4W-03 | Ch4w | Rule-compliant variant generation rate | Manual exception-heavy variation process | Compliance proportion | Meets pre-registered exception budget | Generation logs |
EM-09-01 | Ch9 | Standards interpretability trace completeness | Baseline interpretability trace completeness | Completeness index | Improved trace completeness over baseline | Ch9 case outputs |
EM-09-02 | Ch9 | Modular-fit and bounded-check performance | Baseline modular-fit under monolithic representation | Composite score | Improved bounded verification over baseline | Ch9 modular-fit outputs |
EM-09-03 | Ch9 | Workflow burden delta across time, cognitive, and skill proxies | Baseline burden profile for matched tasks | Delta | Burden reduction with declared confidence limits | Ch9 workflow outputs |
EM-09-04 | Ch9 | Exception governance quality in discussion synthesis | Baseline unguided exception handling | Quality score | All exceptions typed and justified | Ch9 discussion evidence |
Linkage coverage is complete: every environment requirement in the Requirements Register maps to at least one design feature and one evaluation measure. The full problem-statement derivation for each requirement is in the Environmental Grounding Dossier. Overall, the matrix confirms completeness: every requirement, feature, and measure is linked. No orphan exists in any direction. Evaluation results in Chapter 10 are therefore interpretable as direct evidence against the environment-derived requirements. Post-hoc performance claims are excluded by the pre-declared traceability structure.