Differences

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

--- dido:99_annexes:annex-d-requirements:part-00:p0-req-10-004 [2026/07/11 12:57] – ↷ Links adapted because of a move operation nick_dido
+++ dido:99_annexes:annex-d-requirements:part-00:p0-req-10-004 [2026/07/18 12:33] (current) – external edit 127.0.0.1
@@ Line 13: / Line 13: @@
 ===== Rationale =====
-The Financial Systems Archetype document set separates architectural meaning from implementation choice. Conceptual architecture defines what the financial system means, what responsibilities it has, and how its major concepts relate. Implementation technologies provide mechanisms for realising those concepts, but they do not define the concepts themselves.
+The Financial Systems Archetype document set separates architectural meaning from implementation choice. Conceptual architecture defines what the financial system means, what responsibilities it has, and how its major concepts relate. Implementation technologies provide mechanisms for realizing those concepts, but they do not define the concepts themselves.
 If implementation technologies are allowed to redefine conceptual architecture, the architecture becomes dependent on a particular tool, platform, messaging technology, data format, programming model, or deployment environment. This would weaken portability, reduce long-term governance, and make it harder to compare or evolve implementations without changing the underlying architectural meaning.
@@ Line 19: / Line 19: @@
 ===== Applies To =====
-This requirement applies to the organisation, authoring, review, maintenance, and interpretation of the Financial Systems Archetype document set.
+This requirement applies to the organization, authoring, review, maintenance, and interpretation of the Financial Systems Archetype document set.
 It applies specifically to:
@@ Line 28: / Line 28: @@
 * deployment profiles;
 * technology mappings;
-* platform-specific artefacts; and
+* platform-specific artifacts; and
 * evidence or verification material that refers to implementation technologies.
 ===== Verification =====
-Verification SHALL confirm that implementation technologies are treated as realisation mechanisms and not as sources of conceptual meaning.
+Verification SHALL confirm that implementation technologies are treated as realization mechanisms and not as sources of conceptual meaning.
 Verification activities should include review checks confirming that:
 * conceptual architecture sections do not depend on a specific implementation technology;
-* implementation profiles map logical elements to technology artefacts without redefining the logical or conceptual elements;
+* implementation profiles map logical elements to technology artifacts without redefining the logical or conceptual elements;
 * technology-specific terminology is not used as a substitute for conceptual definitions;
 * deployment choices do not alter the architectural meaning of the elements being deployed;