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.
Requirements-design-evaluation traceability: no orphan in any directionThe requirements-design-evaluation traceability matrix rendered as a left-to-right flow, so the no-orphan property is self-evident: six environment requirements connect through nine design features to seven evaluation measures and on to the five propositions (P1 interoperability, P2 transportability, P3 manipulability, P4 transformability, P5 integrated burden), following the nine linkage rows of the matrix below. Every requirement reaches a design feature, an evaluation measure, and a proposition, and every column is reached; no requirement, feature, or measure is an orphan in any direction. After Appendix D (Requirements-Design-Evaluation Traceability Matrix).
Requirement-to-Feature-to-Measure Linkages
Req. ID | Feature ID | Measure ID | Proposition | Chapter Anchors | Evidence Object |
Two summative measures are shared by design, so they appear in two linkage rows each: EM-09-01 warrants both Proposition 1 (standards interpretability) and Proposition 3, which borrows it as replay evidence, and EM-09-02 warrants both Proposition 2 (modular fit) and Proposition 3. Proposition 3 carries no dedicated Chapter 4 formative measure and takes EM-09-01 and EM-09-02 as its two summatives, as recorded in the canonical Property-Proposition-Evaluation Map and the Evaluation Workbench. The repeated appearance is intentional shared warranting, not a cross-wire, and creates no orphan.
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 |
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-09-01 | Ch10 | Standards interpretability trace completeness | Baseline interpretability trace completeness | Completeness index | Improved trace completeness over baseline | Ch10 case outputs |
EM-09-02 | Ch10 | Modular-fit and bounded-check performance | Baseline modular-fit under monolithic representation | Composite score | Improved bounded verification over baseline | Ch10 modular-fit outputs |
EM-09-03 | Ch10 | Workflow burden delta across time, cognitive, and skill proxies | Baseline burden profile for matched tasks | Delta | Net reduction with declared confidence limits | Ch10 workflow outputs |
EM-09-04 | Ch10 | Exception governance quality in discussion synthesis | Baseline unguided exception handling | Quality score | All exceptions typed and justified | Ch10 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.
