3.1 Traceability to SIP-RA [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== 3.1 Traceability to SIP-RA ======

[[fxdemo:04-part:03-traceability-to-parent-and-source-architectures:start | Go To Traceability to Parent and Source Architectures ]]

SIP-RA supplies the parent architecture discipline for structured information processing systems. This part applies and specializes that discipline for the Phase 0 implementation of the FX Demo.

The Phase 0 Implementation Profile preserves the SIP-RA emphasis on structured information, explicit interfaces, separation of concerns, [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|traceable interpretation]], governed processing, reviewability, and implementation discipline. It applies those concerns by mapping selected FX logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Nodes]], logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_communication_endpoint|Communication Endpoints]], logical information structures, [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]] classifications, interaction patterns, and traceability relationships to concrete Phase 0 implementation artifacts.

<WRAP table-caption>
**Table 3-1:** SIP-RA concerns addressed by the Phase 0 Implementation Profile.
</WRAP>

^ SIP-RA concern ^ Part 4: Phase 0 implementation treatment ^
| Structured information processing | Maps selected FX logical information structures to [[dido:99_annexes:annex-b-terms-and-definitions:i:idl|IDL]] structures, generated types, and implementation-level data representations. |
| Explicit interfaces | Maps selected FX logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_communication_endpoint|Communication Endpoints]] to [[dido:99_annexes:annex-b-terms-and-definitions:d:dds|DDS]] Topics or other selected communication artifacts. |
| Separation of concerns | Preserves the distinction among implementation artifacts that realize Control, Data, Health and Observability, Policy and Release, and Audit and Provenance. |
| Traceable interpretation | Preserves [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|traceability]] from implementation artifacts to the FX logical elements, inherited logical elements, and conceptual elements they realize. |
| Governed processing across boundaries | Defines implementation mappings that support policy-controlled release and audit/provenance obligations. |
| Audit and review | Identifies implementation artifacts that support later deployment, observation, testability, audit, provenance, replay, reconstruction, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|evidence]] planning. |
| Implementation discipline | Requires coding, logging, exception-handling, generation, file-header, and repository conventions through the Phase 0 Developer Handbook. |

----

<WRAP centeralign>

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

</WRAP>