Differences

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

--- dido:99_annexes:annex-d-requirements:part-01:p1-req-13-2-001:start [2026/07/11 12:57] – ↷ Links adapted because of a move operation nick_dido
+++ 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 15: / Line 15: @@
 The Conceptual Architecture defines a stable meaning for the Financial Systems Archetype. Logical structure, implementation mapping, deployment mechanics, testability, and evidence serve different architectural purposes and operate at different levels of abstraction.
-Preserving separation prevents implementation or deployment decisions from altering the architecture's conceptual meaning. It also supports traceability from conceptual intent through logical modelling, implementation mapping, deployment realisation, verification, and evidence collection.
+Preserving separation prevents implementation or deployment decisions from altering the architecture's conceptual meaning. It also supports traceability from conceptual intent through logical modeling, implementation mapping, deployment realization, verification, and evidence collection.
 ===== Applies To =====
-This requirement applies to the organisation, interpretation, review, and maintenance of the Conceptual Architecture.
+This requirement applies to the organization, interpretation, review, and maintenance of the Conceptual Architecture.
 It applies specifically to the separation among:
@@ Line 44: / Line 44: @@
 ===== Traceability =====
-This requirement supports traceability from conceptual meaning through logical modelling, implementation mapping, deployment realisation, verification, and evidence collection.
+This requirement supports traceability from conceptual meaning through logical modeling, implementation mapping, deployment realization, verification, and evidence collection.
 Related requirement identifiers: