OR-001a — Developer Operations

Go to OR-001 — Operation by Identified User Categories

Crucible SHALL execute each Crucible operation assigned to a Developer by the applicable operational scenario in response to the Developer interaction specified for that operation.

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 execute each operation assigned to a Developer by 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

The Original Requirement identifies Developers as a category of users that participates in Crucible operation but does not identify:

• The Crucible operations assigned to a Developer
• The operational scenarios in which a Developer participates
• The Developer interaction that causes Crucible to execute an assigned operation
• The inputs supplied by a Developer
• The outputs presented to a Developer
• The completion condition for an operation assigned to a Developer
• The Evidence required to demonstrate successful operation
• The distinction between Developer participation and participation by another identified user category

The phrase support operation by Developers does not identify an observable Crucible behavior.

OR-001a:

• Identifies Crucible as the responsible actor
• Identifies the Developer as the applicable user category
• Requires the applicable operational scenario to assign the operation to a Developer
• Requires the applicable operational scenario to specify the Developer interaction
• Requires Crucible to execute the assigned operation in response to the specified Developer interaction
• Separates Developer operation from operation by the other identified user categories

OR-001a does not establish:

• That every Crucible operation applies to a Developer
• That every Developer performs the same operations
• That every operational scenario assigns the same operations to a Developer
• A role-assignment mechanism
• A role-based authorization model
• A particular access-control model
• A particular user interface
• A particular interaction mechanism
• Permissions not established by another controlling requirement

Separating Developer operation from operation by the other identified user categories provides an independently testable and traceable requirement.

The applicable operational scenario establishes the context needed to determine:

• Which Crucible operation applies to a Developer
• Which Developer interaction applies to the operation
• Which inputs the Developer supplies
• Which outputs the Developer receives or reviews
• Which completion condition applies
• Which failures and exceptions apply
• Which Evidence demonstrates execution of the operation

The Crucible Concept of Operations [C2] identifies Build, Capture, and Deploy as high-level Crucible operations.

The Concept of Operations also addresses:

• Phase 1 command-line operation
• CI/CD pipeline integration
• Image-layer baseline composition
• Infrastructure baseline composition
• Machine Image construction
• Dependency capture
• Compliance-finding capture
• Infrastructure deployment
• Connected-to-disconnected transfer
• Offline package-repository population
• Compliance Evidence generation
• Phase 2 web management
• Strategic native execution

The applicable operational scenario determines which of these operations and interactions apply to a Developer.

This requirement does not allocate every identified Crucible operation to a Developer.

This requirement does not define the detailed behavior of Build, Capture, Deploy, or another Crucible operation. Separate functional and operational requirements define those behaviors.

This requirement applies to:

• Crucible
• Developers
• Applicable operational scenarios
• Crucible operations assigned to Developers
• Developer interactions specified by applicable operational scenarios
• Developer inputs
• Operation status
• Operation results
• Operation failures
• Operation exceptions
• Build operations assigned to Developers
• Capture operations assigned to Developers
• Deploy operations assigned to Developers
• Phase 1 command-line operation
• CI/CD pipeline integration
• Phase 2 web management
• Strategic native execution
• Connected Environments
• Disconnected Environments
• Air-Gapped Environments
• Artifacts
• Evidence
• Provenance
• Traceability

Verification confirms that:

# The applicable operational scenario identifies the Developer
# The applicable operational scenario identifies each Crucible operation assigned to the Developer
# The applicable operational scenario identifies the Developer interaction associated with each assigned operation
# Crucible receives the specified Developer interaction
# Crucible executes the operation assigned to the Developer
# The executed operation corresponds to the operation identified by the applicable operational scenario
# Crucible produces the status, result, failure, exception, Artifact, Evidence, or other output specified for the operation
# The verification record preserves Traceability between the applicable operational scenario, Developer interaction, and executed operation

Verification includes:

• Applicable operational scenario inspection
• Developer identification inspection
• Assigned-operation inspection
• Developer-interaction inspection
• Developer-input inspection
• Execution of each operation assigned to the Developer
• Operation-status inspection
• Operation-result inspection
• 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 assigned Crucible operation
# The specified Developer interaction
# Each Developer input
# The executed Crucible operation
# The operation start condition
# 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]]

This requirement is realized by:

• Requirements that define Build operations assigned to Developers
• Requirements that define Capture operations assigned to Developers
• Requirements that define Deploy operations assigned to Developers
• Requirements that define Phase 1 command-line interactions
• Requirements that define CI/CD pipeline interactions
• Requirements that define Developer inputs
• Requirements that define operation status and results
• Requirements that define operation failures and exceptions
• Requirements that define generated Artifacts and Evidence

• 4. Operational Concepts
• 5. Descriptions, Composition, and Baselines
• 7. Infrastructure and Deployment
• 10. Reproducibility, Provenance, and Traceability

The following pages reference this requirement:

Phase 1 and subsequent phases

Not Assessed

Implementation status requires verification that the current Crucible implementation executes each Crucible operation assigned to a Developer by the applicable operational scenario in response to the specified Developer interaction.

Draft

This requirement derives from OR-001 in the Crucible System Requirements Specification, Version 1.1 Draft.

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.

Changes to the Statement should preserve:

• Crucible as the responsible actor
• The Developer as the applicable user category
• Assignment of the operation by the applicable operational scenario
• Identification of the Developer interaction by the applicable operational scenario
• Execution of the assigned operation by Crucible

The requirement owner should confirm:

• Which Crucible operations apply to Developers
• Which operational scenarios assign those operations
• Which Developer interaction applies to each operation
• Which Developer inputs apply
• Which outputs apply
• Which existing requirements realize each assigned operation
• Which uncovered interactions require additional atomic requirements

Material changes should receive review and should update the related verification criteria, requirements realization, related architecture sections, and source records.

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.