Operational Requirement

Go to Terms and Definitions

An Operational Requirement specifies a required condition, capability, constraint, or interaction associated with the operation of a system within its intended environment.

An Operational Requirement may address:

• Operational actors and roles
• Operating environments
• Operational conditions
• Mission scenarios
• System availability
• Deployment locations
• Connectivity conditions
• Security classifications
• Administrative boundaries
• Operational interactions
• Concurrent operations
• Distributed operations
• Operational constraints
• Operational Lifecycle conditions

An Operational Requirement establishes the circumstances under which the system operates or the operational outcome required within those circumstances.

An Operational Requirement differs from a functional requirement:

• An Operational Requirement specifies a required operational condition, capability, constraint, or interaction
• A functional requirement specifies behavior the system performs

An Operational Requirement may constrain or provide context for multiple functional requirements.

An Operational Requirement differs from a Mission Objective:

• A Mission Objective states a high-level result that the system achieves in furtherance of its mission
• An Operational Requirement specifies the operational conditions, capabilities, interactions, or constraints associated with achieving that result

Operational Requirements may apply across:

• Connected Environments
• Disconnected Environments
• Air-Gapped Environments
• Classified environments
• Unclassified environments
• Centralized environments
• Distributed environments
• Concurrently managed environments

requirement that specifies a condition, capability, constraint, or interaction associated with operation of a system within its intended environment

Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

An Operational Requirement should identify, as applicable:

• The system or operational subject
• The operational actor or role
• The applicable operating environment
• The required operational condition or capability
• The applicable constraint
• The required interaction
• The operational boundary
• The observable result

An Operational Requirement should remain independent of unnecessary implementation detail.

Verification of an Operational Requirement may require:

• Operational demonstrations
• Scenario-based testing
• Environment inspection
• Role and interaction testing
• Connectivity testing
• Concurrent-operation testing
• Distributed-operation testing

An Operational Requirement does not replace the lower-level functional, performance, security, reliability, logging, or data requirements needed to define the detailed system behavior.

An Operational Requirement specifies that Crucible operates in Connected, Disconnected, and Air-Gapped Environments. Functional and security requirements then define the behaviors and controls required within each operating condition.