Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
| dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-04-virtual-network-and-communication-requirements:net-002-define-virtual-network-topology:start [2026/08/22 18:39] – removed - external edit (Unknown date) 127.0.0.1 | dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-04-virtual-network-and-communication-requirements:net-002-define-virtual-network-topology:start [2026/08/22 18:39] (current) – ↷ Page moved and renamed from dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-04-virtual-network-and-communication-requirements:net-002-define-virtual-network-topology to dido:03-dido-te:99-annexes:annex-c-requirements:03-fun nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== NET-002 — Define Virtual Network Topology ====== | ||
| + | [[dido: | ||
| + | |||
| + | ===== Statement ===== | ||
| + | |||
| + | The [[dido: | ||
| + | |||
| + | ===== Source ===== | ||
| + | |||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | |||
| + | ===== Rationale ===== | ||
| + | |||
| + | A [[dido: | ||
| + | |||
| + | The [[dido: | ||
| + | |||
| + | Separating establishment of the Virtual Network from definition of its Network Topology permits the same Virtual Network concept to represent different communication structures for different tests. | ||
| + | |||
| + | The governing [[dido: | ||
| + | |||
| + | Network Topology remains distinct from the [[dido: | ||
| + | |||
| + | This requirement does not prescribe a particular routing protocol, network technology, overlay mechanism, middleware implementation, | ||
| + | |||
| + | ===== Applies To ===== | ||
| + | |||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | |||
| + | ===== Verification ===== | ||
| + | |||
| + | Verification confirms that: | ||
| + | |||
| + | - Each Virtual Network specified by the governing Test Definition has a defined Network Topology. | ||
| + | - The Network Topology identifies the communicating entities represented by the topology. | ||
| + | - The Network Topology identifies the communication relationships among those entities. | ||
| + | - Communication relationships not specified by the governing Test Definition are not inferred solely from technical connectivity. | ||
| + | - The defined Network Topology is traceable to the governing Test Definition. | ||
| + | - The Network Topology can be defined independently of the technology used to realize the Virtual Network. | ||
| + | |||
| + | Verification includes a Test Definition specifying multiple communicating entities and communication relationships and confirms that the resulting Network Topology represents those relationships. | ||
| + | |||
| + | ===== Traceability ===== | ||
| + | |||
| + | {{backlinks> | ||
| + | |||
| + | ===== ConOps Relationship ===== | ||
| + | |||
| + | This requirement defines the communication structure of a Virtual Network established under NET-001. | ||
| + | |||
| + | NET-003 governs connection of participating Nodes through the Virtual Network, while NET-004 governs configuration of the Communication Characteristics associated with communication through that network. | ||
| + | |||
| + | ===== Delivery Phase ===== | ||
| + | |||
| + | TBD | ||
| + | |||
| + | ===== Requirement Status ===== | ||
| + | |||
| + | Draft | ||
| + | |||
| + | ===== Statement Reference ===== | ||
| + | |||
| + | <code dokuwiki> | ||
| + | {{section> | ||
| + | </ | ||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | </ | ||