Differences

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

--- public:99_annexes:annex-b-terms-and-definitions:e:executable_artifact [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1
+++ public:99_annexes:annex-b-terms-and-definitions:e:executable_artifact [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
@@ Line 1: / Line 1: @@
+====== Execution Facility ======
+[[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
+===== Discussion =====
+An Execution Facility is an [[public:99_annexes:annex-b-terms-and-definitions:o:operational_resource|Operational Resource]] that interprets or performs [[public:99_annexes:annex-b-terms-and-definitions:e:executable_instruction|Executable Instructions]].
+An Execution Facility can provide one or more capabilities required to execute instructions, including:
+  * Processing
+  * Interpretation
+  * Scheduling
+  * Automation
+  * Communication
+  * Data access
+  * State management
+  * Model execution
+  * Service invocation
+  * Device control
+  * Measurement
+  * Observation
+  * Result capture
+  * Error reporting
+An Execution Facility can include:
+  * A processor
+  * A physical machine
+  * A virtual machine
+  * A container runtime
+  * A process
+  * A command processor
+  * An interpreter
+  * A compiler runtime
+  * An automation engine
+  * A workflow engine
+  * A test framework
+  * A model-execution engine
+  * A database engine
+  * A service
+  * A device controller
+  * A hardware test instrument
+  * A human-operated execution tool
+  * A combination of hardware, software, and services
+An Execution Facility can identify:
+  * Its identity
+  * Its name
+  * Its description
+  * Its type
+  * Its [[public:99_annexes:annex-b-terms-and-definitions:v:version|Version]]
+  * Its supported instruction languages or formats
+  * Its supported operations
+  * Its available interfaces
+  * Its applicable [[public:99_annexes:annex-b-terms-and-definitions:e:endpoint|Endpoints]]
+  * Its required dependencies
+  * Its resource requirements
+  * Its operating constraints
+  * Its supported [[public:99_annexes:annex-b-terms-and-definitions:e:executable_instruction|Executable Instructions]]
+  * Its applicable [[public:99_annexes:annex-b-terms-and-definitions:e:executable_artifact|Executable Artifacts]]
+  * Its applicable [[public:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environments]]
+  * Its applicable [[public:99_annexes:annex-b-terms-and-definitions:d:deployment_target|Deployment Targets]]
+  * Its applicable [[public:99_annexes:annex-b-terms-and-definitions:g:governance_policy|Governance Policies]]
+  * Its [[public:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]]
+  * Its [[public:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]
+A [[public:99_annexes:annex-b-terms-and-definitions:t:test_executable|Test Executable]] contains or references the Executable Instructions used during [[public:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]].
+The Execution Facility interprets or performs those Executable Instructions within the applicable [[public:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]].
+A Test Environment can contain, provide, identify, or provide access to one or more Execution Facilities.
+===== Definition =====
+//[[public:99_annexes:annex-b-terms-and-definitions:o:operational_resource|Operational Resource]] that interprets or performs [[public:99_annexes:annex-b-terms-and-definitions:e:executable_instruction|Executable Instructions]]//
+===== Source =====
+Adapted from:
+  * [[https://www.omg.org/spec/TestIF/1.0/Beta3/PDF|OMG Test Information Interchange Format (TestIF), Version 1.0 Beta 3, Section 7.3.7, TestExecutable]]
+  * [[public:99_annexes:annex-b-terms-and-definitions:e:executable_instruction|Executable Instruction]]
+  * [[public:99_annexes:annex-b-terms-and-definitions:t:test_executable|Test Executable]]
+  * [[public:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]]
+  * [[public:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]]
+  * DIDO Reference Implementation Conceptual Model
+  * DIDO-TE draft Requirements Register
+OMG TestIF describes TestExecutable as a low-level procedural definition that supports test automation through executable information such as code and scripts.
+OMG TestIF does not define Execution Facility as a separate TestIF model element. This definition introduces Execution Facility to identify the Operational Resource that interprets or performs the Executable Instructions associated with a Test Executable.
+===== Note =====
+An Execution Facility differs from an [[public:99_annexes:annex-b-terms-and-definitions:e:executable_instruction|Executable Instruction]]:
+  * An Executable Instruction specifies an operation
+  * An Execution Facility interprets or performs the operation
+An Execution Facility differs from a [[public:99_annexes:annex-b-terms-and-definitions:t:test_executable|Test Executable]]:
+  * A Test Executable contains, organizes, or references Executable Instructions
+  * An Execution Facility interprets or performs those Executable Instructions
+An Execution Facility differs from an [[public:99_annexes:annex-b-terms-and-definitions:e:executable_artifact|Executable Artifact]]:
+  * An Executable Artifact stores, packages, or provides Executable Instructions
+  * An Execution Facility loads, interprets, invokes, or performs those instructions
+An Execution Facility differs from a [[public:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]]:
+  * A Test Environment identifies the conditions, resources, configurations, and dependencies required to conduct testing
+  * An Execution Facility provides a capability for interpreting or performing Executable Instructions within that Test Environment
+An Execution Facility differs from a [[public:99_annexes:annex-b-terms-and-definitions:d:deployment_target|Deployment Target]]:
+  * A Deployment Target identifies a destination onto which a deployable artifact can be installed, configured, or activated
+  * An Execution Facility interprets or performs Executable Instructions
+A Deployment Target can provide or host an Execution Facility. The same resource can act as both when it satisfies both definitions.
+An Execution Facility differs from a [[public:99_annexes:annex-b-terms-and-definitions:n:node|Node]]:
+  * A Node is an identifiable participant that performs one or more assigned roles in a distributed system
+  * An Execution Facility provides the capability to interpret or perform Executable Instructions
+A Node can host, use, or provide access to one or more Execution Facilities. An Execution Facility does not become a Node unless it also acts as an identifiable participant with assigned roles in the distributed system.
+An Execution Facility can use other Execution Facilities. For example, a test framework can invoke a command processor, which invokes a runtime, which sends a request to a service.
+An Execution Facility can operate locally or remotely. Physical location does not determine whether a resource qualifies as an Execution Facility.
+An Execution Facility is not necessarily dedicated to testing. The facility qualifies when it interprets or performs Executable Instructions used for the applicable purpose.
+A human does not ordinarily constitute an Execution Facility. A human-operated tool can constitute an Execution Facility when the tool interprets or performs the Executable Instructions and the human controls or initiates its operation.
+A reproducible [[public:99_annexes:annex-b-terms-and-definitions:t:test_run|Test Run]] should identify the applicable Execution Facilities and their Versions, configurations, dependencies, and operating conditions.
+===== Example =====
+A [[public:99_annexes:annex-b-terms-and-definitions:t:test_executable|Test Executable]] references a versioned script that submits a proposed transaction to a [[public:99_annexes:annex-b-terms-and-definitions:n:node|Node]].
+The applicable Execution Facilities include:
+  * A container runtime that starts the test container
+  * A command processor that invokes the script
+  * A language interpreter that interprets the script
+  * A test framework that supplies the applicable [[public:99_annexes:annex-b-terms-and-definitions:t:test_argument_value|Test Argument Values]]
+  * A service that processes the resulting request
+During [[public:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]], the Execution Facilities:
+  * Load the referenced [[public:99_annexes:annex-b-terms-and-definitions:e:executable_artifact|Executable Artifact]]
+  * Interpret or perform its Executable Instructions
+  * Submit the proposed transaction through the applicable [[public:99_annexes:annex-b-terms-and-definitions:e:endpoint|Endpoint]]
+  * Capture the response
+  * Provide the resulting data to the [[public:99_annexes:annex-b-terms-and-definitions:t:test_run|Test Run]]
+The Test Run records:
+  * The identity of each Execution Facility
+  * The Version of each Execution Facility
+  * The applicable configuration
+  * The applicable dependencies
+  * The applicable [[public:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]]
+  * The resulting [[public:99_annexes:annex-b-terms-and-definitions:t:test_result|Test Result]]
+  * The supporting [[public:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]
+----
+<WRAP centeralign>
+© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
+</WRAP>