NOD-005h — Record Node Execution

The DIDO-TE SHALL record each execution of a Node.

A Node execution record preserves the identity, context, sequence, activity, observations, inputs, outputs, decisions, exceptions, and completion status associated with a Node’s participation in Test Execution.

The record identifies which Node executed, the applicable Node Definition, Node Implementation, Node Configuration, Test Definition, Test Environment, and Test Execution. It also identifies the authority permitting execution, applicable procedures, Test Inputs, Node Bindings, Test Resources, timing, observed behavior, control actions, outputs, and resulting Node state.

The Node execution record supports reconstruction of Test Execution, evaluation of Test Outcomes and Test Results, diagnosis of failures, disposition of Test Execution Exceptions, reproduction of testing, and production of Evidence.

Incomplete, inaccurate, mutable, inconsistently timed, or untraceable execution records prevent the DIDO-TE from demonstrating what the Node did and which conditions governed its behavior.

Verification confirms that:

  • Each Node execution record has a unique identity.
  • Each Node execution record identifies the applicable Node and Test Execution.
  • Each Node execution record identifies the applicable Node Definition, Node Implementation, Node Configuration, Test Definition, and Test Environment.
  • Each Node execution record identifies the Authorizing Authority and the authorization under which execution occurred.
  • Each Node execution record identifies the applicable initiation, execution-control, exception-handling, and completion procedures.
  • Each Node execution record identifies the initial and final Node states.
  • Each Node execution record identifies its initiation time, completion time, duration, and applicable sequence.
  • Each Node execution record uses a controlled and consistent time reference.
  • Each Node execution record identifies the Test Inputs supplied to the Node.
  • Each Node execution record identifies the Node Bindings, Dependencies, and Test Resources used during execution.
  • Each Node execution record identifies the execution parameters and operating constraints.
  • Each Node execution record identifies the Node activities, interactions, observations, outputs, state changes, and resource use material to Test Execution.
  • Each Node execution record identifies the control actions applied during execution and their actual effects.
  • Each Node execution record identifies each Test Execution Exception, its type, disposition, responsible Authorizing Authority, actions, and resolution status.
  • Each Node execution record identifies the completion conditions, resource dispositions, resulting Node state, and completion status.
  • Each Node execution record identifies the applicable Test Outcome and Test Results.
  • The DIDO-TE distinguishes intended Node activity from observed Node activity.
  • The DIDO-TE distinguishes expected outputs from actual outputs.
  • The DIDO-TE associates each material input, activity, observation, output, control action, exception, and state change with the applicable time and sequence.
  • The DIDO-TE detects a missing, incomplete, inconsistent, duplicated, altered, out-of-sequence, ambiguously timed, misattributed, or unauthorized Node execution record.
  • A material correction to a Node execution record produces a distinguishable revision and preserves the prior record.
  • The DIDO-TE protects Node execution records from unauthorized alteration, disclosure, or deletion.
  • The DIDO-TE preserves Node execution records for the retention period governing the applicable Test Execution and Evidence.
  • The DIDO-TE supports reconstruction of the Node execution sequence from initiation through completion.
  • The DIDO-TE maintains Traceability among the Node Definition, Node Implementation, Node Configuration, Test Definition, Test Environment, Test Execution, Authorizing Authority, Test Inputs, Node Bindings, Test Resources, Node activity, observations, outputs, control actions, exceptions, completion status, Test Outcome, Test Results, and resulting Evidence.
  • A missing, incomplete, inaccurate, altered, unauthorized, ambiguous, misattributed, or untraceable Node execution record constitutes nonconformance with this requirement.

Verification includes:

  • Inspection of Node execution record identities
  • Inspection of Node, Test Execution, Node Definition, Node Implementation, Node Configuration, Test Definition, and Test Environment references
  • Inspection of the Authorizing Authority and authorization applicable to the execution
  • Inspection of initiation, execution-control, exception-handling, and completion procedures
  • Inspection of Test Inputs, Node Bindings, Dependencies, Test Resources, execution parameters, and operating constraints
  • Inspection of recorded Node activity, observations, outputs, state changes, control actions, and resource use
  • Inspection of Test Execution Exceptions, dispositions, actions, and resolution status
  • Confirmation that records distinguish intended activity and outputs from observed activity and outputs
  • Confirmation that execution records use a controlled and consistent time reference
  • Reconstruction of a selected Node execution from initiation through completion
  • A negative assessment involving a missing or incomplete execution record
  • A negative assessment involving an altered, misattributed, or unauthorized execution record
  • A negative assessment involving an out-of-sequence or ambiguously timed record
  • Confirmation that a material correction preserves the prior record
  • Inspection of retention controls, Test Outcomes, Test Results, Evidence, and Traceability
  • Add links to the architecture sections governing Node execution records, time synchronization, Test Execution, Test Outcomes, Test Results, Evidence retention, and Traceability.

Assign the applicable delivery phase.

Draft

Use the following syntax to reference this requirement’s Statement section from another DokuWiki page:

{{section>dido:03-dido-te:99-annexes:annex-c-requirements:03-node-requirements:nod-005-execute-a-node:nod-005h-record-node-execution#Statement&noheader&nofooter&noeditbtn}}

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

  • dido/03-dido-te/99-annexes/annex-c-requirements/03-functional-requirements/03-02-node-requirements/nod-005-execute-a-node/nod-005h-record-node-execution.txt
  • Last modified: 2026/08/17 14:20
  • by nick_dido