MO-005 — Reusable and Version-Controlled Infrastructure Baselines

Go to Mission Objectives

The system SHALL establish infrastructure as a reusable and version-controlled asset.[C1]

The Original Requirement preserves the approved mission objective but does not express independently testable normative statements.

The following Specification Discipline and Authoring findings apply:

• The system does not use the defined system name Crucible
• Establish is a weak verb that does not identify the behavior Crucible performs
• Infrastructure does not identify the managed subject as an Infrastructure Baseline
• Asset does not use the defined concept Artifact
• Reusable does not identify the selection, application, or minimum reuse conditions
• Version-controlled combines identification, revision management, preservation, retrieval, and change control without identifying the required behaviors
• The Original Requirement does not identify how each Infrastructure Baseline is uniquely identified
• The Original Requirement does not identify how revisions of an Infrastructure Baseline are distinguished
• The Original Requirement does not require selection of an approved Infrastructure Baseline for an Infrastructure Deployment
• The Original Requirement does not identify the minimum number of Infrastructure Deployments required to demonstrate reuse
• The Original Requirement does not prohibit modification of approved Infrastructure Baseline content during reuse
• The Original Requirement does not require each Infrastructure Deployment to identify the Infrastructure Baseline revision used
• The Original Requirement combines Artifact management, identification, Version Control, selection, reuse, immutability, and deployment traceability within one compound normative statement
• These obligations can pass or fail independently
• The Original Requirement does not provide independently identifiable statements for verification and traceability

The previously normalized Statement also combined:

• Management of each Infrastructure Baseline as an Artifact
• Unique identification
• Version Control
• Selection for Infrastructure Deployment
• Reuse across multiple Infrastructure Deployments
• Preservation of approved baseline content
• Traceability from each Infrastructure Deployment to the applied Infrastructure Baseline revision

These obligations can pass or fail independently.

The Original Requirement therefore requires decomposition into independently identifiable normative requirements.

The decomposition preserves MO-005 as the stable parent requirement identifier. Each replacement requirement receives a lettered identifier and a separate requirement page.

The Original Requirement is replaced by the following independently identifiable normative requirements: