Differences
This shows you the differences between two versions of the page.
| dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:twin-005-acquire-twin-state:twin-005b-access-twin-state-values [2026/08/20 16:54] – created nick_dido | dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:twin-005-acquire-twin-state:twin-005b-access-twin-state-values [2026/08/20 16:59] (current) – removed nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== TWIN-005b — Access Twin State Values ====== | ||
| - | [[dido: | ||
| - | |||
| - | ===== Statement ===== | ||
| - | |||
| - | The [[dido: | ||
| - | |||
| - | ===== Source ===== | ||
| - | |||
| - | * [[dido: | ||
| - | * [[dido: | ||
| - | * [[dido: | ||
| - | |||
| - | ===== Rationale ===== | ||
| - | |||
| - | Identification of [[dido: | ||
| - | |||
| - | The requirement remains independent of the mechanism used to provide access. Values may originate from physical, virtual, simulated, recorded, or other eligible [[dido: | ||
| - | |||
| - | Access to a value does not by itself establish the value' | ||
| - | |||
| - | ===== Applies To ===== | ||
| - | |||
| - | * [[dido: | ||
| - | * [[dido: | ||
| - | * [[dido: | ||
| - | * [[dido: | ||
| - | * [[dido: | ||
| - | * [[dido: | ||
| - | |||
| - | ===== Verification ===== | ||
| - | |||
| - | Verification confirms that: | ||
| - | |||
| - | - A value can be obtained for each available element of identified Twin State. | ||
| - | - Each accessed value corresponds to an identified element of Twin State. | ||
| - | - Access does not require knowledge of implementation-specific mechanisms beyond the defined access interface. | ||
| - | - Information outside the identified Twin State is not treated as a Twin State value solely because it is technically accessible. | ||
| - | - The accessed value retains sufficient association with the identified Twin State element for subsequent interpretation. | ||
| - | |||
| - | Verification includes access to at least one Twin State value from a participating Twin Realization. | ||
| - | |||
| - | ===== Traceability ===== | ||
| - | |||
| - | {{backlinks> | ||
| - | |||
| - | ===== ConOps Relationship ===== | ||
| - | |||
| - | This requirement supports retrieval or observation of identified Twin State values for subsequent synchronization, | ||
| - | |||
| - | ===== Delivery Phase ===== | ||
| - | |||
| - | TBD | ||
| - | |||
| - | ===== Requirement Status ===== | ||
| - | |||
| - | Draft | ||
| - | |||
| - | ===== Statement Reference ===== | ||
| - | |||
| - | <code dokuwiki> | ||
| - | {{section> | ||
| - | </ | ||
| - | |||
| - | ---- | ||
| - | |||
| - | <WRAP centeralign> | ||
| - | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| - | </ | ||