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-001 [2026/07/11 12:57] – ↷ Links adapted because of a move operation nick_didodido:99_annexes:annex-d-requirements:part-00:p0-req-10-001 [2026/07/18 12:33] (current) – external edit 127.0.0.1
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 the separation among: It applies specifically to the separation among:
Line 37: Line 37:
   * Conceptual sections define meaning without depending on implementation technology;   * Conceptual sections define meaning without depending on implementation technology;
   * Logical sections refine conceptual elements without redefining them;   * Logical sections refine conceptual elements without redefining them;
-  * Implementation profiles map logical elements to implementation artefacts without changing their meaning;+  * Implementation profiles map logical elements to implementation artifacts without changing their meaning;
   * Deployment profiles describe executable or operational arrangements without replacing architectural definitions; and   * Deployment profiles describe executable or operational arrangements without replacing architectural definitions; and
   * Evidence sections support claims made elsewhere in the document set.   * Evidence sections support claims made elsewhere in the document set.
Line 43: Line 43:
 ===== Traceability ===== ===== Traceability =====
  
-This requirement supports traceability from high-level conceptual architecture through logical modelling, implementation mapping, deployment realisation, and evidence collection.+This requirement supports traceability from high-level conceptual architecture through logical modeling, implementation mapping, deployment realization, and evidence collection.
  
 Related requirement identifiers: Related requirement identifiers:
  • dido/99_annexes/annex-d-requirements/part-00/p0-req-10-001.1783799872.txt.gz
  • Last modified: 2026/07/11 12:57
  • by nick_dido