OR-001a — Developer Operations

Go to OR-001 — Operation by Identified User Categories

Crucible SHALL perform each Crucible operation invoked by a Developer in accordance with the applicable operational scenario.

This requirement derives from:

• 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[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.

The separate requirements derived from OR-001 address:

• OR-001b — DevSecOps Engineer Operations
• OR-001c — Platform Engineer Operations
• OR-001d — System Administrator Operations
• OR-001e — Security Engineer Operations
• OR-001f — Compliance Officer Operations

Developers require access to the Crucible operations assigned to them by the applicable operational scenario.

This requirement ensures that Crucible performs each applicable operation invoked by a Developer under the conditions defined for that operation.

Separating Developer operations from the operations associated with other user categories supports independent verification, 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.

This requirement applies to:

• Crucible
• Developers
• Operational scenarios applicable to Developers
• Crucible operations identified for Developers
• Developer invocation of Crucible operations
• Controlled Inputs
• Operation status
• Operation results
• Operation failures
• Operation exceptions
• Artifacts
• Evidence
• Provenance
• Traceability
• Connected Environments
• Disconnected Environments
• Air-Gapped Environments

Verification confirms that:

1. The applicable operational scenario identifies each Crucible operation that a Developer can invoke
2. The applicable operational scenario identifies the conditions under which the Developer can invoke each operation
3. The Developer can invoke each identified Crucible operation under the specified conditions
4. Crucible performs each operation invoked by the Developer
5. The performed operation corresponds to the operation invoked by the Developer
6. Crucible produces each status, result, failure indication, exception indication, Artifact, Evidence item, or other output specified for the operation
7. The verification record preserves Traceability among the applicable operational scenario, the Developer invocation, and the performed Crucible operation

The following pages reference this requirement:

Determine the Delivery Phase applicable to OR-001a.

Assess whether the current Crucible implementation performs each Crucible operation invoked by a Developer in accordance with the applicable operational scenario.

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.

The following unresolved issues affect this requirement:

Define Developer or reference an authoritative definition. Clarify whether Developer identifies a person, user category, organizational function, Operational Role, or another kind of actor.

Distinguish Developer from DevSecOps Engineer, Platform Engineer, System Administrator, Security Engineer, and Compliance Officer.

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:

• Crucible as the responsible actor
• Developer as the applicable user category
• The applicable operational scenario as the source of the operational context
• Invocation of the operation by the Developer
• 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.

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:

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

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