OR-004b — Concurrent Environment Management [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.
====== OR-004b — Concurrent Environment Management ======

[[dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-004:start|Go to OR-004 — Concurrent Environment Deployment and Management]]

===== Statement =====

[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL concurrently manage two or more [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environments]].

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

This requirement derives from:

  * [[dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-004:start|OR-004 — Concurrent Environment Deployment and Management]]
  * Crucible System Requirements Specification, Version 1.1 Draft, Operational Requirements, OR-004

The Original Requirement states:

> //The system SHALL support deployment and management of multiple environments simultaneously.//[[dido:02-crusible:99-annexes:annex-b:cr-001|[C1]]]

OR-004b replaces the weak phrase **support management** with the observable behavior **manage**, defines multiple as two or more, and expresses simultaneous management as concurrent management.

===== Rationale =====

Organizations often operate more than one Infrastructure Environment during overlapping periods.

Concurrent management enables [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] to perform management activity for one Infrastructure Environment without requiring management activity for another Infrastructure Environment to finish first.

This requirement establishes concurrent management capability without defining the specific management operations, maximum concurrency limit, or internal scheduling mechanism.

===== 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_environment|Infrastructure Environments]]
  * Concurrent management operations

===== Verification =====

Verification confirms that:

  - At least two Infrastructure Environments are selected for management
  - [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] performs management activity for the selected Infrastructure Environments during overlapping time periods
  - Management activity for one Infrastructure Environment does not require management activity for every other selected Infrastructure Environment to complete first
  - Each tested Infrastructure Environment produces its own management result
  - Completion or failure of one tested management operation does not prevent management of the other tested Infrastructure Environment unless a documented shared dependency requires that behavior

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

The following pages reference this requirement:

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

===== Delivery Phase =====

Implemented and Verified.

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

<todo>Assess whether the current Crucible implementation concurrently manages two or more Infrastructure Environments.</todo>

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

<todo>Review and approve OR-004b as a leaf requirement derived from OR-004.</todo>

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

<todo>Define the management operations included within concurrent environment management.</todo>

<todo>Define the point at which an environment management operation begins for concurrency verification.</todo>

<todo>Define the point at which an environment management operation ends for concurrency verification.</todo>

<todo>Determine whether a minimum overlap duration is required to demonstrate concurrent management.</todo>

<todo>Determine whether requirements elsewhere define a supported concurrency limit greater than two Infrastructure Environments.</todo>

<todo>Determine whether requirements elsewhere define behavior when Crucible reaches the supported concurrency limit.</todo>

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

This requirement page retains the stable requirement identifier ''OR-004b''.

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

OR-004b governs concurrent management of two or more Infrastructure Environments.

OR-004b does not govern:

  * Concurrent deployment of Infrastructure Environments
  * The management operations available for an Infrastructure Environment
  * The maximum number of concurrently managed Infrastructure Environments
  * Management scheduling or queuing mechanisms
  * Environment identity, Operational Lifecycle State, configuration, resource, operation, or record association
  * Isolation between Infrastructure Environments

Changes to the Statement should preserve:

  * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] as the responsible actor
  * Concurrent management as the required behavior
  * Two or more Infrastructure Environments as the minimum tested quantity

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

<code dokuwiki>
{{section>dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-004:or-004b#Statement&noheader&nofooter&noeditbtn}}
</code>

----

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