6.1 Information Model Overview

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-TE.

The model is derived initially from the Testing Package of [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 Test Sets, Test Cases, and Test Steps that compose the test structure;the Test Executables and Test Arguments used to perform test activities;the Expected Results used to describe expected test behavior;the Test Environment in which testing occurs;the Nodes, Twin Nodes, and other Resources participating in testing;the Configuration, communication, state, and time conditions governing testing;the Test Results produced by testing;the Test Runs associated with those Test Results; andthe information required to support Validation, Evidence, and Traceability.

Relationship to Common Information Types

The DIDO-TE Information Model uses reusable information types defined in 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:

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

[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; andany 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:

;Test Environment configuration and controlled environmental conditions;Twin Node participation;Virtual Network and communication conditions;controlled test state;controlled test time;Validation Criteria;Evidence requirements; andgoverned 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 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 Test Execution;the information required to interpret Test Results; andthe 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:

Test Definition
|
v
Test Structure and Test Conditions
|
v
Test Execution
|
v
Test Results
|
v
Comparison and Validation
|
v
Evidence and Traceability

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 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; andC.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:

Source

The initial structural content of this section is derived from the Testing Package of [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 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 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.

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.