[DTE5] DIDO-TE Requirements Register

Go to Annex B: References

Reference

DIDO Solutions, Inc. DIDO-TE Requirements Register. Draft requirements register.

Bibliographic Information

Attribute	Value
Reference Identifier	[DTE5]
Title	DIDO-TE Requirements Register
Filename
Artifact Type	Requirements register
Source Requirement Identifiers	REQ-0001 through REQ-0091
Version
Document Date
Preparing Organisation	DIDO Solutions, Inc.
File Format
Status	Draft source material

Scope

The DIDO-TE Requirements Register records source requirements, acceptance criteria, explanatory information, and supporting material for the Distributed Immutable Data Object Test Environment (DIDO-TE).

The register contains source requirements identified as REQ-0001 through REQ-0091.

The register serves as source material for the canonical DIDO-TE requirements maintained in Annex C: Requirements.

The source requirement identifiers preserve traceability to the register. They do not constitute canonical DIDO-TE requirement identifiers.

Requirement Content

The register addresses DIDO-TE subject areas associated with:

Test Environment configurationNodes and Deployment TargetsTwin NodesVirtual networks and communicationState and time controlTest definitionTest executionRecord and playbackBaselines and comparisonValidationMonitoring and EvidenceCatalogues and reuseGovernance and Communities of InterestDIDO-TE operationsSecurityLogging and auditingReliabilityPerformanceMaintainabilityData managementInteroperabilityThe register may contain compound statements, acceptance criteria, explanatory material, implementation suggestions, and other supporting information. Annex C analyses and dispositions this material before establishing canonical requirements.

Relevance to DIDO-TE

This reference provides source-requirement provenance for the DIDO-TE requirements corpus.

Annex C uses `[DTE5]` to:

Identify source requirementsPreserve source identifiers and titlesPreserve original source wordingIdentify independently interpretable obligationsIdentify independently verifiable obligationsRecord requirement decompositionRecord terminology normalisationEstablish traceability between source and canonical requirementsDistinguish normative obligations from acceptance criteria and supporting materialA source requirement does not become a canonical DIDO-TE requirement until the requirements process analyses, normalises, traces, reviews, and approves it.

Citation Use

DIDO-TE pages cite this reference using:

[DTE5]

A citation identifies the applicable source requirement identifier and title.

For example:

[[dido:03-dido-te:99-annexes:annex-b-references:dte-005|[DTE5]]], ''REQ-0010 — Domain-scoped environments''.

When a canonical requirement derives from one obligation within a compound source requirement, the citation identifies the applicable source obligation.

For example:

[[dido:03-dido-te:99-annexes:annex-b-references:dte-005|[DTE5]]], ''REQ-0010 — Domain-scoped environments'', source obligation concerning creation of a Domain-owned Test Environment.

When an acceptance criterion supports a requirement or its verification criteria, the citation identifies the applicable acceptance criterion.

Source-Requirement Treatment

Annex C preserves the original identifier, title, and wording of each source requirement cited from `[DTE5]`.

The requirements process:

Applies Specification Discipline and Authoring (SDA) analysis to identify candidate weaknessesApplies Common Specification Weakness Enumeration (CWE) evaluation to confirm and classify defectsSeparates compound source statements into independently interpretable and independently verifiable obligationsNormalises spelling, capitalisation, spacing, and terminology without changing the source meaningDistinguishes normative obligations from acceptance criteria, rationale, explanation, examples, and implementation guidanceRecords the lineage between each canonical requirement and its source obligationAssigns a canonical DIDO-TE identifier following review and approvalThe canonical requirement retains traceability to its source requirement even when analysis produces several independently verifiable leaf requirements.

Identifier Treatment

The identifiers REQ-0001 through REQ-0091 identify requirements within `[DTE5]`.

These identifiers remain source-reference identifiers.

Annex C assigns canonical identifiers according to the applicable requirement class, including:

MO for Mission ObjectivesOR for Operational RequirementsFR for Functional RequirementsSEC for Security RequirementsLOG for Logging and Auditing RequirementsREL for Reliability RequirementsPER for Performance RequirementsMNT for Maintainability RequirementsDAT for Data Management RequirementsINT for Interoperability RequirementsAnnex C does not replace the source identifier. Its traceability record preserves both identifiers.

Relationship to Other References

[DTE5] provides source requirements associated with concepts, proposals, and model content recorded in other DIDO-TE references.

See:

[DTE1] records patented subject matter. [DTE2] and [DTE3] describe proposed applications of DIDO-TE. [DTE4] supplies a historical Conceptual Model. [DTE5] records the source requirements considered during development of the canonical DIDO-TE requirements corpus.

Cite the reference that directly supports the applicable statement or requirement derivation.

Status

[DTE5] records draft source material.

The register does not, by itself, establish the current normative DIDO-TE requirements corpus. Annex C: Requirements contains the canonical requirements following analysis, normalisation, traceability, review, and approval.

The source identifiers, original wording, version, date, and provenance remain part of the source record.

Notes for Editors

Preserve `[DTE5]` and this page namespace as stable citation identifiers.

Preserve the authoritative source file as the canonical source artefact.

Record the authoritative filename, version, date, file format, and publication status when that metadata becomes available.

Preserve the identifiers REQ-0001 through REQ-0091 in derivation and traceability records.

Do not assign a source REQ-#### identifier to a canonical DIDO-TE requirement.

Identify the precise source requirement, source obligation, and applicable acceptance criterion when deriving a canonical requirement from `[DTE5]`.

Apply SDA analysis before CWE evaluation.

Do not derive requirements solely from a source title, category heading, summary, or inferred architectural intent.

Preserve the original source statement in the provenance record. Record the normalised requirement separately.

Do not classify a change to scope, actor, behaviour, value, constraint, cardinality, relationship, or meaning as an editorial correction.

Do not treat acceptance criteria, explanatory material, examples, implementation suggestions, or supporting information as independent normative requirements without analysis, traceability, review, and approval.

Separate compound source requirements into independently interpretable and independently verifiable obligations.

Record the revision, provenance, and supersession relationship before replacing `[DTE5]` with another requirements register.

Preserve `[DTE5]` when existing requirements, Evidence, reports, or externally published documents cite it.

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.