dido:99_annexes:annex-d-requirements:part-00:p0-req-10-003

This is an old revision of the document!


P0-REQ-10-003

The document set SHALL preserve traceability from conceptual elements to logical elements, implementation artefacts, deployment artefacts, and evidence.

Part 0, Section 10: Document Set Requirements.

The Financial Systems Archetype document set is intended to support a governed architectural chain from meaning to realisation. Conceptual elements define the architectural intent. Logical elements refine that intent into structured models. Implementation artefacts realise the logical elements using selected technologies. Deployment artefacts describe operational placement and execution. Evidence provides the basis for verifying that the deployed result remains consistent with the architecture.

Without traceability across these levels, later implementation or deployment decisions could become disconnected from the conceptual architecture. This would make it difficult to determine whether an implementation still satisfies the intended financial-system meaning, whether evidence supports the correct architectural claim, or whether changes in one part of the document set affect related parts.

This requirement applies to the organisation, authoring, review, maintenance, and interpretation of trace relationships across the Financial Systems Archetype document set.

It applies specifically to traceability among:

* conceptual elements; * logical elements; * implementation artefacts; * deployment artefacts; and * evidence and verification material.

Verification SHALL confirm that architectural elements can be traced across the document set from conceptual definition through logical refinement, implementation mapping, deployment realisation, and supporting evidence.

Verification activities should include review checks confirming that:

* conceptual elements have corresponding logical refinements where appropriate; * logical elements can be traced back to the conceptual elements they refine; * implementation artefacts identify the logical elements they realise; * deployment artefacts identify the implementation artefacts they deploy or configure; * evidence items identify the architectural or implementation claims they support; and * trace links are maintained when document parts are revised, split, moved, or extended.

This requirement supports the document set’s ability to demonstrate continuity from architectural intent to implemented and evidenced system behaviour.

Related requirement identifiers:

* P0-REQ-10-001 * P0-REQ-10-002 * P0-REQ-10-004 * P0-REQ-10-005

Related source section:

* 10. Document Set Requirements

Draft

  • dido/99_annexes/annex-d-requirements/part-00/p0-req-10-003.1783799872.txt.gz
  • Last modified: 2026/07/11 12:57
  • by nick_dido