| Both sides previous revision Previous revision Next revision | Previous revision |
| fxdemo:01-part:04-traceability-to-parent-and-source-architectures:04-4-traceability-position [2026/07/11 11:07] – ↷ Links adapted because of a move operation nick_dido | fxdemo:01-part:04-traceability-to-parent-and-source-architectures:04-4-traceability-position [2026/07/18 12:33] (current) – external edit 127.0.0.1 |
|---|
| [[fxdemo:01-part:start | Go to Top ]] | [[fxdemo:01-part:start | Go to Top ]] |
| |
| The Financial Systems Archetype uses the following [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] position. | The Financial Systems Archetype 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 [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:i:interpretation|Interpretation]] alignment. The original FX Demo [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]] provides source material that the new document set normalises across the proper architectural layers. | SIP-RA provides the parent with a structured information processing discipline. FDIS-RA provides financial-domain [[dido:99_annexes:annex-b-terms-and-definitions:i:interpretation|Interpretation]] alignment. The original FX Demo [[dido:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]] provides source material that the new document set normalizes across the proper architectural layers. |
| |
| This [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] position prevents three kinds of confusion. | This [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] position prevents three kinds of confusion. |
| |
| First, it prevents FDIS-RA from replacing SIP-RA as the parent [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]]. Second, it prevents the original FX Demo [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]] from remaining a mixed-layer controlling document. Third, it prevents implementation details from moving upward into the conceptual architecture. | First, it prevents FDIS-RA from replacing SIP-RA as the parent [[dido:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]]. Second, it prevents the original FX Demo [[dido:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]] from remaining a mixed-layer controlling document. Third, it prevents implementation details from moving upward into the conceptual architecture. |
| |
| Part 1, therefore, defines only the conceptual architecture. Later parts carry forward logical, domain-profile, implementation, deployment, testability, and [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] concerns while preserving [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] back to this conceptual foundation. | Part 1, therefore, defines only the conceptual architecture. Later parts carry forward logical, domain-profile, implementation, deployment, testability, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] concerns while preserving [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] back to this conceptual foundation. |
| |
| ---- | ---- |