[DTE5] DIDO-TE Requirements Register

Go to Annex B: References

Title: DIDO-TE Requirements Register

Reference Identifier: [DTE5]

Artifact Type: Requirements register

Status: Draft source material

Source Requirement Identifiers: REQ-0001 through REQ-0091

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 serves as source material for the canonical DIDO-TE requirements maintained in Annex C: Requirements.

The identifiers REQ-0001 through REQ-0091 identify requirements within the source register. Annex C preserves these identifiers for source traceability but assigns canonical DIDO-TE identifiers to requirements derived, normalised, reviewed, and approved from the register.

DIDO-TE documentation cites the Requirements Register through its stable reference identifier and the applicable source requirement identifier.

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.

A citation identifies an applicable acceptance criterion, paragraph, table, field, or other source location when that information contributes to the requirement derivation or verification criteria.

The Requirements Register provides source requirements rather than the canonical DIDO-TE requirements.

The derivation process:

1. Preserves the source requirement identifier, title, and original wording
2. Applies Specification Discipline and Authoring (SDA) analysis to identify candidate specification weaknesses
3. Applies Common Specification Weakness Enumeration (CWE) evaluation to confirm and classify defects
4. Separates compound requirements into independently interpretable and independently verifiable obligations
5. Normalises terminology without changing the source meaning
6. Distinguishes normative obligations from acceptance criteria, explanation, rationale, and implementation guidance
7. Records the relationship between each canonical requirement and its source
8. Assigns a canonical DIDO-TE identifier only after review and approval

The source identifiers remain stable source-reference identifiers. They do not become canonical DIDO-TE requirement identifiers.

Each canonical requirement derived from this register records:

1. The reference identifier [DTE5]
2. The source requirement identifier
3. The source requirement title
4. The applicable source obligation
5. The original source wording
6. Any normalised wording
7. Any decomposition relationship
8. Any substantive change and its rationale
9. The disposition of relevant acceptance criteria and supporting material

A decomposed leaf requirement also identifies its non-leaf parent requirement in its Derived From section.

The Source section records external provenance from [DTE5]. The Derived From section records requirement decomposition within Annex C. These sections serve different purposes.

Treat [DTE5] as source material rather than as the canonical DIDO-TE requirements corpus.

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

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

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

Apply SDA analysis before CWE evaluation.

Do not correct or replace the original source statement in the provenance record. Record the original source statement and 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 text, implementation suggestions, examples, or supporting material as independent normative requirements without analysis, traceability, review, and approval.

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

Preserve traceability from each canonical requirement to the precise source requirement and source obligation from which it derives.

Record the register version, date, provenance, and supersession relationship when authoritative metadata becomes available.

Do not replace this reference with a later revision without recording the relationship between the revisions. Preserve this reference when existing requirements, Evidence, reports, or published documents cite it.