fxdemo:02-part:03-traceability-to-parent-and-source-architectures:03-5-traceability-position: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
fxdemo:02-part:03-traceability-to-parent-and-source-architectures:03-5-traceability-position:start [2026/07/11 11:07] – ↷ Links adapted because of a move operation nick_didofxdemo:02-part:03-traceability-to-parent-and-source-architectures:03-5-traceability-position:start [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 2: Line 2:
 [[fxdemo:02-part:start | Go To Top ]] [[fxdemo:02-part:start | Go To Top ]]
  
-This part uses the following [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] position.+This part uses the following [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] position.
  
-SIP-RA provides the parent with a structured information processing discipline. FDIS-RA provides financial-domain interpretation alignment. Part 1 provides the conceptual foundation. The original FX Demo Reference Architecture provides source material that this part normalises into a distributed, node-based Logical Architecture / PIM.+SIP-RA provides the parent with a structured information processing discipline. FDIS-RA provides financial-domain interpretation alignment. Part 1 provides the conceptual foundation. The original FX Demo Reference Architecture provides source material that this part normalizes into a distributed, node-based Logical Architecture / PIM.
  
 This traceability position prevents three kinds of confusion. This traceability position prevents three kinds of confusion.
Line 10: Line 10:
 First, it prevents the Logical Architecture / PIM from replacing the Part 1 Conceptual Architecture. Second, it prevents the original FX Demo Reference Architecture from remaining a mixed-layer controlling document. Third, it prevents implementation mechanisms such as DDS, REST, RPC, Protocol Buffers, IDL, Python, Kubernetes, K3S, Docker, RTI Connext DDS, or Crucible from defining the logical architecture. First, it prevents the Logical Architecture / PIM from replacing the Part 1 Conceptual Architecture. Second, it prevents the original FX Demo Reference Architecture from remaining a mixed-layer controlling document. Third, it prevents implementation mechanisms such as DDS, REST, RPC, Protocol Buffers, IDL, Python, Kubernetes, K3S, Docker, RTI Connext DDS, or Crucible from defining the logical architecture.
  
-Part 2 defines one platform-independent, distributed, node-based logical architecture. Later parts specialise, implement, deploy, test, and [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:e:evidence|evidence]] the Logical Architecture while preserving [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] back to Part 1.+Part 2 defines one platform-independent, distributed, node-based logical architecture. Later parts specialize, implement, deploy, test, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|evidence]] the Logical Architecture while preserving [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] back to Part 1.
  
 ---- ----
  • fxdemo/02-part/03-traceability-to-parent-and-source-architectures/03-5-traceability-position/start.1783793235.txt.gz
  • Last modified: 2026/07/11 11:07
  • by nick_dido