Operational Resource

An Operational Resource is a Resource used to perform or support an operational activity.

An Operational Resource can include:

  • A person
  • A service
  • A software component
  • A physical machine
  • A virtual machine
  • A container
  • A network
  • A storage facility
  • A database
  • A test instrument
  • A communication facility
  • An external system
  • Another resource required to conduct or support operations

An Operational Resource can identify:

  • Its identity
  • Its name
  • Its description
  • Its type
  • Its owner
  • Its operator
  • Its applicable Roles
  • Its provided capabilities
  • Its required capabilities
  • Its interfaces
  • Its applicable Endpoints
  • Its dependencies
  • Its configuration
  • Its availability
  • Its capacity
  • Its operational status
  • Its applicable Governance Policies

A Test Environment can contain, identify, allocate, configure, or provide access to Operational Resources required for Test Execution.

Resource used to perform or support an operational activity

Adapted from:

  • DIDO Reference Architecture
  • DIDO Reference Implementation Conceptual Model
  • DIDO-TE draft Requirements Register

Every Operational Resource is a Resource. A Resource is not necessarily an Operational Resource.

A Resource becomes an Operational Resource when an operational activity uses or depends on it.

An Operational Resource differs from a Test Environment:

  • An Operational Resource performs or supports an operational activity
  • A Test Environment identifies the conditions, configurations, dependencies, and Operational Resources required to conduct testing

An Operational Resource differs from a Deployment Target:

  • An Operational Resource performs or supports an operational activity
  • A Deployment Target provides a destination for installing, configuring, or activating a deployable artifact

The same resource can satisfy both definitions.

An Operational Resource differs from an Execution Facility:

  • An Operational Resource performs or supports an operational activity
  • An Execution Facility interprets or performs Executable Instructions

Every Execution Facility used operationally is an Operational Resource. An Operational Resource is not necessarily an Execution Facility.

An Operational Resource can be:

  • Dedicated or shared
  • Permanent or temporary
  • Local or remote
  • Physical or virtual
  • Human-operated or automated
  • Internal or external to the system

A DIDO-TE Test Environment uses the following Operational Resources:

  • Three Nodes forming a Node Set
  • A container runtime
  • A test automation service
  • A database
  • A communication network
  • An Artifact Repository
  • A monitoring service
  • A User acting in the Test Operator Role

Each Operational Resource supports the applicable Test Execution and appears in the resulting Test Run record.


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

  • dido/99_annexes/annex-b-terms-and-definitions/o/operational_resource.txt
  • Last modified: 2026/08/04 13:47
  • by nick_dido