The source model associates a Domain with Test.
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:
specific business or semantic area within an Ecosystem
A Domain is not an implementation profile, a deployment environment, a DDS Domain ID, a runtime plane, or a topic namespace.
| 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. |
The Domain relationship places a Test within the governance and semantic context represented by that Domain.
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.
[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:
No change to the [DTE4] source-model multiplicity is made on this page.
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.