Differences

This shows you the differences between two versions of the page.

--- dido:99_annexes:annex-b-terms-and-definitions:r:reference_architecture [2026/07/11 11:14] – ↷ Page moved from dido:99_annexes:99_annexes:annex-b-terms-and-definitions:r:reference_architecture to dido:99_annexes:annex-b-terms-and-definitions:r:reference_architecture nick_dido
+++ dido:99_annexes:annex-b-terms-and-definitions:r:reference_architecture [2026/07/18 12:33] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
 ====== Reference Architecture (RA) ======
-[[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:start|Return to Terms and Definitions]]
+[[dido:99_annexes:annex-b-terms-and-definitions:start|Return to Terms and Definitions]]
 ===== Discussion =====
@@ Line 7: / Line 7: @@
 A Reference Architecture (RA) provides a shared architectural frame for a recurring class of problems. It establishes a common language for stakeholder communities, promotes consistency in addressing recurring architectural concerns, supports validation and comparison across independently developed systems, and encourages alignment with common standards, specifications, and architectural patterns.
-A Reference Architecture is neither an implementation nor a detailed system design. It provides a conceptual and logical framework that establishes shared understanding, defines architectural responsibilities, and enables comparability across systems developed by different organisations or teams.
+A Reference Architecture is neither an implementation nor a detailed system design. It provides a conceptual and logical framework that establishes shared understanding, defines architectural responsibilities, and enables comparability across systems developed by different organizations or teams.
-In the Financial Systems Archetype, a Reference Architecture identifies where architectural authority lies for key concerns such as semantic interpretation, validation, governance, controlled evolution of meaning, traceability, and evidence. It does not prescribe how organisations must implement those concerns in specific representations, technologies, tools, products, or deployment environments.
+In the Financial Systems Archetype, a Reference Architecture identifies where architectural authority lies for key concerns such as semantic interpretation, validation, governance, controlled evolution of meaning, traceability, and evidence. It does not prescribe how organizations must implement those concerns in specific representations, technologies, tools, products, or deployment environments.
 ===== Definition =====
@@ Line 25: / Line 25: @@
 A Reference Architecture defines architectural authority and shared structure. It does not itself define a product, runtime, deployment, implementation stack, database, message format, model repository, or toolchain.
-A Reference Architecture may be formalised later using modelling techniques, such as SysML v2 as a Platform-Independent Model (PIM), aligned with OMG Model-Driven Architecture (MDA) principles. Such formalisation can express architectural elements, interfaces, constraints, and traceability more precisely, but it does not change the purpose of the Reference Architecture.
+A Reference Architecture may be formalized later using modeling techniques, such as SysML v2 as a Platform-Independent Model (PIM), aligned with OMG Model-Driven Architecture (MDA) principles. Such formalization can express architectural elements, interfaces, constraints, and traceability more precisely, but it does not change the purpose of the Reference Architecture.
 ===== Example =====
 The Financial Data Interpretation Systems Reference Architecture (FDIS-RA) provides a stable architectural foundation for regulated data interpretation. It clarifies how concerns such as evidence intake, information extraction, observation management, semantic representation, rule-based interpretation, validation, and standards alignment relate to one another across system boundaries.