dido:99_annexes:annex-d-requirements:part-01:p1-req-13-4-005:start

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-01:p1-req-13-4-005:start [2026/07/11 12:57] – ↷ Links adapted because of a move operation nick_didodido:99_annexes:annex-d-requirements:part-01:p1-req-13-4-005:start [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 5: Line 5:
 ===== Statement ===== ===== Statement =====
  
-A [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]] SHALL classify runtime communication and behaviour by architectural purpose.+A [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]] SHALL classify runtime communication and behavior by architectural purpose.
  
 ===== Source ===== ===== Source =====
Line 13: Line 13:
 ===== Rationale ===== ===== Rationale =====
  
-A Runtime Plane groups runtime communication and behaviour according to architectural purpose. This classification supports separation of concerns across data exchange, control, health and observability, policy and release, audit and provenance, and other governed runtime purposes.+A Runtime Plane groups runtime communication and behavior according to architectural purpose. This classification supports separation of concerns across data exchange, control, health and observability, policy and release, audit and provenance, and other governed runtime purposes.
  
 This requirement prevents runtime concerns with different purposes from becoming indistinct or unmanaged. This requirement prevents runtime concerns with different purposes from becoming indistinct or unmanaged.
Line 24: Line 24:
  
   * Runtime communication   * Runtime communication
-  * Runtime behaviour+  * Runtime behavior
   * Architectural purpose   * Architectural purpose
   * Plane separation   * Plane separation
Line 31: Line 31:
 ===== Verification ===== ===== Verification =====
  
-Verification SHALL confirm that each Runtime Plane classifies runtime communication and behaviour by architectural purpose.+Verification SHALL confirm that each Runtime Plane classifies runtime communication and behavior by architectural purpose.
  
 Verification activities include review checks confirming that: Verification activities include review checks confirming that:
Line 37: Line 37:
   * Runtime Plane descriptions identify architectural purpose   * Runtime Plane descriptions identify architectural purpose
   * Runtime communication maps to an appropriate Runtime Plane   * Runtime communication maps to an appropriate Runtime Plane
-  * Runtime behaviour maps to an appropriate Runtime Plane+  * Runtime behavior maps to an appropriate Runtime Plane
   * Runtime Planes remain distinct from implementation technologies and deployment boundaries   * Runtime Planes remain distinct from implementation technologies and deployment boundaries
  
  • dido/99_annexes/annex-d-requirements/part-01/p1-req-13-4-005/start.1783799875.txt.gz
  • Last modified: 2026/07/11 12:57
  • by nick_dido