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

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:or-001a [2026/07/22 07:48] – nick_didodido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-001:or-001a [2026/07/30 05:30] (current) – [Delivery Phase] nick_dido
Line 5: Line 5:
 ===== Statement ===== ===== Statement =====
  
-[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL perform each Crucible operation invoked by a Developer under the conditions specified by the operational scenario.+[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL perform each Crucible operation allocated to the Developer Role.
  
 ===== Derived From ===== ===== Derived From =====
Line 23: Line 23:
 >> //Compliance Officers//[[dido:02-crusible:99-annexes:annex-b:cr-001|[C1]]] >> //Compliance Officers//[[dido:02-crusible:99-annexes:annex-b:cr-001|[C1]]]
  
-OR-001a preserves the intent that Developers participate in Crucible operation by requiring Crucible to perform each operation invoked by a Developer under the conditions specified by the operational scenario.+OR-001a preserves the intent that Developers participate in Crucible operation by requiring Crucible to perform each operation allocated to the Developer Role.
  
 The separate requirements derived from OR-001 address: The separate requirements derived from OR-001 address:
Line 35: Line 35:
 ===== Rationale ===== ===== Rationale =====
  
-Developers require access to the Crucible operations assigned to them by the operational scenario.+Developers require access to the Crucible operations allocated to the Developer Role.
  
-This requirement ensures that Crucible performs each operation invoked by a Developer under the conditions defined for that operation.+This requirement ensures that Crucible performs each operation allocated to the Developer Role.
  
-Separating Developer operations from the operations associated with other user categories supports independent verification, [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]], and determination of whether Crucible satisfies the operational needs assigned to Developers.+Separating Developer operations from operations allocated to other user categories supports independent verification, [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]], and determination of whether Crucible satisfies the operational needs assigned to Developers.
  
-Without this requirement, Crucible could perform operations for other user categories while failing to perform the operations required by Developers.+Without this requirement, Crucible could perform operations allocated to other user categories while failing to perform the operations allocated to the Developer Role.
  
 ===== Applies To ===== ===== Applies To =====
Line 49: Line 49:
   * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]]   * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]]
   * Developers   * Developers
-  * Operational scenarios that identify Developer operations +  * Developer Role 
-  * Crucible operations identified for Developers +  * Crucible operations allocated to the Developer Role
-  * Developer invocation of Crucible operations+
   * [[dido:99_annexes:annex-b-terms-and-definitions:c:controlled_input|Controlled Inputs]]   * [[dido:99_annexes:annex-b-terms-and-definitions:c:controlled_input|Controlled Inputs]]
   * Operation status   * Operation status
Line 69: Line 68:
 Verification confirms that: Verification confirms that:
  
-  - The operational scenario identifies each Crucible operation that a Developer can invoke +  - The Developer Role is identified 
-  - The operational scenario identifies the conditions under which the Developer can invoke each operation +  - Each Crucible operation allocated to the Developer Role is identified 
-  - The Developer can invoke each identified Crucible operation under the specified conditions +  - Crucible performs each operation allocated to the Developer Role 
-  - Crucible performs each operation invoked by the Developer +  - The performed operation corresponds to the allocated operation 
-  - The performed operation corresponds to the operation invoked by the Developer +  - Crucible produces each status, result, failure indication, exception indication, [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifact]], [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] item, or other output specified for the operation 
-  - Crucible produces each status, result, failure indication, exception indication, Artifact, Evidence item, or other output specified for the operation +  - The verification record preserves [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] between the Developer Role, the allocated operation, and the performed operation
-  - The verification record preserves Traceability among the operational scenario, the Developer invocation, and the performed Crucible operation+
  
 ===== Referenced By ===== ===== Referenced By =====
Line 85: Line 83:
 ===== Delivery Phase ===== ===== Delivery Phase =====
  
-<todo>Determine the Delivery Phase for OR-001a.</todo>+Implemented and Verified.
  
 ===== Implementation Status ===== ===== Implementation Status =====
  
-<todo>Assess whether the current Crucible implementation performs each Crucible operation invoked by a Developer under the conditions specified by the operational scenario.</todo>+<todo>Assess whether the current Crucible implementation performs each Crucible operation allocated to the Developer Role.</todo>
  
 ===== Requirement Status ===== ===== Requirement Status =====
Line 100: Line 98:
 The following unresolved issues affect this requirement: The following unresolved issues affect this requirement:
  
-<todo>Define Developer or reference an authoritative definition. Clarify whether Developer identifies a person, user category, organizational function, Operational Role, or another kind of actor.</todo>+<todo>Define Developer Role or reference an authoritative definition. Identify the essential characteristics of the role and distinguish the role from the DevSecOps Engineer Role, Platform Engineer Role, System Administrator Role, Security Engineer Role, and Compliance Officer Role.</todo>
  
-<todo>Distinguish Developer from DevSecOps Engineer, Platform Engineer, System Administrator, Security Engineer, and Compliance Officer.</todo>+<todo>Identify the controlling source that allocates Crucible operations to the Developer Role.</todo>
  
 ---- ----
Line 116: Line 114:
  
   * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] as the responsible actor   * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] as the responsible actor
-  * Developer as the identified user category +  * Developer Role as the recipient of the operation allocation 
-  * The operational scenario as the source of the operating conditions +  * Allocation of each Crucible operation to the Developer Role 
-  * Invocation of the operation by the Developer +  * Performance of each allocated operation by Crucible
-  * Performance of the invoked operation by Crucible+
  
-The unresolved meaning of Developer should remain recorded in the Issues section until an authoritative definition or classification resolves the issue.+The unresolved meaning of Developer Role should remain recorded in the Issues section until an authoritative definition resolves the issue. 
 + 
 +The source of each operation allocation should remain recorded in the Issues section until a controlling source establishes the allocation.
  
 Material changes should receive review and should update the verification criteria, source records, and Issues section. Material changes should receive review and should update the verification criteria, source records, and Issues section.
  • dido/02-crusible/99-annexes/annex-c-requirements/02-operational-requirements/or-001/or-001a.1784731695.txt.gz
  • Last modified: 2026/07/22 07:48
  • by nick_dido