dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-007:start

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-007:start [2026/07/11 12:57] – ↷ Page moved from dido:99_annexes:annex-c-requirements:part-01:p1-req-13-5-007:start to dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-007:start nick_didodido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-007:start [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 1: Line 1:
 ====== P1-REQ-13-5-007 ====== ====== P1-REQ-13-5-007 ======
  
-[[dido:99_annexes:annex-c-requirements:part-01:start|Return to Part 1 Requirements]]+[[dido:99_annexes:annex-d-requirements:part-01:start|Return to Part 1 Requirements]]
  
 ===== Statement ===== ===== Statement =====
Line 13: Line 13:
 ===== Rationale ===== ===== Rationale =====
  
-Runtime Planes classify runtime communication and behaviour by architectural purpose. Implementation mechanisms realise selected aspects of those planes in a particular technology environment.+Runtime Planes classify runtime communication and behavior by architectural purpose. Implementation mechanisms realize selected aspects of those planes in a particular technology environment.
  
 Distinguishing Runtime Planes from implementation mechanisms prevents DDS topics, middleware constructs, APIs, services, scripts, generated types, containers, or other mechanisms from redefining the conceptual plane. Distinguishing Runtime Planes from implementation mechanisms prevents DDS topics, middleware constructs, APIs, services, scripts, generated types, containers, or other mechanisms from redefining the conceptual plane.
Line 39: Line 39:
  
   * Runtime Planes classify architectural purpose   * Runtime Planes classify architectural purpose
-  * Implementation mechanisms realise Runtime Planes without redefining them+  * Implementation mechanisms realize Runtime Planes without redefining them
   * Technology examples do not become conceptual plane definitions   * Technology examples do not become conceptual plane definitions
   * Later profiles preserve the conceptual meaning of each Runtime Plane   * Later profiles preserve the conceptual meaning of each Runtime Plane
Line 51: Line 51:
 Related requirement identifiers: Related requirement identifiers:
  
-  * [[dido:99_annexes:annex-c-requirements:part-01:p1-req-13-5-001:start]] +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-001:start]] 
-  * [[dido:99_annexes:annex-c-requirements:part-01:p1-req-13-5-008:start]] +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-008:start]] 
-  * [[dido:99_annexes:annex-c-requirements:part-01:p1-req-13-2-003:start]] +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-2-003:start]] 
-  * [[dido:99_annexes:annex-c-requirements:part-01:p1-req-13-2-004:start]]+  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-2-004:start]]
  
 ===== Status ===== ===== Status =====
  • dido/99_annexes/annex-d-requirements/part-01/p1-req-13-5-007/start.1783799863.txt.gz
  • Last modified: 2026/07/11 12:57
  • by nick_dido