Differences

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

--- dido:99_annexes:annex-d-requirements:part-02:p2-req-16-4-008 [2026/07/11 12:57] – ↷ Page moved from dido:99_annexes:annex-c-requirements:part-02:p2-req-16-4-008 to dido:99_annexes:annex-d-requirements:part-02:p2-req-16-4-008 nick_dido
+++ dido:99_annexes:annex-d-requirements:part-02:p2-req-16-4-008 [2026/07/18 12:33] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
 ====== P2-REQ-16-4-008 ======
-[[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 =====
-The Logical Architecture / PIM SHALL support communication pattern independence by distinguishing logical communication relationships from the implementation mechanisms that realise them.
+The Logical Architecture / PIM SHALL support communication pattern independence by distinguishing logical communication relationships from the implementation mechanisms that realize them.
 ===== Source =====
@@ Line 13: / Line 13: @@
 ===== Rationale =====
-Logical communication relationships describe architectural intent rather than implementation behaviour. Distinguishing logical communication from implementation mechanisms allows different communication patterns, protocols, middleware products, and runtime infrastructures to realise the same logical relationships without altering the architecture. This separation preserves platform independence while supporting interoperability, governance, and long-term architectural evolution.
+Logical communication relationships describe architectural intent rather than implementation behavior. Distinguishing logical communication from implementation mechanisms allows different communication patterns, protocols, middleware products, and runtime infrastructures to realize the same logical relationships without altering the architecture. This separation preserves platform independence while supporting interoperability, governance, and long-term architectural evolution.
 ===== Applies To =====
-This requirement applies to the Logical Communication Model and all profiles that specialise or realise it.
+This requirement applies to the Logical Communication Model and all profiles that specialize or realize it.
 It applies specifically to:
@@ Line 30: / Line 30: @@
 ===== Verification =====
-Verification SHALL confirm that logical communication relationships remain independent of the implementation mechanisms that realise them.
+Verification SHALL confirm that logical communication relationships remain independent of the implementation mechanisms that realize them.
 Verification activities should include review checks confirming that:
@@ Line 41: / Line 41: @@
 ===== Traceability =====
-This requirement supports traceability between logical communication relationships and the implementation mechanisms that realise them while preserving platform independence.
+This requirement supports traceability between logical communication relationships and the implementation mechanisms that realize them while preserving platform independence.
 Related requirement identifiers:
-  * [[dido:99_annexes:annex-c-requirements:part-02:p2-req-16-4-001]]
+  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-4-001]]
-  * [[dido:99_annexes:annex-c-requirements:part-02:p2-req-16-4-005]]
+  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-4-005]]
-  * [[dido:99_annexes:annex-c-requirements:part-02:p2-req-16-4-007]]
+  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-4-007]]
   * [[fxdemo:dido_99_annexes:annex-c-requirements:part-02:p2-req-16-10-007]]