Differences

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

--- dido:03-dido-te:06-information-model:start [2026/08/23 17:06] – removed - external edit (Unknown date) 127.0.0.1
+++ dido:03-dido-te:06-information-model:start [2026/08/23 17:09] (current) – nick_dido
@@ Line 1: / Line 1: @@
+====== 6. DIDO-TE Information Model ======
+[[dido:03-dido-te:start|Go to DIDO-TE Cover Page]]
+The DIDO-TE Information Model defines the principal information elements, relationships, and structures used to describe, configure, execute, observe, and evaluate tests within the [[dido:99_annexes:annex-b-terms-and-definitions:d:dido-te|DIDO-TE]].
+The Information Model provides the architectural vocabulary and structural relationships used by the DIDO-TE [[dido:99_annexes:annex-b-terms-and-definitions:r:requirement|requirements]] and [[dido:99_annexes:annex-b-terms-and-definitions:c:concept_of_operations|Concept of Operations (ConOps)]]. It establishes what information exists and how that information is related without prescribing a particular storage technology, serialization format, programming language, database schema, or implementation platform.
+The [[dido:99_annexes:annex-b-terms-and-definitions:m:model|model]] builds upon [[dido:03-dido-te:99-annexes:annex-b-references:dte-004|[DTE4] DIDO Reference Data Model]] and extends that model where required by the DIDO-TE architecture.
+===== Purpose =====
+The DIDO-TE Information Model provides a common structural basis for:
+  * defining the subject and scope of a test;
+  * organizing test plans, [[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]];
+  * identifying [[dido:99_annexes:annex-b-terms-and-definitions:t:test_executable|Test Executables]] and their [[dido:99_annexes:annex-b-terms-and-definitions:t:test_argument|Test Arguments]];
+  * specifying [[dido:99_annexes:annex-b-terms-and-definitions:e:expected_result|Expected Results]];
+  * identifying the [[dido:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]] in which testing occurs;
+  * representing the participants and [[dido:99_annexes:annex-b-terms-and-definitions:r:resource|Resources]] required by a test;
+  * specifying state, time, network, communication, [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration|Configuration]], and other governed test conditions;
+  * representing [[dido:99_annexes:annex-b-terms-and-definitions:t:test_result|Test Results]] and [[dido:99_annexes:annex-b-terms-and-definitions:t:test_run|Test Runs]];
+  * supporting [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] among [[dido:99_annexes:annex-b-terms-and-definitions:t:test_definition|Test Definitions]], [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Executions]], Test Results, and supporting [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]; and
+  * providing a structural foundation for the DIDO-TE Concept of Operations and normative requirements.
+===== 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 class definitions reference those common types rather than redefining their structure or semantics within individual class descriptions.
+This separation allows a common type to be reused consistently by multiple model elements.
+===== Modeling Approach =====
+The Information Model distinguishes architectural concepts from their implementation.
+[[dido:99_annexes:annex-b-terms-and-definitions:u:uml|Unified Modeling Language (UML)]] class diagrams in this section describe information elements and their relationships. The diagrams are not intended to prescribe object-oriented software classes or a particular implementation technology.
+Each model element is described using:
+  * its architectural purpose;
+  * its defining characteristics;
+  * its attributes, where applicable;
+  * the Common Information Types used by those attributes;
+  * its associations with other model elements;
+  * association multiplicities where established by [DTE4];
+  * relevant constraints and architectural interpretation; and
+  * Traceability to [DTE4] and DIDO-TE requirements.
+Where [DTE4] provides an element or relationship, this section preserves that source-model structure unless DIDO-TE introduces a deliberate refinement.
+Where DIDO-TE introduces a concept not represented in [DTE4], the extension is identified explicitly rather than being represented as though it existed in the source model.
+===== Relationship to the DIDO Reference Data Model =====
+The initial DIDO-TE Information Model is derived in part from the Testing Package of [DTE4].
+[DTE4] includes the following principal testing elements:
+  * **Test**
+  * **Test Plan**
+  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_set|Test Set]]
+  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_case|Test Case]]
+  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_step|Test Step]]
+  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_executable|Test Executable]]
+  * [[dido:99_annexes:annex-b-terms-and-definitions:e:expected_result|Expected Results]]
+  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_result|Test Result]]
+  * [[dido:99_annexes:annex-b-terms-and-definitions:t:test_run|Test Run]]
+  * **Test Tag**
+[DTE4] also establishes relationships between the testing structure and its execution environment.
+DIDO-TE extends this foundation with architectural concepts required for governed distributed testing, including Test Environment Configuration, [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Nodes]], [[dido:99_annexes:annex-b-terms-and-definitions:t:twin_node|Twin Nodes]], [[dido:99_annexes:annex-b-terms-and-definitions:v:virtual_network|Virtual Networks]], communication conditions, state control, time control, [[dido:99_annexes:annex-b-terms-and-definitions:v:validation|Validation]], Evidence, and other concepts defined by the DIDO-TE requirements.
+===== Relationship to Test Definition =====
+The [[dido:99_annexes:annex-b-terms-and-definitions:t:test_definition|Test Definition]] provides the governed specification of what is required for a test.
+[DTE4] does not define a model element named Test Definition. The DIDO-TE Information Model therefore derives the structure of the Test Definition from:
+  * the existing testing elements and relationships represented by [DTE4];
+  * the Common Information Types used by those model elements;
+  * the information required by the DIDO-TE functional requirements; and
+  * the relationships required to connect test specification, Test Execution, Test Results, Validation, and Evidence.
+The Test Definition model is developed after the constituent testing elements are described so that its structure is derived from those elements rather than imposed independently of them.
+===== Relationship to the Concept of Operations =====
+The Information Model defines the information elements and relationships used by DIDO-TE.
+The [[dido:99_annexes:annex-b-terms-and-definitions:c:concept_of_operations|Concept of Operations (ConOps)]] describes how actors, capabilities, systems, and processes create, configure, use, exchange, and evaluate those information elements during testing.
+Accordingly:
+  * the Information Model defines **what information exists and how it is related**; and
+  * the Concept of Operations describes **how that information participates in DIDO-TE operations**.
+===== Relationship to Requirements =====
+The DIDO-TE [[dido:99_annexes:annex-b-terms-and-definitions:r:requirement|requirements]] place normative obligations on the concepts and relationships defined by the Information Model.
+In particular, [[dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-06-test-definition-requirements:start|C.3.6 Test Definition Requirements]] identifies the information that a governing Test Definition is required to specify, identify, or reference.
+The Information Model provides the structural basis for those requirements. Annex C remains the normative source of DIDO-TE conformance obligations.
+===== Contents =====
+  * [[dido:03-dido-te:06-information-model:06-01-overview:start|6.1 Information Model Overview]]
+  * [[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]]
+{{indexmenu>dido:03-dido-te:06-information-model#1|js navbar nocookie maxjs#1 id#dido_te_information_model_nav}}
+===== Source =====
+The initial structure 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]] and is refined by the DIDO-TE architecture and requirements.
+===== Notes for Editors =====
+  * Treat [DTE4] as the source for existing modeled elements, relationships, attributes, multiplicities, and types.
+  * 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 anomalies in [DTE4]. Identify corrections or architectural refinements explicitly.
+  * Use focused UML class diagrams for individual model elements before producing the integrated Information Model.
+  * Preserve [DTE4] multiplicities where they are known unless a deliberate DIDO-TE refinement is approved.
+  * Distinguish [DTE4] source-model content from DIDO-TE extensions.
+  * Do not treat UML classes as implementation classes.
+  * Develop the Test Definition structure from the constituent model elements and the obligations identified by the DIDO-TE requirements.
+  * Use the integrated diagram in Section 6.14 to show the resulting DIDO-TE Information Model after the individual elements have been reviewed.
+----
+<WRAP centeralign>
+© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
+</WRAP>