Show pageOld revisionsBacklinksAdd to bookExport to PDFODT exportBack to top Backlinks This is a list of pages that seem to link back to the current page. Application Programming Interface (API)Data Structure InstanceDFX Information Structure TraceabilityFX Transaction CandidatePart 1 Concept to FX Logical Profile ElementPart 1 Concept to FX Logical Profile ElementRecordTraceabilityP1-REQ-13-4-001P1-REQ-13-4-007P1-REQ-13-4-008P1-REQ-13-4-011P1-REQ-13-4-012P1-REQ-13-9-003Introduction1. Scope3.1 Traceability to SIP-RA3.3 Coverage of the Original FX Demo Reference Architecture3. Traceability to Parent and Source Architectures7.1 Overview7.7 Data Structure Definition8.7 Cross-Plane Relationships9.8 Cross-Concern Relationships10.3 Conceptual Element to Logical Element / PIM10.4 Logical Element / PIM to Implementation Artifact / PSM10.7 Bidirectional Review and Impact Analysis11.2 Conceptual Elements Remain Distinct11.3 Conceptual Architecture Does Not Prescribe Realization Mechanisms11.6 Implementation Mappings Do Not Redefine Concepts12.2 Conceptual Elements Become Logical Elements12.3 Logical Architecture Preserves Conceptual Meaning12.6 Logical Architecture Provides the Basis for Implementation Profiles12.7 Traceability from Part 1 to Part 213.4 Core Conceptual Element Requirements13.9 Relationship to Logical Architecture / PIM Requirements3.3 Traceability to Part 1 Conceptual Architecture4.6 Traceability from Concept to Logical Model5.7 Logical Traceability Model8.1 Overview13.4 What Domain Profiles Preserve3.3 Traceability to Part 1 Conceptual Architecture5.8 FX Demo Logical Traceability Model7.11 Spelling, Grammar, and Style18.5 Control Plane Acceptance Criteria18.6 Data Plane Acceptance Criteria19.2 Full ACTUS Processing19.5 Full IEF Policy Enforcement dido/99_annexes/annex-b-terms-and-definitions/d/data_structure_definition.txt Last modified: 2026/07/18 12:33by 127.0.0.1