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-003-establish-controlled-starting-state:env-003g-establish-required-communication-relationships [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-003-establish-controlled-starting-state:env-003g-establish-required-communication-relationships [2026/08/18 12:34] (current) – ↷ Links adapted because of a move operation nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== ENV-003g — Establish Required Communication Relationships ====== | ||
| + | [[dido: | ||
| + | |||
| + | ===== Statement ===== | ||
| + | |||
| + | Before each [[dido: | ||
| + | |||
| + | ===== Derived From ===== | ||
| + | |||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | |||
| + | ===== Rationale ===== | ||
| + | |||
| + | Establishing the required communication relationships creates the controlled paths through which participating [[dido: | ||
| + | |||
| + | Each communication relationship must correspond to its specified participants, | ||
| + | |||
| + | Controlling communication relationships prevents absent, unintended, unauthorised, | ||
| + | |||
| + | ===== Applies To ===== | ||
| + | |||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | |||
| + | ===== Verification ===== | ||
| + | |||
| + | Verification confirms that: | ||
| + | |||
| + | * The controlled descriptive information identifies each communication relationship required for the Test Execution. | ||
| + | * The controlled descriptive information identifies the participants, | ||
| + | * The DIDO-TE establishes each required communication relationship before Test Execution. | ||
| + | * Each established communication relationship connects the specified participants. | ||
| + | * Each established communication relationship conforms to its specified direction, interface, protocol, address, topic, channel, security controls, and quality characteristics. | ||
| + | * Each required communication relationship supports the exchange specified by the applicable Test Definition. | ||
| + | * The Test Environment excludes unintended, unauthorised, | ||
| + | * The DIDO-TE removes or isolates residual communication relationships from prior Test Executions. | ||
| + | * The DIDO-TE records the identity, participants, | ||
| + | * The DIDO-TE maintains [[dido: | ||
| + | * An absent, unintended, unauthorised, | ||
| + | |||
| + | Verification includes: | ||
| + | |||
| + | * Inspection of the controlled descriptive information identifying each required communication relationship | ||
| + | * Inspection of the specified participants, | ||
| + | * Observation of communication-relationship establishment | ||
| + | * Confirmation of communication between the specified participants | ||
| + | * Comparison of each established communication relationship with its controlled descriptive information | ||
| + | * Testing for unintended, unauthorised, | ||
| + | * Inspection of communication-relationship identity, Configuration, | ||
| + | * Inspection of Traceability records connecting each communication relationship to its controlled descriptive information, | ||
| + | * A negative assessment using an absent, unintended, unauthorised, | ||
| + | * Confirmation that the negative assessment produces a nonconformance result | ||
| + | |||
| + | ===== Referenced By ===== | ||
| + | |||
| + | {{backlinks> | ||
| + | |||
| + | ===== Related Architecture Sections ===== | ||
| + | |||
| + | * Add links to the architecture sections governing communication relationships, | ||
| + | |||
| + | ===== 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. | ||
| + | </ | ||