Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| public:99_annexes:annex-b-terms-and-definitions:s:starting_condition [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1 | public:99_annexes:annex-b-terms-and-definitions:s:starting_condition [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Starting Condition ====== | ||
| + | [[public: | ||
| + | |||
| + | ===== Discussion ===== | ||
| + | |||
| + | A Starting Condition is a state, value, event, or circumstance established or observed at the start of an activity. | ||
| + | |||
| + | A Starting Condition can apply to: | ||
| + | |||
| + | * [[public: | ||
| + | * A [[public: | ||
| + | * A [[public: | ||
| + | * A [[public: | ||
| + | * A [[public: | ||
| + | * A [[public: | ||
| + | * A process | ||
| + | * An operation | ||
| + | * Another activity with an identifiable starting event | ||
| + | |||
| + | A Starting Condition can identify: | ||
| + | |||
| + | * The applicable activity | ||
| + | * The starting event | ||
| + | * The starting time | ||
| + | * The applicable [[public: | ||
| + | * The applicable Test Environment Version | ||
| + | * The applicable [[public: | ||
| + | * The applicable [[public: | ||
| + | * The applicable [[public: | ||
| + | * The applicable [[public: | ||
| + | * The applicable [[public: | ||
| + | * The applicable states | ||
| + | * The applicable values | ||
| + | * The applicable [[public: | ||
| + | * The applicable [[public: | ||
| + | * The applicable [[public: | ||
| + | * The applicable dependencies | ||
| + | * The applicable external conditions | ||
| + | * Its [[public: | ||
| + | * Its [[public: | ||
| + | |||
| + | ===== Definition ===== | ||
| + | |||
| + | //state, value, event, or circumstance established or observed at the start of an activity// | ||
| + | |||
| + | ===== Source ===== | ||
| + | |||
| + | Adapted from: | ||
| + | |||
| + | * [[https:// | ||
| + | * [[public: | ||
| + | * [[public: | ||
| + | * [[public: | ||
| + | * DIDO Reference Implementation Conceptual Model | ||
| + | * DIDO-TE draft Requirements Register | ||
| + | |||
| + | OMG TestIF supports Test Run starting times, starting Sequenced Test Objects, Test Argument Values, Test Environments, | ||
| + | |||
| + | OMG TestIF does not define Starting Condition as a separate TestIF model element. This definition introduces the term to identify the state and circumstances that apply when an activity begins. | ||
| + | |||
| + | ===== Note ===== | ||
| + | |||
| + | Use the singular glossary term Starting Condition. Link plural usage to the same controlling page: | ||
| + | |||
| + | <code dokuwiki> | ||
| + | [[dido: | ||
| + | </ | ||
| + | |||
| + | A Starting Condition differs from a condition that must be satisfied before an activity begins: | ||
| + | |||
| + | * The prior condition determines whether the activity can begin | ||
| + | * The Starting Condition identifies the state, value, event, or circumstance that applies when the activity begins | ||
| + | |||
| + | The same information can perform both roles when the activity requires a particular state at its starting event. | ||
| + | |||
| + | A Starting Condition differs from an [[public: | ||
| + | |||
| + | * A Starting Condition identifies the applicable state at the start of an activity | ||
| + | * An Expected Result identifies the anticipated outcome used to evaluate a Test Result | ||
| + | |||
| + | A Starting Condition differs from a [[public: | ||
| + | |||
| + | * A Starting Condition identifies the state or circumstance applicable at the start | ||
| + | * A Timing Condition constrains or characterizes when an event or activity starts, occurs, completes, repeats, or relates temporally to another event or activity | ||
| + | |||
| + | A Starting Condition must identify the applicable subject and activity. A value such as '' | ||
| + | |||
| + | Reproducible Test Execution can require preservation or recreation of applicable Starting Conditions. | ||
| + | |||
| + | The applicable [[public: | ||
| + | |||
| + | * Which Starting Conditions require exact reproduction | ||
| + | * Which Starting Conditions permit variation | ||
| + | * The permitted variation | ||
| + | * The observation or measurement method | ||
| + | * The Evidence required to demonstrate the Starting Conditions | ||
| + | |||
| + | ===== Example ===== | ||
| + | |||
| + | A Test Run evaluates a Node Set beginning from an approved distributed state. | ||
| + | |||
| + | The Starting Conditions identify: | ||
| + | |||
| + | * Test Environment Version '' | ||
| + | * Configuration Version '' | ||
| + | * Node Set '' | ||
| + | * The Version of each Node | ||
| + | * The state of each Node | ||
| + | * The approved Baseline | ||
| + | * The applicable Test Argument Values | ||
| + | * The available Operational Resources | ||
| + | * The starting network Configuration | ||
| + | * The starting event | ||
| + | * The starting time | ||
| + | |||
| + | The Test Run records the observed Starting Conditions before Test Execution proceeds. | ||
| + | |||
| + | A repeated Test Run uses the recorded Starting Conditions to recreate the required starting state and preserve Reproducibility. | ||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | </ | ||