Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| dido:99_annexes:annex-d-requirements:part-00:p0-req-10-003 [2026/07/11 12:57] – ↷ Page moved from dido:99_annexes:annex-c-requirements:part-00:p0-req-10-003 to dido:99_annexes:annex-d-requirements:part-00:p0-req-10-003 nick_dido | dido:99_annexes:annex-d-requirements:part-00:p0-req-10-003 [2026/07/18 12:33] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== P0-REQ-10-003 ====== | ====== P0-REQ-10-003 ====== | ||
| - | [[dido: | + | [[dido: |
| ===== Statement ===== | ===== Statement ===== | ||
| - | The document set SHALL preserve traceability from conceptual elements to logical elements, implementation | + | The document set SHALL preserve traceability from conceptual elements to logical elements, implementation |
| ===== Source ===== | ===== Source ===== | ||
| Line 13: | Line 13: | ||
| ===== Rationale ===== | ===== Rationale ===== | ||
| - | 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 | + | The Financial Systems Archetype document set is intended to support a governed architectural chain from meaning to realization. Conceptual elements define the architectural intent. Logical elements refine that intent into structured models. Implementation |
| 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. | 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. | ||
| Line 19: | Line 19: | ||
| ===== Applies To ===== | ===== Applies To ===== | ||
| - | This requirement applies to the organisation, authoring, review, maintenance, | + | This requirement applies to the organization, authoring, review, maintenance, |
| It applies specifically to traceability among: | It applies specifically to traceability among: | ||
| Line 25: | Line 25: | ||
| * conceptual elements; | * conceptual elements; | ||
| * logical elements; | * logical elements; | ||
| - | * implementation | + | * implementation |
| - | * deployment | + | * deployment |
| * evidence and verification material. | * evidence and verification material. | ||
| ===== Verification ===== | ===== Verification ===== | ||
| - | Verification SHALL confirm that architectural elements can be traced across the document set from conceptual definition through logical refinement, implementation mapping, deployment | + | Verification SHALL confirm that architectural elements can be traced across the document set from conceptual definition through logical refinement, implementation mapping, deployment |
| Verification activities should include review checks confirming that: | Verification activities should include review checks confirming that: | ||
| Line 37: | Line 37: | ||
| * conceptual elements have corresponding logical refinements where appropriate; | * conceptual elements have corresponding logical refinements where appropriate; | ||
| * logical elements can be traced back to the conceptual elements they refine; | * logical elements can be traced back to the conceptual elements they refine; | ||
| - | * implementation | + | * implementation |
| - | * deployment | + | * deployment |
| * evidence items identify the architectural or implementation claims they support; and | * evidence items identify the architectural or implementation claims they support; and | ||
| * trace links are maintained when document parts are revised, split, moved, or extended. | * trace links are maintained when document parts are revised, split, moved, or extended. | ||
| Line 44: | Line 44: | ||
| ===== Traceability ===== | ===== Traceability ===== | ||
| - | This requirement supports the document set’s ability to demonstrate continuity from architectural intent to implemented and evidenced system | + | This requirement supports the document set’s ability to demonstrate continuity from architectural intent to implemented and evidenced system |
| Related requirement identifiers: | Related requirement identifiers: | ||
| - | * [[dido: | + | * [[dido: |
| - | * [[dido: | + | * [[dido: |
| - | * [[dido: | + | * [[dido: |
| - | * [[dido: | + | * [[dido: |
| Related source section: | Related source section: | ||