This is an old revision of the document!
5.2.1 Domain
The source model associates a Domain with Test.
Discussion
A Domain identifies a specific business or semantic area within an Ecosystem. It provides the classification level most directly associated with a domain profile.
Within the Monetary Ecosystem, a Domain may identify an area such as Foreign Exchange, Commercial Paper, Settlement, Liquidity, or another financial structured-information processing area.
A Domain provides the business and semantic scope inherited by later logical profiles, implementation profiles, deployment profiles, and evidence plans.
Definition:
Definition
specific business or semantic area within an Ecosystem
Note
A Domain is not an implementation profile, a deployment environment, a DDS Domain ID, a runtime plane, or a topic namespace.
Relationship to Test
| Domain per Test | Tests per Domain | Relationship |
|---|---|---|
0..1 | 0..* | A Test may be associated with zero or one Domain. A Domain may be associated with zero or more Tests. |
Architectural Meaning
Domain provides the governance and subject-area context within which testing is organized.
Association with a Domain allows a Test to be situated within the Community of Interest, subject area, governance context, or other domain-specific context represented by the DIDO architecture.
The relationship does not, by itself, define the policies, requirements, configurations, or other governed constraints that apply to the Test. Those relationships are established through the corresponding DIDO-TE information elements and requirements.
Model Refinement Considerations
[DTE4] permits a Test to be associated with zero or one Domain.
Whether DIDO-TE should require every Test to be associated with exactly one Domain remains to be determined during normalization of the DIDO-TE Information Model.
The relationship between Domain and the Test Definition also requires review. In particular, DIDO-TE must determine whether:
-
Domain is associated with Test and inherited by the Test Definition;
-
the Test Definition references its governing Domain directly; or
-
both relationships are required for Traceability.
No change to the [DTE4] source-model multiplicity is made on this page.
Source
-
[DTE4] DIDO Reference Data Model, DIDO - RI::DIDO - Conceptual Model::Community::Testing Package.
Notes for Editors
-
The canonical semantics of Domain are maintained in the shared Terms and Definitions corpus and are transcluded above.
-
Do not duplicate or redefine Domain semantics on this page.
-
Preserve the [DTE4] source-model multiplicities until a deliberate DIDO-TE refinement is approved.
-
Record any change to Domain cardinality as a DIDO-TE model refinement rather than as a correction to [DTE4].
-
Review the Domain-to-Test Definition relationship when the Test Definition model is developed in Section 5.13.
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.