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-02:p2-req-16-6-004 [2026/07/11 12:57] – ↷ Page moved from dido:99_annexes:annex-c-requirements:part-02:p2-req-16-6-004 to dido:99_annexes:annex-d-requirements:part-02:p2-req-16-6-004 nick_didodido:99_annexes:annex-d-requirements:part-02:p2-req-16-6-004 [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 1: Line 1:
 ====== P2-REQ-16-6-004 ====== ====== P2-REQ-16-6-004 ======
  
-[[dido:99_annexes:annex-c-requirements:part-02:start| Return to Requirements]]+[[dido:99_annexes:annex-d-requirements:part-02:start| Return to Requirements]]
  
 ===== Statement ===== ===== Statement =====
  
-The [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_health_and_observability_plane|Logical Health and Observability Plane]] SHALL support observation of operational condition and behaviour.+The [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_health_and_observability_plane|Logical Health and Observability Plane]] SHALL support observation of operational condition and behavior.
  
 ===== Source ===== ===== Source =====
Line 13: Line 13:
 ===== Rationale ===== ===== Rationale =====
  
-The Logical Health and Observability Plane provides architectural support for observing the operational condition and behaviour of the distributed system. Separating observability from operational control and domain information improves governance, monitoring, diagnostics, and architectural review while remaining independent of monitoring technologies.+The Logical Health and Observability Plane provides architectural support for observing the operational condition and behavior of the distributed system. Separating observability from operational control and domain information improves governance, monitoring, diagnostics, and architectural review while remaining independent of monitoring technologies.
  
 ===== Applies To ===== ===== Applies To =====
Line 24: Line 24:
   * Operational observation;   * Operational observation;
   * Health reporting; and   * Health reporting; and
-  * Behaviour reporting.+  * Behavior reporting.
  
 ===== Verification ===== ===== Verification =====
  
-Verification SHALL confirm that the Logical Health and Observability Plane supports observation of operational condition and behaviour.+Verification SHALL confirm that the Logical Health and Observability Plane supports observation of operational condition and behavior.
  
 Verification activities should include review checks confirming that: Verification activities should include review checks confirming that:
  
   * operational condition is represented within the Logical Health and Observability Plane;   * operational condition is represented within the Logical Health and Observability Plane;
-  * behavioural observations are represented;+  * behavioral observations are represented;
   * observability concerns remain distinct from control and data concerns; and   * observability concerns remain distinct from control and data concerns; and
   * implementation technologies do not redefine the Runtime Plane.   * implementation technologies do not redefine the Runtime Plane.
Line 43: Line 43:
 Related requirement identifiers: Related requirement identifiers:
  
-  * [[dido:99_annexes:annex-c-requirements:part-02:p2-req-16-6-001]] +  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-6-001]] 
-  * [[dido:99_annexes:annex-c-requirements:part-02:p2-req-16-7-002]] +  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-7-002]] 
-  * [[dido:99_annexes:annex-c-requirements:part-02:p2-req-16-9-004]]+  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-9-004]]
  
 Related source section: Related source section:
  • dido/99_annexes/annex-d-requirements/part-02/p2-req-16-6-004.1783799868.txt.gz
  • Last modified: 2026/07/11 12:57
  • by nick_dido