OR-001a — Developer Operations [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== OR-001a — Developer Operations ======

[[dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-001:start|Go to OR-001 — Operation by Identified User Categories]]

===== Statement =====

[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL perform each Crucible operation allocated to the Developer Role.

===== Derived From =====

This requirement derives from:

  * [[dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-001:start|OR-001 — Operation by Identified User Categories]]

The Original Requirement states:

> //The system SHALL support operation by://
>> //Developers//
>> //DevSecOps Engineers//
>> //Platform Engineers//
>> //System Administrators//
>> //Security Engineers//
>> //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 allocated to the Developer Role.

The separate requirements derived from OR-001 address:

  * [[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]]

===== Rationale =====

Developers require access to the Crucible operations allocated to the Developer Role.

This requirement ensures that Crucible performs each operation allocated to the Developer Role.

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 allocated to other user categories while failing to perform the operations allocated to the Developer Role.

===== Applies To =====

This requirement applies to:

  * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]]
  * Developers
  * Developer Role
  * Crucible operations allocated to the Developer Role
  * [[dido:99_annexes:annex-b-terms-and-definitions:c:controlled_input|Controlled Inputs]]
  * Operation status
  * Operation results
  * Operation failures
  * Operation exceptions
  * [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifacts]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:c:connected_environment|Connected Environments]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:d:disconnected_environment|Disconnected Environments]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:a:air-gapped_environment|Air-Gapped Environments]]

===== Verification =====

Verification confirms that:

  - The Developer Role is identified
  - Each Crucible operation allocated to the Developer Role is identified
  - Crucible performs each operation allocated to the Developer Role
  - The performed operation corresponds to the allocated operation
  - 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
  - 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

===== Referenced By =====

The following pages reference this requirement:

{{backlinks>.#dido:02-crusible}}

===== Delivery Phase =====

Implemented and Verified.

===== Implementation Status =====

<todo>Assess whether the current Crucible implementation performs each Crucible operation allocated to the Developer Role.</todo>

===== Requirement Status =====

<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>

----
===== Issues =====

The following unresolved issues affect this requirement:

<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>Identify the controlling source that allocates Crucible operations to the Developer Role.</todo>

----
===== Notes for Editors =====

This requirement page should retain the stable requirement identifier ''OR-001a''.

This page is a leaf requirement page and omits a trailing '':start'' from its namespace.

The parent OR-001 page is a non-leaf page and retains a trailing '':start'' in its namespace.

Changes to the Statement should preserve:

  * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] as the responsible actor
  * Developer Role as the recipient of the operation allocation
  * Allocation of each Crucible operation to the Developer Role
  * Performance of each allocated operation by Crucible

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.

To reference this requirement Statement from another wiki page, insert:

<code dokuwiki>
{{section>dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-001:or-001a#Statement&noheader&nofooter&noeditbtn}}
</code>

Do not rename this page after an external citation unless a redirect or move plan is in place.

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>