Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-01-test-environment-requirements:env-001-define-test-environment:env-001j-define-deployment-constraints [2026/08/18 12:34] – removed - external edit (Unknown date) 127.0.0.1 | dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-01-test-environment-requirements:env-001-define-test-environment:env-001j-define-deployment-constraints [2026/08/18 12:34] (current) – ↷ Links adapted because of a move operation nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== ENV-001j — Define Deployment Constraints ====== | ||
| + | [[dido: | ||
| + | |||
| + | ===== Statement ===== | ||
| + | |||
| + | The [[dido: | ||
| + | |||
| + | ===== Derived From ===== | ||
| + | |||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | |||
| + | ===== Rationale ===== | ||
| + | |||
| + | Defining the applicable deployment [[dido: | ||
| + | |||
| + | The defined Constraints support deployment planning, validation of the deployed Test Environment, | ||
| + | |||
| + | An explicit determination that no deployment Constraint applies distinguishes an intentional condition from missing information. | ||
| + | |||
| + | ===== Applies To ===== | ||
| + | |||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | |||
| + | ===== Verification ===== | ||
| + | |||
| + | Verification confirms that: | ||
| + | |||
| + | * Each Test Environment defines every applicable deployment Constraint. | ||
| + | * Each defined deployment Constraint identifies the element, operation, condition, or Deployment Target it governs. | ||
| + | * The deployed Test Environment satisfies each applicable deployment Constraint. | ||
| + | * A Test Environment without an applicable deployment Constraint records the determination and its basis. | ||
| + | * A missing, undefined, or unsatisfied applicable deployment Constraint constitutes nonconformance with this requirement. | ||
| + | |||
| + | Verification includes: | ||
| + | |||
| + | * Inspection of the controlled information for each Test Environment | ||
| + | * Inspection of the defined deployment Constraints | ||
| + | * Inspection of the deployed Test Environment and its Deployment Target | ||
| + | * Comparison of the observed deployment state with the defined deployment Constraints | ||
| + | * Inspection of recorded determinations that no deployment Constraint applies | ||
| + | * Inspection of the basis recorded for each such determination | ||
| + | * A negative assessment using a Test Environment that violates an applicable deployment Constraint | ||
| + | * Confirmation that the negative assessment produces a nonconformance result | ||
| + | |||
| + | ===== Referenced By ===== | ||
| + | |||
| + | {{backlinks> | ||
| + | |||
| + | ===== Related Architecture Sections ===== | ||
| + | |||
| + | * Add links to the architecture sections governing Test Environment deployment, Deployment Targets, and deployment Constraints. | ||
| + | |||
| + | ===== Delivery Phase ===== | ||
| + | |||
| + | Assign the applicable delivery phase. | ||
| + | |||
| + | ===== Requirement Status ===== | ||
| + | |||
| + | Draft | ||
| + | |||
| + | ===== Statement Reference ===== | ||
| + | |||
| + | Use the following syntax to reference this requirement’s Statement section from another DokuWiki page: | ||
| + | |||
| + | <code dokuwiki> | ||
| + | {{section> | ||
| + | </ | ||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | </ | ||