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-05-state-and-time-control-requirements:start [2026/08/23 11:30] – created nick_dido
+++ dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-05-state-and-time-control-requirements:start [2026/08/23 12:53] (current) – nick_dido
@@ Line 5: / Line 5: @@
 This section identifies the requirements governing controlled state and time within a [[dido:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]].
-State and Time Control allows a distributed test to begin from defined conditions, reproduce those conditions across repeated executions, control the temporal context in which test activities occur, and associate test behavior and results with the corresponding test time.
+**State and Time Control** allows a distributed test to begin from defined conditions, reproduce those conditions across repeated executions, control the temporal context in which test activities occur, and associate test behavior and results with the corresponding test time.
-The requirements distinguish control of test state from control of test time. State identifies the conditions from which a test begins or to which the Test Environment is restored. Time control establishes and manages the timeline against which test activities occur.
+The requirements distinguish **State Control** from **Time Control**. **State Control** establishes or restores the conditions from which a test begins. **Time Control** establishes and manages the temporal context against which test activities occur.
-The DIDO-TE source material describes virtualized environments that may be repeatedly initialized from a desired starting point with a preconfigured context. It further describes virtual system time that is independent of real time, configurable timeline starting points, execution at rates equal to or different from real time, and resetting a test timeline when repeating a test.
+The DIDO-TE source material describes virtualized environments that may be repeatedly initialized from a desired starting point with a preconfigured context. It further describes **test time** that is independent of **wall-clock time**, configurable timeline starting points, execution at rates equal to or different from real time, and resetting a test timeline when repeating a test.
-Controlled state and controlled time support repeatability and deterministic testing by allowing separate Test Executions to begin from equivalent conditions and progress through equivalent temporal contexts.
+Controlled **state** and controlled **time** support repeatability and deterministic testing by allowing separate [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Executions]] to begin from equivalent conditions and progress through equivalent temporal contexts.
-State and Time Control remains distinct from Test Definition, Test Execution, Record and Playback, Baseline and Comparison, and Validation. The governing Test Definition specifies the required state and time conditions. This requirement family establishes the capabilities required to realize and control those conditions.
+State and Time Control remains distinct from [[dido:99_annexes:annex-b-terms-and-definitions:t:test_definition|Test Definition]], Test Execution, Record and Playback, Baseline and Comparison, and Validation. The governing Test Definition specifies the required state and time conditions. This requirement family establishes the capabilities required to realize and control those conditions.
 A State and Time Control requirement may be represented by an individual leaf requirement or by a non-leaf requirement group containing subordinate independently verifiable obligations.
@@ Line 29: / Line 29: @@
 ===== Contents =====
-  * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-05-state-and-time-control-requirements:stc-001-establish-initial-test-state|STC-001 — Establish Initial Test State]]
-  * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-05-state-and-time-control-requirements:stc-002-restore-test-state|STC-002 — Restore Test State]]
-  * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-05-state-and-time-control-requirements:stc-003-establish-a-test-timeline|STC-003 — Establish a Test Timeline]]
-  * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-05-state-and-time-control-requirements:stc-004-set-the-test-timeline-starting-point|STC-004 — Set the Test Timeline Starting Point]]
-  * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-05-state-and-time-control-requirements:stc-005-control-test-timeline-rate|STC-005 — Control Test Timeline Rate]]
-  * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-05-state-and-time-control-requirements:stc-006-reset-the-test-timeline|STC-006 — Reset the Test Timeline]]
-  * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-05-state-and-time-control-requirements:stc-007-associate-test-events-with-test-time|STC-007 — Associate Test Events with Test Time]]
 {{indexmenu>dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-05-state-and-time-control-requirements#1|js navbar nocookie maxjs#2 id#dido_te_state_time_requirements_nav}}
@@ Line 51: / Line 43: @@
 Repeatable distributed testing requires control over both the conditions from which a test begins and the temporal context in which test activities occur.
-A Test Environment may contain Nodes, Twin Realizations, data, configuration, and other resources whose condition affects test behavior. Establishing and restoring a known starting state allows repeated Test Executions to begin from controlled conditions.
+A [[dido:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]] may contain [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Nodes]], [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_realization|Twin Realizations]], data, [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration|Configuration]], and other resources whose condition affects test behavior. Establishing and restoring a known **starting state** allows repeated Test Executions to begin from controlled conditions.
-Distributed-system behavior may also depend upon time. Time-sensitive transactions, cryptographic operations, scheduling behavior, event ordering, and other activities may produce different results when executed at different points in time or at different rates.
+Distributed-system behavior may also depend upon **time**. Time-sensitive transactions, cryptographic operations, scheduling behavior, event ordering, and other activities may produce different results when executed at different points in time or at different rates.
-The DIDO-TE source material therefore separates test time from wall-clock time. A test timeline may begin at a configured point, may progress at a rate equal to or different from real time, and may be reset when a test is repeated. :contentReference[oaicite:3]{index=3}
+The DIDO-TE source material therefore separates **test time** from **wall-clock time**. A **test timeline** may begin at a configured point, may progress at a rate equal to or different from real time, and may be reset when a test is repeated.
 This separation permits tests to reproduce temporal conditions without requiring the physical execution environment to experience the same real-world timing conditions.
-State and Time Control provides controlled conditions for Test Execution. It does not define the test actions themselves, the recording of those actions, the criteria used for comparison, or the decision used for Validation.
+**State and Time Control** provides controlled conditions for Test Execution. It does not define the test actions themselves, the recording of those actions, the criteria used for comparison, or the decision used for Validation.
 ===== Applies To =====
@@ Line 77: / Line 69: @@
 ===== ConOps Relationship =====
-This requirement family supports preparation and control of the state and temporal context used during Test Execution.
+This requirement family supports preparation and control of the **state** and temporal context used during Test Execution.
-The ConOps describes how a Test Environment is placed into its required starting state, how test time is established and controlled, and how those conditions are used during repeated Test Executions.
+The ConOps describes how a Test Environment is placed into its required **starting state**, how **test time** is established and controlled, and how those conditions are used during repeated Test Executions.
 State and Time Control supports Record and Playback, Baseline and Comparison, and Validation by making the starting conditions and temporal context of repeated Test Executions reproducible.
@@ Line 101: / Line 93: @@
 Apply the requirement identification, decomposition, source and derivation, normative-language, quality, status, and page-structure rules defined by Annex C.
-Do not equate test time with wall-clock time. DIDO-TE source material explicitly permits test time to be independent of real time and to progress at a rate different from real time.
+Do not equate **test time** with **wall-clock time**. DIDO-TE source material explicitly permits test time to be independent of real time and to progress at a rate different from real time.
 Do not combine initial-state establishment, state restoration, timeline establishment, timeline starting point, timeline rate, or timeline reset into a single normative requirement. These capabilities are independently verifiable.