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-03-twin-node-requirements:twin-007-simulate-twin-behavior:start [2026/08/21 17:36] – removed - external edit (Unknown date) 127.0.0.1 | dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:twin-007-simulate-twin-behavior:start [2026/08/21 17:36] (current) – ↷ Page moved and renamed from dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:twin-007-simulate-twin-behavior to dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin- nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== TWIN-007 — Simulate Twin Behavior ====== | ||
| + | [[dido: | ||
| + | |||
| + | ===== Statement ===== | ||
| + | |||
| + | The [[dido: | ||
| + | |||
| + | ===== Source ===== | ||
| + | |||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | |||
| + | ===== Rationale ===== | ||
| + | |||
| + | A [[dido: | ||
| + | |||
| + | Simulation allows a Test Execution to exercise represented behavior without requiring every behavior to originate from a corresponding physical or operational realization. | ||
| + | |||
| + | The [[dido: | ||
| + | |||
| + | Simulation does not require the Twin Realization to reproduce behavior outside the scope of the Twin Relationship. | ||
| + | |||
| + | Where correspondence between simulated and other Twin Realizations is assessed, the configured [[dido: | ||
| + | |||
| + | ===== Applies To ===== | ||
| + | |||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | |||
| + | ===== Verification ===== | ||
| + | |||
| + | Verification confirms that: | ||
| + | |||
| + | - A Twin Realization identified for simulation by the governing Test Definition can simulate behavior. | ||
| + | - The simulated behavior corresponds to characteristics represented by the governing Twin Relationship. | ||
| + | - The simulated behavior responds to test conditions defined by the governing Test Definition. | ||
| + | - Characteristics outside the scope of the Twin Relationship are not required to be simulated. | ||
| + | - The simulated behavior remains associated with the Twin Realization that produced it. | ||
| + | - Simulated behavior can be distinguished from behavior obtained from another Twin Realization. | ||
| + | - Where Fidelity Criteria govern the simulated behavior, the simulation produces information sufficient to assess that behavior against those criteria. | ||
| + | |||
| + | Verification includes a Test Execution that exercises at least one represented behavior of a Twin Realization identified for simulation by the Test Definition. | ||
| + | |||
| + | ===== Traceability ===== | ||
| + | |||
| + | {{backlinks> | ||
| + | |||
| + | ===== ConOps Relationship ===== | ||
| + | |||
| + | This requirement supports Test Execution using simulated behavior from a Twin Realization. | ||
| + | |||
| + | Simulation may use established or synchronized state, configured Twin Data Mappings, Data Sources, communication characteristics, | ||
| + | |||
| + | ===== Delivery Phase ===== | ||
| + | |||
| + | TBD | ||
| + | |||
| + | ===== Requirement Status ===== | ||
| + | |||
| + | Draft | ||
| + | |||
| + | ===== Statement Reference ===== | ||
| + | |||
| + | <code dokuwiki> | ||
| + | {{section> | ||
| + | </ | ||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | </ | ||