Differences

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

--- dido:03-dido-te:99-annexes:annex-c-requirements:01-mission-objectives:mo-009:start [2026/08/07 00:36] – removed - external edit (Unknown date) 127.0.0.1
+++ dido:03-dido-te:99-annexes:annex-c-requirements:01-mission-objectives:mo-009:start [2026/08/07 01:15] (current) – nick_dido
@@ Line 1: / Line 1: @@
+====== MO-009 — Reusable Test Resources ======
+[[dido:03-dido-te:99-annexes:annex-c-requirements:01-mission-objectives:start|Go to Mission Objectives]]
+===== Original Requirement =====
+> //[[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]] SHALL provide reusable [[dido:99_annexes:annex-b-terms-and-definitions:t:test_resource|Test Resources]].//
+===== Assessment of Original Requirement =====
+MO-009 was generated as part of the DIDO-TE mission-objective requirements set. The identifier, title, and Original Requirement express the architectural intent that resources developed or acquired for testing support controlled reuse across applicable tests and [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Executions]].
+The Original Requirement identifies DIDO-TE as the responsible actor and uses the normative modal verb **SHALL**. However, the statement does not define a complete or objectively verifiable obligation.
+The following findings apply:
+  * **Provide** does not identify the required DIDO-TE behaviour. It may mean create, acquire, store, catalogue, publish, distribute, or make available.
+  * **Reusable** describes a desired quality without specifying the conditions under which a Test Resource qualifies as reusable.
+  * The statement does not identify the classes of Test Resources within its scope.
+  * The statement does not identify the contexts across which reuse occurs.
+  * The statement does not distinguish repeated use without modification from controlled adaptation.
+  * The statement does not require DIDO-TE to identify the purpose, version, dependencies, compatibility constraints, or applicable conditions of a Test Resource.
+  * The statement does not require DIDO-TE to preserve or control reusable Test Resources.
+  * The statement does not establish how a user determines whether a Test Resource applies to a particular [[dido:99_annexes:annex-b-terms-and-definitions:t:test_definition|Test Definition]], Test Execution, [[dido:99_annexes:annex-b-terms-and-definitions:c:candidate_solution|Candidate Solution]], or [[dido:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]].
+  * The statement does not require DIDO-TE to record the use of a Test Resource.
+  * The statement does not establish the [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] required to demonstrate successful reuse.
+  * An assessor cannot determine from the Original Requirement whether an implementation conforms.
+Although the Original Requirement contains one grammatical obligation, the concept of reusable Test Resources contains several independently verifiable obligations.
+A Test Resource cannot support controlled reuse unless DIDO-TE:
+  * Identifies and describes the Test Resource
+  * Preserves and controls the Test Resource
+  * Identifies the conditions governing its applicability and compatibility
+  * Records its use during applicable Test Executions
+An implementation could satisfy any one of these obligations while failing the others. For example, DIDO-TE could catalogue a Test Resource without controlling its versions, or preserve the resource without identifying the Test Environments in which it applies.
+MO-009 therefore requires decomposition into separate requirements governing Test Resource description, control, applicability, and use [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]].
+The decomposition preserves ''MO-009'' as the stable parent requirement identifier. Each proposed replacement requirement receives a lettered identifier and a separate leaf requirement page.
+===== Proposed Statements =====
+The Original Requirement is decomposed into the following proposed replacement requirements:
+{{indexmenu>dido:03-dido-te:99-annexes:annex-c-requirements:01-mission-objectives:mo-009#1|js navbar nocookie maxjs#1 id#dido_te_mo_009_requirements_nav}}
+===== Requirement Status =====
+<todo>Review and approve the decomposition of MO-009 into separate Test Resource description, control, applicability, and use Traceability requirements.</todo>
+<todo>Determine whether MO-009a through MO-009d collectively supersede MO-009.</todo>
+<todo>If MO-009a through MO-009d are accepted as the complete replacement for MO-009, mark MO-009 as superseded and preserve this page as the parent Traceability record.</todo>
+----
+===== Issues =====
+<todo>Define Test Resource in the shared Terms and Definitions corpus.</todo>
+<todo>Confirm the classes of Test Resources governed by MO-009.</todo>
+<todo>Confirm the contexts across which DIDO-TE supports Test Resource reuse.</todo>
+<todo>Determine whether Test Resource reuse includes controlled adaptation.</todo>
+<todo>Confirm the information required to describe a reusable Test Resource.</todo>
+<todo>Confirm the controls required to preserve Test Resource versions, integrity, provenance, and dependencies.</todo>
+<todo>Confirm the conditions used to determine Test Resource applicability and compatibility.</todo>
+<todo>Confirm the records required to establish Traceability for Test Resource use.</todo>
+<todo>Confirm that MO-009a through MO-009d collectively preserve the complete intent of MO-009.</todo>
+<todo>Confirm the controlling DIDO-TE architectural or mission source from which MO-009 was derived.</todo>
+----
+===== Notes for Editors =====
+MO-009 was generated as part of the DIDO-TE mission-objective requirements set. It does not reproduce an independently approved source statement.
+This page retains the Original Requirement label to preserve the wording assessed during decomposition. The label identifies the original generated wording within this requirements corpus, not wording quoted from an external source.
+This page retains the stable parent requirement identifier ''MO-009''.
+This page is a non-leaf requirement page and retains a trailing '':start'' in its namespace.
+The proposed child requirements are:
+  * ''MO-009a — Test Resource Description''
+  * ''MO-009b — Test Resource Control''
+  * ''MO-009c — Test Resource Applicability''
+  * ''MO-009d — Test Resource Use Traceability''
+The explicit links in Proposed Statements provide temporary links for creating the child pages. After all child pages exist and appear in the dynamic index, remove the explicit list to prevent duplicate entries.
+The Original Requirement should not be marked as superseded until the requirement owner:
+  * Approves all four child requirements
+  * Confirms that the child requirements collectively preserve the complete intent of MO-009
+  * Confirms the Test Resource classes and reuse contexts within scope
+  * Confirms that no additional child requirement is required
+After supersession, this page should remain as the parent Traceability record and continue to preserve the Original Requirement, its assessment, and the supersession decision.
+The non-leaf page namespace is:
+<code>
+dido:03-dido-te:99-annexes:annex-c-requirements:01-mission-objectives:mo-009:start
+</code>
+The child requirement namespaces omit '':start''.
+----
+<WRAP centeralign>
+© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
+</WRAP>