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

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
dido:99_annexes:annex-d-requirements:part-00:p0-req-10-002 [2026/07/11 12:57] – ↷ Links adapted because of a move operation nick_didodido:99_annexes:annex-d-requirements:part-00:p0-req-10-002 [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 13: Line 13:
 ===== Rationale ===== ===== Rationale =====
  
-The Financial Systems Archetype document set depends on a clear conceptual foundation. Financial-system concepts establish the meaning of the architecture before those concepts are refined into logical structures, mapped to implementation technologies, or realised in deployment environments.+The Financial Systems Archetype document set depends on a clear conceptual foundation. Financial-system concepts establish the meaning of the architecture before those concepts are refined into logical structures, mapped to implementation technologies, or realized in deployment environments.
  
 If logical models, implementation profiles, or deployment profiles are defined before the underlying concepts are established, technology choices can begin to shape or distort the conceptual architecture. This requirement preserves the discipline that meaning comes first, logical structure comes second, implementation mapping comes third, and deployment comes only after the relevant abstractions have been defined. If logical models, implementation profiles, or deployment profiles are defined before the underlying concepts are established, technology choices can begin to shape or distort the conceptual architecture. This requirement preserves the discipline that meaning comes first, logical structure comes second, implementation mapping comes third, and deployment comes only after the relevant abstractions have been defined.
Line 19: Line 19:
 ===== Applies To ===== ===== 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: It applies specifically to:
Line 39: Line 39:
 * logical models refine defined financial-system concepts rather than inventing new meanings; * logical models refine defined financial-system concepts rather than inventing new meanings;
 * implementation profiles map to logical elements rather than defining architecture directly; * implementation profiles map to logical elements rather than defining architecture directly;
-* deployment profiles realise implementation profiles rather than bypassing conceptual or logical definitions; and+* deployment profiles realize implementation profiles rather than bypassing conceptual or logical definitions; and
 * later document parts preserve the meanings established in earlier conceptual sections. * later document parts preserve the meanings established in earlier conceptual sections.
  
  • dido/99_annexes/annex-d-requirements/part-00/p0-req-10-002.1783799872.txt.gz
  • Last modified: 2026/07/11 12:57
  • by nick_dido