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

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
dido:99_annexes:annex-d-requirements:part-00:p0-req-10-001 [2026/07/11 12:57] – removed - external edit (Unknown date) 127.0.0.1dido:99_annexes:annex-d-requirements:part-00:p0-req-10-001 [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 1: Line 1:
 +====== P0-REQ-10-001 ======
 +
 +[[dido:99_annexes:annex-d-requirements:part-00:start| Return to Requirements]]
 +
 +===== Statement =====
 +
 +The document set SHALL preserve separation between conceptual, logical, implementation, deployment, and evidence concerns.
 +
 +===== Source =====
 +
 +Part 0, Section 10: Document Set Requirements.
 +
 +===== Rationale =====
 +
 +The Financial Systems Archetype document set is intended to preserve a clear separation of concerns across the full architecture lifecycle. Conceptual meaning, logical structure, implementation mapping, deployment mechanics, and evidence each serve different purposes and are governed at different levels of abstraction.
 +
 +Without this separation, implementation choices could obscure or distort the conceptual architecture, logical models could become dependent on particular technologies, and evidence could be treated as an implementation detail rather than as a governed basis for verification. Maintaining separation makes the document set easier to govern, review, extend, and trace.
 +
 +===== Applies To =====
 +
 +This requirement applies to the organization, authoring, review, maintenance, and interpretation of the Financial Systems Archetype document set.
 +
 +It applies specifically to the separation among:
 +
 +  * Conceptual architecture;
 +  * Logical models;
 +  * Implementation profiles;
 +  * Deployment profiles; and
 +  * Evidence and verification material.
 +
 +===== Verification =====
 +
 +Verification SHALL confirm that each part of the document set has a distinct architectural responsibility and does not collapse one concern into another.
 +
 +Verification activities should include review checks confirming that:
 +
 +  * Conceptual sections define meaning without depending on implementation technology;
 +  * Logical sections refine conceptual elements without redefining them;
 +  * Implementation profiles map logical elements to implementation artifacts without changing their meaning;
 +  * Deployment profiles describe executable or operational arrangements without replacing architectural definitions; and
 +  * Evidence sections support claims made elsewhere in the document set.
 +
 +===== Traceability =====
 +
 +This requirement supports traceability from high-level conceptual architecture through logical modeling, implementation mapping, deployment realization, and evidence collection.
 +
 +Related requirement identifiers:
 +
 +  * [[dido:99_annexes:annex-d-requirements:part-00:p0-req-10-002]]
 +  * [[dido:99_annexes:annex-d-requirements:part-00:p0-req-10-003]]
 +  * [[dido:99_annexes:annex-d-requirements:part-00:p0-req-10-004]]
 +
 +Related source section:
 +
 +  * [[fxdemo:00-part:11-document-set-requirements:start]]
 +
 +===== Status =====
 +
 +Draft