Differences

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

--- dido:03-dido-te:99-annexes:annex-b-references:dte-005 [2026/08/07 10:52] – created nick_dido
+++ dido:03-dido-te:99-annexes:annex-b-references:dte-005 [2026/08/08 02:16] (current) – old revision restored (2026/08/08 02:09) nick_dido
@@ Line 5: / Line 5: @@
 ===== Reference =====
-**Title:** DIDO-TE Requirements Register
+DIDO Solutions, Inc. //DIDO-TE Requirements Register//. Draft requirements register.
-**Reference Identifier:** [DTE5]
+===== Bibliographic Information =====
-**Artifact Type:** Requirements register
+^ Attribute ^ Value ^
+| Reference Identifier | [DTE5] |
+| Title | DIDO-TE Requirements Register |
+| Filename | <todo>Record the authoritative filename.</todo> |
+| Artifact Type | Requirements register |
+| Source Requirement Identifiers | ''REQ-0001'' through ''REQ-0091'' |
+| Version | <todo>Record the authoritative version.</todo> |
+| Document Date | <todo>Record the authoritative document date.</todo> |
+| Preparing Organisation | DIDO Solutions, Inc. |
+| File Format | <todo>Record the authoritative file format.</todo> |
+| Status | Draft source material |
-**Status:** Draft source material
+===== Scope =====
-**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).
-===== Description =====
+The register contains source requirements identified as ''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 [[dido:03-dido-te:99-annexes:annex-c-requirements:start|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.
+The source requirement identifiers preserve traceability to the register. They do not constitute canonical DIDO-TE requirement identifiers.
-===== Citation =====
+===== Requirement Content =====
-DIDO-TE documentation cites the Requirements Register through its stable reference identifier and the applicable source requirement identifier.
+The register addresses DIDO-TE subject areas associated with:
+  * Test Environment configuration
+  * Nodes and Deployment Targets
+  * Twin Nodes
+  * Virtual networks and communication
+  * State and time control
+  * Test definition
+  * Test execution
+  * Record and playback
+  * Baselines and comparison
+  * Validation
+  * Monitoring and Evidence
+  * Catalogues and reuse
+  * Governance and Communities of Interest
+  * DIDO-TE operations
+  * Security
+  * Logging and auditing
+  * Reliability
+  * Performance
+  * Maintainability
+  * Data management
+  * Interoperability
+The 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 requirements
+  * Preserve source identifiers and titles
+  * Preserve original source wording
+  * Identify independently interpretable obligations
+  * Identify independently verifiable obligations
+  * Record requirement decomposition
+  * Record terminology normalisation
+  * Establish traceability between source and canonical requirements
+  * Distinguish normative obligations from acceptance criteria and supporting material
+A 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:
+[[dido:03-dido-te:99-annexes:annex-b-references:dte-005|[DTE5]]]
+A citation identifies the applicable source requirement identifier and title.
 For example:
@@ Line 41: / Line 99: @@
 </code>
-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.
+When an acceptance criterion supports a requirement or its verification criteria, the citation identifies the applicable acceptance criterion.
-===== Use of Source Requirements =====
+===== Source-Requirement Treatment =====
-The Requirements Register provides source requirements rather than the canonical DIDO-TE requirements.
+Annex C preserves the original identifier, title, and wording of each source requirement cited from `[DTE5]`.
-The derivation process:
+The requirements process:
-  - Preserves the source requirement identifier, title, and original wording
+  - Applies Specification Discipline and Authoring (SDA) analysis to identify candidate weaknesses
-  - Applies Specification Discipline and Authoring (SDA) analysis to identify candidate specification weaknesses
   - Applies Common Specification Weakness Enumeration (CWE) evaluation to confirm and classify defects
-  - Separates compound requirements into independently interpretable and independently verifiable obligations
+  - Separates compound source statements into independently interpretable and independently verifiable obligations
-  - Normalises terminology without changing the source meaning
+  - Normalises spelling, capitalisation, spacing, and terminology without changing the source meaning
-  - Distinguishes normative obligations from acceptance criteria, explanation, rationale, and implementation guidance
+  - Distinguishes normative obligations from acceptance criteria, rationale, explanation, examples, and implementation guidance
-  - Records the relationship between each canonical requirement and its source
+  - Records the lineage between each canonical requirement and its source obligation
-  - Assigns a canonical DIDO-TE identifier only after review and approval
+  - Assigns a canonical DIDO-TE identifier following review and approval
-The source identifiers remain stable source-reference identifiers. They do not become canonical DIDO-TE requirement identifiers.
+The canonical requirement retains traceability to its source requirement even when analysis produces several independently verifiable leaf requirements.
-===== Source Traceability =====
+===== Identifier Treatment =====
-Each canonical requirement derived from this register records:
+The identifiers ''REQ-0001'' through ''REQ-0091'' identify requirements within `[DTE5]`.
-  - The reference identifier [DTE5]
+These identifiers remain source-reference identifiers.
-  - The source requirement identifier
-  - The source requirement title
-  - The applicable source obligation
-  - The original source wording
-  - Any normalised wording
-  - Any decomposition relationship
-  - Any substantive change and its rationale
-  - 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.
+Annex C assigns canonical identifiers according to the applicable requirement class, including:
-The ''Source'' section records external provenance from [DTE5]. The ''Derived From'' section records requirement decomposition within Annex C. These sections serve different purposes.
+  * ''MO'' for Mission Objectives
+  * ''OR'' for Operational Requirements
+  * ''FR'' for Functional Requirements
+  * ''SEC'' for Security Requirements
+  * ''LOG'' for Logging and Auditing Requirements
+  * ''REL'' for Reliability Requirements
+  * ''PER'' for Performance Requirements
+  * ''MNT'' for Maintainability Requirements
+  * ''DAT'' for Data Management Requirements
+  * ''INT'' for Interoperability Requirements
+Annex 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:
+  * [[dido:03-dido-te:99-annexes:annex-b-references:dte-001|[DTE1] U.S. Patent Application US20220237111A1]]
+  * [[dido:03-dido-te:99-annexes:annex-b-references:dte-002|[DTE2] Non-Traditional BAA Submission]]
+  * [[dido:03-dido-te:99-annexes:annex-b-references:dte-003|[DTE3] Draft BAA White Paper]]
+  * [[dido:03-dido-te:99-annexes:annex-b-references:dte-004|[DTE4] DIDO Reference Data Model]]
+[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. [[dido:03-dido-te:99-annexes:annex-c-requirements:start|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 =====
-Treat [DTE5] as source material rather than as the canonical DIDO-TE requirements corpus.
+Preserve `[DTE5]` and this page namespace as stable citation identifiers.
-Preserve the identifiers ''REQ-0001'' through ''REQ-0091'' in all derivation and traceability records.
+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.
-Do not derive requirements solely from a source title, category heading, summary, or inferred architectural intent.
+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 correct or replace the original source statement in the provenance record. Record the original source statement and the normalised requirement separately.
+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 text, implementation suggestions, examples, or supporting material as independent normative requirements without analysis, traceability, review, and approval.
+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.
-Preserve traceability from each canonical requirement to the precise source requirement and source obligation from which it derives.
+Record the revision, provenance, and supersession relationship before replacing `[DTE5]` with another requirements register.
-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.
+Preserve `[DTE5]` when existing requirements, Evidence, reports, or externally published documents cite it.
 ----