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/21 12:17] – 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 in accordance with the applicable 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 in accordance with the applicable 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 =====
  
-The Original Requirement combines six independently testable user categories within one normative statement.+Developers require access to the Crucible operations allocated to the Developer Role.
  
-OR-001a separates Developer operations from operations associated with the other identified user categories. The separate requirement provides a stable identifier for verification and [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]].+This requirement ensures that Crucible performs each operation allocated to the Developer Role.
  
-The applicable operational scenario identifies:+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.
  
-  * The Crucible operations available to a Developer +Without this requirement, Crucible could perform operations allocated to other user categories while failing to perform the operations allocated to the Developer Role.
-  * The conditions under which a Developer invokes each operation +
-  * The [[dido:99_annexes:annex-b-terms-and-definitions:c:controlled_input|Controlled Inputs]] provided by a Developer +
-  * The status and results presented to a Developer +
-  * The completion conditions applicable to each operation +
-  * The failure and exception conditions applicable to each operation +
-  * The [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifacts]] and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] produced by each operation +
- +
-The [[dido:02-crusible:99-annexes:annex-b:cr-002|Crucible Concept of Operations [C2]]] identifies Build, Capture, and Deploy as high-level Crucible operations. +
- +
-OR-001a does not establish that: +
- +
-  * Every Crucible operation applies to a Developer +
-  * Every Developer invokes the same Crucible operations +
-  * Every operational scenario identifies the same Developer operations +
-  * Developer constitutes an Operational Role +
-  * A particular role-assignment mechanism applies +
-  * A particular authorization or access-control model applies +
-  * A particular interface supports Developer operations +
- +
-Separate operational and functional requirements define the detailed behavior, inputs, outputs, completion conditions, failures, exceptions, Artifacts, and Evidence associated with each Crucible operation.+
  
 ===== Applies To ===== ===== Applies To =====
Line 69: 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 applicable to Developers +  * 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 89: Line 68:
 Verification confirms that: Verification confirms that:
  
-  - The applicable operational scenario identifies each Crucible operation that a Developer can invoke +  - The Developer Role is identified 
-  - The applicable 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 applicable operational scenario, the Developer invocation, and the performed Crucible operation +
- +
-Verification includes: +
- +
-  * Inspection of the applicable operational scenario +
-  * Inspection of the Crucible operations identified for the Developer +
-  * Inspection of the invocation conditions +
-  * Invocation of each identified Crucible operation +
-  * Observation of Crucible performance of each invoked operation +
-  * Comparison of each invoked operation with the corresponding performed operation +
-  * Inspection of operation status and results +
-  * Failure-condition testing +
-  * Exception-condition testing +
-  * Artifact inspection +
-  * Evidence inspection +
-  * Provenance inspection +
-  * Traceability inspection +
- +
-The verification record identifies: +
- +
-  - The applicable operational scenario +
-  - The Developer +
-  - The invoked Crucible operation +
-  - The invocation conditions +
-  - The Controlled Inputs provided by the Developer +
-  - The performed Crucible operation +
-  - The operation completion condition +
-  - Each generated status or result +
-  - Each observed failure or exception +
-  - Each generated [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifact]] +
-  - The generated [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] +
-  - The associated [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]] +
-  - The associated [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] +
- +
-===== Related Architecture Sections ===== +
- +
-No related architecture sections have been identified.+
  
 ===== Referenced By ===== ===== Referenced By =====
Line 141: Line 83:
 ===== Delivery Phase ===== ===== Delivery Phase =====
  
-To Be Determined+Implemented and Verified.
  
 ===== Implementation Status ===== ===== Implementation Status =====
  
-Not Assessed +<todo>Assess whether the current Crucible implementation performs each Crucible operation allocated to the Developer Role.</todo>
- +
-Implementation status requires verification that the current [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] implementation performs each Crucible operation invoked by a Developer in accordance with the applicable operational scenario.+
  
 ===== Requirement Status ===== ===== Requirement Status =====
  
-Draft +<todo>Review and accept OR-001a as a proposed derived requirement created from the evaluation and decomposition of OR-001 in the Crucible System Requirements Specification, Version 1.1 Draft.</todo>
- +
-This requirement derives from OR-001 in the Crucible System Requirements Specification, Version 1.1 Draft.+
  
 +----
 ===== Issues ===== ===== Issues =====
  
 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 174: 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 applicable user category +  * Developer Role as the recipient of the operation allocation 
-  * The applicable operational scenario as the source of the operational context +  * 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 Role should remain recorded in the Issues section until an authoritative definition resolves the issue.
  
-The unresolved meaning of Developer should remain recorded in the Issues section until an authoritative definition or classification 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, related architecture sections, source records, and Issues section.+Material changes should receive review and should update the verification criteria, source records, and Issues section.
  
 To reference this requirement Statement from another wiki page, insert: To reference this requirement Statement from another wiki page, insert:
  • dido/02-crusible/99-annexes/annex-c-requirements/02-operational-requirements/or-001/or-001a.1784661476.txt.gz
  • Last modified: 2026/07/21 12:17
  • by nick_dido