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-010-control-twin-interaction:twin-010c-require-authorization-for-state-changing-interactions [2026/08/21 16:58] – created nick_dido | dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-03-twin-node-requirements:twin-010-control-twin-interaction:twin-010c-require-authorization-for-state-changing-interactions [2026/08/21 17:09] (current) – removed nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== TWIN-010c — Require Authorization for State-Changing Interactions ====== | ||
| - | [[dido: | ||
| - | |||
| - | ===== Statement ===== | ||
| - | |||
| - | The [[dido: | ||
| - | |||
| - | ===== Source ===== | ||
| - | |||
| - | * [[dido: | ||
| - | * [[dido: | ||
| - | * [[dido: | ||
| - | |||
| - | ===== Rationale ===== | ||
| - | |||
| - | Permission to perform an interaction does not establish authority to change the state of another entity. | ||
| - | |||
| - | State-changing interactions can alter the conditions under which Test Execution, synchronization, | ||
| - | |||
| - | This requirement establishes the authorization requirement. TWIN-010d separately prevents execution when the required authorization is absent or denied. | ||
| - | |||
| - | Technical connectivity, | ||
| - | |||
| - | ===== Applies To ===== | ||
| - | |||
| - | * [[dido: | ||
| - | * [[dido: | ||
| - | * [[dido: | ||
| - | * [[dido: | ||
| - | * [[dido: | ||
| - | * [[dido: | ||
| - | * [[dido: | ||
| - | |||
| - | ===== Verification ===== | ||
| - | |||
| - | Verification confirms that: | ||
| - | |||
| - | - Each permitted state-changing interaction requires an authorization decision. | ||
| - | - A permitted interaction that does not change state does not acquire a state-change authorization requirement solely because it participates in a Twin Relationship. | ||
| - | - The authorization requirement identifies the interaction and the entity whose state may change. | ||
| - | - Interaction permission does not substitute for authorization. | ||
| - | - Interaction direction does not substitute for authorization. | ||
| - | - Technical connectivity or interface access does not establish authorization. | ||
| - | |||
| - | Verification includes at least one permitted state-changing interaction and confirms that authorization is required independently of interaction permission. | ||
| - | |||
| - | ===== Traceability ===== | ||
| - | |||
| - | {{backlinks> | ||
| - | |||
| - | ===== ConOps Relationship ===== | ||
| - | |||
| - | This requirement establishes the authorization prerequisite for permitted state-changing interactions after interaction permission and direction have been defined. | ||
| - | |||
| - | ===== Delivery Phase ===== | ||
| - | |||
| - | TBD | ||
| - | |||
| - | ===== Requirement Status ===== | ||
| - | |||
| - | Draft | ||
| - | |||
| - | ===== Statement Reference ===== | ||
| - | |||
| - | <code dokuwiki> | ||
| - | {{section> | ||
| - | </ | ||
| - | |||
| - | ---- | ||
| - | |||
| - | <WRAP centeralign> | ||
| - | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| - | </ | ||