fxdemo:01-part:04-traceability-to-parent-and-source-architectures:04-2-alignment-with-fdis-ra

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:01-part:04-traceability-to-parent-and-source-architectures:04-2-alignment-with-fdis-ra [2026/06/26 15:56] – owenfxdemo:01-part:04-traceability-to-parent-and-source-architectures:04-2-alignment-with-fdis-ra [2026/07/11 11:15] (current) – ↷ Links adapted because of a move operation nick_dido
Line 2: Line 2:
 [[fxdemo:01-part:start | Go to Top ]] [[fxdemo:01-part:start | Go to Top ]]
  
-FDIS-RA provides financial-domain architectural precedent for systems that interpret, validate, compare, and govern regulated data. The Financial Systems Archetype aligns with FDIS-RA by treating meaning, interpretation, validation, provenance, comparability, and evidence as architectural concerns rather than implementation by-products. +FDIS-RA provides financial-domain architectural precedent for systems that [[dido:99_annexes:annex-b-terms-and-definitions:i:interpretation|Interpret]], validate, compare, and govern regulated [[dido:99_annexes:annex-b-terms-and-definitions:d:data|Data]]. The Financial Systems Archetype aligns with FDIS-RA by treating meaning, [[dido:99_annexes:annex-b-terms-and-definitions:i:interpretation|Interpretation]], validation, provenance, comparability, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] as architectural concerns rather than implementation by-products. 
-FDIS-RA does not replace SIP-RA as the parent reference architecture. Instead, FDIS-RA informs the financial-domain interpretation concerns that the Financial Systems Archetype must preserve.+ 
 +FDIS-RA does not replace SIP-RA as the parent [[dido:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture (RA)]]. Instead, FDIS-RA informs the financial-domain interpretation concerns that the Financial Systems Archetype must preserve. 
 Part 1 uses FDIS-RA as an alignment source for the following conceptual concerns. Part 1 uses FDIS-RA as an alignment source for the following conceptual concerns.
  
 Table 3-2: FDIS-RA concerns aligned with the Conceptual Architecture Table 3-2: FDIS-RA concerns aligned with the Conceptual Architecture
 +
 ^ FDIS-RA concern ^ Part 1 treatment ^ ^ FDIS-RA concern ^ Part 1 treatment ^
-| Semantic interpretation as an architectural concern | Defines semantics, interpretation, and governance of meaning as conceptual concerns. | +| Semantic [[dido:99_annexes:annex-b-terms-and-definitions:i:interpretation|Interpretation]] as an architectural concern | Defines [[dido:99_annexes:annex-b-terms-and-definitions:s:semantic|Semantics]], [[dido:99_annexes:annex-b-terms-and-definitions:i:interpretation|Interpretation]], and governance of meaning as conceptual concerns. | 
-| Separation of evidence, observation, interpretation, validation, and analytical consumption | Defines separation of concerns and runtime-plane concepts. | +| Separation of [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]], observation, [[dido:99_annexes:annex-b-terms-and-definitions:i:interpretation|Interpretation]], validation, and analytical consumption | Defines separation of concerns and [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]] concepts. | 
-| Traceability and provenance | Defines Traceability and Evidence as core conceptual elements. | +| [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability_and_evidence|Traceability and Evidence]] | Defines [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] as core conceptual elements. | 
-| Auditability and defensibility | Treats evidence as an architectural concern rather than a test by-product. |+| Auditability and defensibility | Treats [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] as an architectural concern rather than a test by-product. |
 | Comparability across systems and time | Preserves conceptual meaning independently from implementation technology. | | Comparability across systems and time | Preserves conceptual meaning independently from implementation technology. |
 | Technology neutrality | Avoids binding conceptual architecture to specific products, tools, languages, middleware, or deployment platforms. | | Technology neutrality | Avoids binding conceptual architecture to specific products, tools, languages, middleware, or deployment platforms. |
 | Long-term governance of meaning | Defines governance of meaning as a conceptual architecture principle. | | Long-term governance of meaning | Defines governance of meaning as a conceptual architecture principle. |
 +
 +----
 +
 +<WRAP centeralign>
 +
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +
 +</WRAP>
 +
 +
  • fxdemo/01-part/04-traceability-to-parent-and-source-architectures/04-2-alignment-with-fdis-ra.1782514619.txt.gz
  • Last modified: 2026/06/26 15:56
  • by owen