dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-001:start

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-001:start [2026/07/22 08:35] nick_didodido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-001:start [2026/07/22 08:49] (current) nick_dido
Line 23: Line 23:
   * **Operation** does not identify the Crucible operations associated with the listed categories   * **Operation** does not identify the Crucible operations associated with the listed categories
   * **Operation by** does not identify the relationship between each listed category and each Crucible operation   * **Operation by** does not identify the relationship between each listed category and each Crucible operation
-  * The Original Requirement does not identify which Crucible operations are allocated to each listed category 
-  * The Original Requirement does not identify whether every listed category participates in the same Crucible operations 
-  * The Original Requirement does not identify the interfaces through which each listed category interacts with Crucible 
-  * The Original Requirement does not identify the inputs provided by each listed category 
-  * The Original Requirement does not identify the outputs received or reviewed by each listed category 
-  * The Original Requirement does not identify an acceptance condition for operation by each listed category 
-  * The Original Requirement combines six independently testable categories within one normative statement 
-  * Crucible can satisfy the requirement for one listed category while failing to satisfy it for another 
-  * The Original Requirement does not provide separate requirement identifiers for verification and [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] of each listed category 
  
 The word **operation** is grammatically valid as a mass noun describing the general act of operating Crucible. For requirements purposes, however, the word does not identify an observable Crucible behavior. The word **operation** is grammatically valid as a mass noun describing the general act of operating Crucible. For requirements purposes, however, the word does not identify an observable Crucible behavior.
Line 57: Line 48:
   * Identification of the Crucible operations allocated to each proposed role   * Identification of the Crucible operations allocated to each proposed role
   * Separation of the six independently testable roles   * Separation of the six independently testable roles
-  * Separate requirement identifiers for verification and Traceability 
   * Confirmation that the derived requirements collectively preserve the complete intent of OR-001   * Confirmation that the derived requirements collectively preserve the complete intent of OR-001
  
Line 64: Line 54:
 ===== Proposed Statements ===== ===== Proposed Statements =====
  
-The Original Requirement requires separate treatment of the following independently testable proposed roles: +The Original Requirement is decomposed into the following proposed replacement requirements:
- +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-001:or-001a|OR-001a — Developer Operations]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-001:or-001b|OR-001b — DevSecOps Engineer Operations]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-001:or-001c|OR-001c — Platform Engineer Operations]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-001:or-001d|OR-001d — System Administrator Operations]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-001:or-001e|OR-001e — Security Engineer Operations]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-001:or-001f|OR-001f — Compliance Officer Operations]] +
- +
-Each child requirement: +
- +
-  * Identifies [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] as the responsible actor +
-  * Identifies one proposed Crucible role +
-  * Requires Crucible to perform each Crucible operation allocated to that role +
-  * Supports independent verification of the operations allocated to that role +
-  * Preserves Traceability to OR-001 +
-  * Records unresolved role definitions and operation-allocation sources as issues +
-  * Does not define a role-assignment mechanism +
-  * Does not define a role-based authorization model +
-  * Does not allocate permissions +
-  * Does not establish that every Crucible operation is allocated to every role+
  
 {{indexmenu>dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-001#1|js navbar nocookie maxjs#1 id#crucible_or_001_requirements_nav}} {{indexmenu>dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-001#1|js navbar nocookie maxjs#1 id#crucible_or_001_requirements_nav}}
  • dido/02-crusible/99-annexes/annex-c-requirements/02-operational-requirements/or-001/start.1784734545.txt.gz
  • Last modified: 2026/07/22 08:35
  • by nick_dido