3.8 Traceability Position

Go To Traceability to Parent and Source Architectures

This part uses the following traceability position.

SIP-RA provides the parent structured information-processing discipline. FDIS-RA provides financial-domain interpretation alignment. Part 1 provides the conceptual foundation. Part 2 provides the reusable distributed, node-based Logical Architecture / Platform-Independent Model (PIM). Part 3 provides the FX Demo Logical Profile. Phase 0 implementation source material provides the selected implementation context. The Phase 0 Developer Handbook provides the detailed development discipline required before coding begins.

This traceability position prevents four kinds of confusion.

1. It prevents Phase 0 implementation artifacts from redefining the Part 1 Conceptual Architecture.
2. It prevents implementation artifacts from redefining the Part 2 Logical Architecture / Platform-Independent Model (PIM).
3. It prevents DDS, IDL, Quality of Service (QoS) profiles, generated types, Python scripts, repository layout, or other implementation mechanisms from redefining the Part 3 FX Demo Logical Profile.
4. It prevents the Phase 0 Developer Handbook from replacing the implementation profile.

Part 4 defines the Phase 0 Implementation Profile / Platform-Specific Model (PSM). Later development phases may define additional implementation profiles that extend, refine, supersede, or replace this profile while preserving traceability to the applicable conceptual, logical, domain logical, implementation, and Developer Handbook artifacts.