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-01:p1-req-13-2-001:start [2026/07/11 12:57] – removed - external edit (Unknown date) 127.0.0.1 | dido:99_annexes:annex-d-requirements:part-01:p1-req-13-2-001:start [2026/07/18 12:33] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== P1-REQ-13-2-001 ====== | ||
| + | [[dido: | ||
| + | |||
| + | ===== Statement ===== | ||
| + | |||
| + | The Conceptual Architecture SHALL preserve separation between conceptual meaning, logical [[dido: | ||
| + | |||
| + | ===== Source ===== | ||
| + | |||
| + | Part 1, Section 13.2: Conceptual Separation Requirements. | ||
| + | |||
| + | ===== Rationale ===== | ||
| + | |||
| + | The Conceptual Architecture defines a stable meaning for the Financial Systems Archetype. Logical structure, implementation mapping, deployment mechanics, testability, | ||
| + | |||
| + | Preserving separation prevents implementation or deployment decisions from altering the architecture' | ||
| + | |||
| + | ===== Applies To ===== | ||
| + | |||
| + | This requirement applies to the organization, | ||
| + | |||
| + | It applies specifically to the separation among: | ||
| + | |||
| + | * Conceptual meaning; | ||
| + | * Logical structure; | ||
| + | * Implementation mapping; | ||
| + | * Deployment mechanics; | ||
| + | * Testability; | ||
| + | * Evidence. | ||
| + | |||
| + | ===== Verification ===== | ||
| + | |||
| + | Verification SHALL confirm that the Conceptual Architecture preserves separation between conceptual meaning, logical structure, implementation mapping, deployment mechanics, testability, | ||
| + | |||
| + | Verification activities should include review checks confirming that: | ||
| + | |||
| + | * Conceptual material defines meaning without depending on logical structure; | ||
| + | * Logical material refines conceptual meaning without replacing it; | ||
| + | * Implementation mappings identify technology realisations without redefining conceptual elements; | ||
| + | * Deployment material describes operational arrangements without changing conceptual meaning; and | ||
| + | * Testability and evidence material support architectural claims without becoming the conceptual basis for those claims. | ||
| + | |||
| + | ===== Traceability ===== | ||
| + | |||
| + | This requirement supports traceability from conceptual meaning through logical modeling, implementation mapping, deployment realization, | ||
| + | |||
| + | Related requirement identifiers: | ||
| + | |||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | |||
| + | Related source section: | ||
| + | |||
| + | * [[fxdemo: | ||
| + | |||
| + | ===== Status ===== | ||
| + | |||
| + | Draft | ||