FR-CFG-003 — Reusable Infrastructure Blueprints [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== FR-CFG-003 — Reusable Infrastructure Blueprints ======

[[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-01-configuration-management:start|Go to Crucible Configuration Management Requirements]]

===== Statement =====

[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL apply the same [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_blueprint|Infrastructure Blueprint]] to two or more [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environments]].

===== Derived From =====

This requirement derives from:

  * Crucible System Requirements Specification, Version 1.1 Draft, Functional Requirements, Configuration Management, FR-CFG-003

The Original Requirement states:

> //The system SHALL support reusable infrastructure blueprints.//[[dido:02-crusible:99-annexes:annex-b:cr-001|[C1]]]

FR-CFG-003:

  * Replaces **The system** with the defined system name [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]]
  * Replaces the weak phrase **support reusable** with the observable behavior **apply**
  * Defines reuse as applying the same Infrastructure Blueprint to two or more Infrastructure Environments

===== Rationale =====

An [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_blueprint|Infrastructure Blueprint]] provides a reusable definition of infrastructure structure, relationships, configurable properties, and constraints.

Applying the same Infrastructure Blueprint to multiple [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environments]] reduces duplicated definitions and promotes consistent infrastructure structure.

Environment-specific values, parameters, or controlled overrides allow each Infrastructure Environment to use the reusable Infrastructure Blueprint within its own operational context.

===== Applies To =====

This requirement applies to:

  * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_blueprint|Infrastructure Blueprints]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environments]]

===== Verification =====

Verification confirms that:

  - A tested Infrastructure Blueprint is selected for reuse
  - [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] applies the same tested Infrastructure Blueprint to at least two Infrastructure Environments
  - Each application identifies the Infrastructure Environment to which the Infrastructure Blueprint applies
  - Each Infrastructure Environment receives the infrastructure definition provided by the tested Infrastructure Blueprint
  - Environment-specific values, parameters, or controlled overrides do not prevent identification of the common Infrastructure Blueprint

===== Referenced By =====

The following pages reference this requirement:

{{backlinks>.#dido:02-crusible}}

===== Implementation Status =====

Implemented and Verified

===== Requirement Status =====

<todo>Review and approve FR-CFG-003 as a leaf requirement.</todo>

----
===== Issues =====

<todo>Determine whether reusable Infrastructure Blueprints permit controlled overrides and identify the rules governing those overrides.</todo>

----
===== Notes for Editors =====

This requirement page retains the stable requirement identifier ''FR-CFG-003''.

This page is a leaf requirement page and omits a trailing '':start'' from its namespace.

The Statement preserves the approved source intent by requiring reuse of the same Infrastructure Blueprint across two or more Infrastructure Environments.

Do not add blueprint approval, validation, deployment, acceptance, revision-history, or traceability obligations to the Statement unless the controlling requirement changes through an approved requirements process.

To reference this requirement Statement from another wiki page, insert:

<code dokuwiki>
{{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-01-configuration-management:fr-cfg-003#Statement&noheader&nofooter&noeditbtn}}
</code>

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>