dido:03-dido-te:06-information-model:06-01-overview:start

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
dido:03-dido-te:06-information-model:06-01-overview:start [2026/08/23 17:14] – removed - external edit (Unknown date) 127.0.0.1dido:03-dido-te:06-information-model:06-01-overview:start [2026/08/23 17:17] (current) – nick_dido
Line 1: Line 1:
 +====== 6.1 Information Model Overview ======
  
 +[[dido:03-dido-te:06-information-model:start|Go to 6. DIDO-TE Information Model]]
 +
 +The DIDO-TE Information Model provides the structural view of the information used to define, configure, execute, observe, and evaluate tests within the [[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]].
 +
 +The model is derived initially from the Testing Package of [[dido:03-dido-te:99-annexes:annex-b-references:dte-004|[DTE4] DIDO Reference Data Model]] and is refined where necessary to support the DIDO-TE architecture and requirements.
 +
 +===== Model Scope =====
 +
 +The Information Model includes the information required to describe:
 +
 +  * the organization of a test;
 +  * the [[dido:99_annexes:annex-b-terms-and-definitions:t:test_set|Test Sets]], [[dido:99_annexes:annex-b-terms-and-definitions:t:test_case|Test Cases]], and [[dido:99_annexes:annex-b-terms-and-definitions:t:test_step|Test Steps]] that compose the test structure;
 +  * the [[dido:99_annexes:annex-b-terms-and-definitions:t:test_executable|Test Executables]] and [[dido:99_annexes:annex-b-terms-and-definitions:t:test_argument|Test Arguments]] used to perform test activities;
 +  * the [[dido:99_annexes:annex-b-terms-and-definitions:e:expected_result|Expected Results]] used to describe expected test behavior;
 +  * the [[dido:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]] in which testing occurs;
 +  * the [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Nodes]], [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_node|Twin Nodes]], and other [[dido:99_annexes:annex-b-terms-and-definitions:r:resource|Resources]] participating in testing;
 +  * the [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration|Configuration]], communication, state, and time conditions governing testing;
 +  * the [[dido:99_annexes:annex-b-terms-and-definitions:t:test_result|Test Results]] produced by testing;
 +  * the [[dido:99_annexes:annex-b-terms-and-definitions:t:test_run|Test Runs]] associated with those Test Results; and
 +  * the information required to support [[dido:99_annexes:annex-b-terms-and-definitions:v:validation|Validation]], [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]], and [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]].
 +
 +===== Relationship to Common Information Types =====
 +
 +The DIDO-TE Information Model uses reusable information types defined in [[dido:03-dido-te:05-common-information-types:start|Section 5, Common Information Types]].
 +
 +Common Information Types define reusable datatypes, structured types, enumerations, identifiers, names, parameter structures, and other value representations independently of the Information Model classes that use them.
 +
 +Information Model elements reference those common types rather than redefining their structure or semantics.
 +
 +===== Existing Testing Structure =====
 +
 +The Testing Package of [DTE4] provides the initial structural foundation for the DIDO-TE Information Model.
 +
 +At a high level, [DTE4] organizes testing using the following hierarchy:
 +
 +<code>
 +Test
 +  |
 +  +-- Test Plan
 +        |
 +        +-- Test Set
 +              |
 +              +-- Test Set
 +              |
 +              +-- Test Case
 +                    |
 +                    +-- Test Executable
 +                    |
 +                    +-- Test Step
 +                          |
 +                          +-- Test Step
 +                          +-- Test Executable
 +                          +-- Expected Results
 +                          +-- Test Result
 +
 +                    +-- Expected Results
 +                    +-- Test Result
 +
 +Test Result
 +  |
 +  +-- Test Run
 +</code>
 +
 +[DTE4] also associates a Test Set with the environment in which that Test Set executes.
 +
 +The hierarchy shown above represents the source-model structure. DIDO-TE may refine individual relationships as the model elements are reviewed in the following sections.
 +
 +===== Model Element Review =====
 +
 +Each principal model element is reviewed independently before the integrated DIDO-TE Information Model is established.
 +
 +The review proceeds from [DTE4] rather than beginning with a newly imposed structure.
 +
 +For each model element, the review identifies:
 +
 +  * the element represented by [DTE4];
 +  * the attributes represented by [DTE4];
 +  * the Common Information Types used by those attributes;
 +  * associations with other model elements;
 +  * association multiplicities;
 +  * semantic or structural issues discovered in the source model;
 +  * DIDO-TE architectural interpretation;
 +  * relationships to existing DIDO-TE glossary concepts;
 +  * relationships to DIDO-TE requirements; and
 +  * any deliberate DIDO-TE extension or refinement.
 +
 +This approach allows the DIDO-TE Information Model to preserve useful source-model structures while distinguishing them from additions made specifically for DIDO-TE.
 +
 +===== Source Model and DIDO-TE Extensions =====
 +
 +The Information Model distinguishes between **source-model content** and **DIDO-TE extensions**.
 +
 +**Source-model content** consists of information elements, attributes, associations, multiplicities, and types represented by [DTE4].
 +
 +**DIDO-TE extensions** consist of information or relationships required by the DIDO-TE architecture that are not represented explicitly in [DTE4].
 +
 +Examples of concepts introduced or substantially expanded by DIDO-TE include:
 +
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_definition|Test Definition]];
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]] configuration and controlled environmental conditions;
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_node|Twin Node]] participation;
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:v:virtual_network|Virtual Network]] and communication conditions;
 +  * controlled test state;
 +  * controlled test time;
 +  * Validation Criteria;
 +  * Evidence requirements; and
 +  * governed Traceability relationships.
 +
 +The inclusion of a DIDO-TE extension does not imply that the corresponding concept existed in [DTE4].
 +
 +===== Test Definition as an Integrating Concept =====
 +
 +The [[dido:99_annexes:annex-b-terms-and-definitions:t:test_definition|Test Definition]] is an important integrating concept within the DIDO-TE Information Model.
 +
 +[DTE4] does not contain a model element named Test Definition. Instead, information relevant to defining a test is distributed across multiple testing elements, supporting types, and their relationships.
 +
 +DIDO-TE therefore derives the Test Definition structure from:
 +
 +  * the testing structure represented by [DTE4];
 +  * the Common Information Types used by the testing elements;
 +  * the conditions required by the DIDO-TE functional requirements;
 +  * the information required by [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]];
 +  * the information required to interpret Test Results; and
 +  * the criteria and Evidence required for Validation and Traceability.
 +
 +The Test Definition is therefore developed after the constituent model elements have been reviewed.
 +
 +This ordering avoids imposing a Test Definition structure that conflicts with or unnecessarily duplicates the existing testing model.
 +
 +===== Information Model Relationships =====
 +
 +The Information Model supports a general architectural flow in which governed test information is defined before execution and is preserved through evaluation:
 +
 +<code>
 +Test Definition
 +      |
 +      v
 +Test Structure and Test Conditions
 +      |
 +      v
 +Test Execution
 +      |
 +      v
 +Test Results
 +      |
 +      v
 +Comparison and Validation
 +      |
 +      v
 +Evidence and Traceability
 +</code>
 +
 +This flow represents an architectural relationship among information elements. It does not prescribe a sequential software implementation, workflow engine, storage mechanism, or execution platform.
 +
 +===== Relationship to Requirements =====
 +
 +The Information Model provides architectural structure for concepts referenced by the DIDO-TE [[dido:99_annexes:annex-b-terms-and-definitions:r:requirement|requirements]].
 +
 +The requirements remain the normative source of DIDO-TE obligations.
 +
 +For example:
 +
 +  * Test Environment requirements identify information that must be represented or referenced by the Test Definition and environment model;
 +  * Twin Node requirements identify information concerning Twin Identities, Twin Realizations, and Twin Relationships;
 +  * Virtual Network and Communication requirements identify governed communication conditions;
 +  * State and Time Control requirements identify governed initial state and temporal conditions; and
 +  * [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-06-test-definition-requirements:start|C.3.6 Test Definition Requirements]] collects and formalizes the information that the governing Test Definition is required to identify, specify, or reference.
 +
 +As the model is refined, individual model elements should maintain explicit Traceability to the requirements that establish the need for those elements or relationships.
 +
 +===== Contents =====
 +
 +The following sections review the principal information-model elements:
 +
 +  * [[dido:03-dido-te:06-information-model:06-02-test:start|6.2 Test]]
 +  * [[dido:03-dido-te:06-information-model:06-03-test-plan|6.3 Test Plan]]
 +  * [[dido:03-dido-te:06-information-model:06-04-test-set|6.4 Test Set]]
 +  * [[dido:03-dido-te:06-information-model:06-05-test-case|6.5 Test Case]]
 +  * [[dido:03-dido-te:06-information-model:06-06-test-step|6.6 Test Step]]
 +  * [[dido:03-dido-te:06-information-model:06-07-test-executable|6.7 Test Executable]]
 +  * [[dido:03-dido-te:06-information-model:06-08-expected-results|6.8 Expected Results]]
 +  * [[dido:03-dido-te:06-information-model:06-09-test-result|6.9 Test Result]]
 +  * [[dido:03-dido-te:06-information-model:06-10-test-run|6.10 Test Run]]
 +  * [[dido:03-dido-te:06-information-model:06-11-test-tag|6.11 Test Tag]]
 +  * [[dido:03-dido-te:06-information-model:06-12-test-environment-relationships|6.12 Test Environment Relationships]]
 +  * [[dido:03-dido-te:06-information-model:06-13-test-definition|6.13 Test Definition]]
 +  * [[dido:03-dido-te:06-information-model:06-14-integrated-information-model|6.14 Integrated DIDO-TE Information Model]]
 +
 +===== Source =====
 +
 +The initial structural content of this section is derived from the Testing Package of [[dido:03-dido-te:99-annexes:annex-b-references:dte-004|[DTE4] DIDO Reference Data Model]].
 +
 +DIDO-TE-specific refinements are derived from the DIDO-TE architecture and requirements.
 +
 +===== Notes for Editors =====
 +
 +  * Preserve the distinction between [DTE4] source-model content and DIDO-TE extensions.
 +  * Use [[dido:03-dido-te:05-common-information-types:start|Section 5, Common Information Types]] for reusable datatype, structured-type, enumeration, identifier, name, parameter, and other common-type definitions.
 +  * Do not redefine Common Information Types on Information Model class pages.
 +  * Do not silently correct [DTE4] source-model anomalies.
 +  * Review each source-model element independently before establishing the integrated model.
 +  * Use focused [[dido:99_annexes:annex-b-terms-and-definitions:u:uml|UML]] class diagrams for the individual model-element sections.
 +  * Preserve [DTE4] multiplicities unless a deliberate DIDO-TE refinement is documented.
 +  * Do not interpret UML classes as prescribed software implementation classes.
 +  * Maintain explicit Traceability between model refinements and the DIDO-TE requirements that require those refinements.
 +  * Develop the Test Definition after reviewing its constituent information elements.
 +  * Use Section 6.14 to present the resulting integrated DIDO-TE Information Model after the individual elements have been reviewed.
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>