C.2 Operational Requirements

Go to Crucible Requirements

The Operational Requirements define the actors, deployment environments, operational classifications, concurrency needs, and management scope within which Crucible operates.

These requirements establish the operational conditions that constrain and guide the functional, security, reliability, performance, maintainability, data management, and interoperability requirements.

• OR-001 — Operational Roles
• OR-002 — Deployment Environments
• OR-003 — Classified and Unclassified Environments
• OR-004 — Concurrent Environment Management
• OR-005 — Distributed Environment Management

Each Operational Requirement page:

1. Preserves the source statement
2. Evaluates the source statement using the Specification Discipline and Authoring framework
3. Confirms and classifies defects using the Common Specification Weakness Enumeration
4. Provides a normalized requirement statement
5. Identifies applicable actors, environments, activities, and constraints
6. Defines ordered verification statements
7. Identifies outgoing traceability
8. Uses wiki backlinks for incoming traceability
9. Identifies additional concepts that require entries in the shared Terms and Definitions corpus

The Operational Requirements use or introduce concepts that should link to the shared Terms and Definitions corpus, including:

• Crucible
• Connected Environment
• Disconnected Environment
• Air-Gapped Environment
• Infrastructure Environment
• Infrastructure Deployment
• Deployment Platform
• Operational Environment
• Operational Role
• Distributed Environment
• Classified Environment
• Unclassified Environment
• Concurrent Operation
• Centralized Management

The individual requirement pages should retain the stable identifiers `OR-001` through `OR-005`.

The source statements should preserve the wording from the controlling System Requirements Specification.

Normalized statements should replace weak verbs such as support with direct, testable behavior.

Incoming traceability should use the wiki Backlinks function rather than a manually maintained list.

Individual requirement links should omit a trailing `:start` when the requirement record is a leaf page.

Do not rename requirement pages after external citation unless a redirect or move plan is in place.