NOD-005b — Initiate Node Execution

Go to NOD-005 — Execute a Node

The DIDO-TE SHALL initiate each authorized execution of a Node through an identified execution procedure.

• NOD-005 — Execute a Node
• NOD-005a — Authorize Node Execution
• NOD-004c — Confirm Node Readiness
• [DTE5] DIDO-TE Requirements Register, source requirement identifier and obligation to be assigned
• [DTE6] Structured Information Processing Reference Architecture (SIP-RA)
• [DTE7] Federated Data Interpretation Systems Reference Architecture (FDIS-RA)

Initiating Node execution changes the Node from a ready condition to active participation in an identified Test Execution.

The execution procedure identifies the target Node, applicable authorization, initiating authority, start condition, execution parameters, sequence, timing, required Node Bindings, required Test Resources, and expected initial execution state.

Node startup and Node execution initiation represent distinct activities. Startup establishes the operating Node. Execution initiation directs that operating Node to begin its assigned Test Execution activity.

Controlled initiation prevents premature, duplicate, conflicting, incorrectly sequenced, or unauthorized Node activity and establishes the point from which the DIDO-TE observes and records Node execution.

• DIDO-TE
• Node
• Node Definition
• Node Implementation
• Node Configuration
• Node Binding
• Test Definition
• Test Input
• Test Resource
• Test Environment
• Test Execution
• Evidence
• Traceability

Verification confirms that:

• The DIDO-TE uniquely identifies the Node before initiating its execution.
• The DIDO-TE identifies the applicable Test Execution and Test Definition.
• The DIDO-TE verifies a current and applicable Node execution authorization.
• The DIDO-TE confirms that the Node retains its successful validation and readiness status.
• The DIDO-TE confirms that the Node occupies the required lifecycle state.
• The DIDO-TE uses an identified and authorized execution procedure.
• The execution procedure identifies the initiating authority, target Node, start condition, parameters, sequence, timing, Node Bindings, Test Resources, and intended initial execution state.
• The DIDO-TE verifies each mandatory execution precondition before initiating Node execution.
• The DIDO-TE confirms that each required Node Binding and Test Resource is available.
• The DIDO-TE coordinates initiation with applicable Nodes, Dependencies, and Test Resources.
• The DIDO-TE initiates Node execution at the specified event, condition, or time.
• The DIDO-TE supplies execution parameters through their specified mechanisms.
• The DIDO-TE prevents premature, duplicate, conflicting, unauthorized, or out-of-sequence initiation.
• The DIDO-TE observes the Node while execution is initiated.
• The DIDO-TE detects an unsuccessful, incomplete, interrupted, stalled, or timed-out initiation.
• The DIDO-TE confirms that the intended Node entered the required initial execution state.
• The DIDO-TE detects Node activity that begins before authorization or the specified start condition.
• An unsuccessful initiation leaves the Node in a known state or identifies the resulting state and required corrective action.
• The DIDO-TE prevents a Node with an unsuccessful, incomplete, ambiguous, or unauthorized initiation result from continuing Test Execution.
• The DIDO-TE records the Node identity, Test Execution, authorization, initiating authority, execution procedure, start condition, parameters, sequence, timing, observations, resulting state, findings, exceptions, and corrective actions.
• Repeated initiation under equivalent controlled conditions produces equivalent initial execution states within specified tolerances.
• The DIDO-TE maintains Traceability among the Node, authorization, validation result, readiness result, Test Definition, Test Execution, execution procedure, Node Bindings, Test Resources, initiation activity, resulting state, findings, exceptions, and resulting Evidence.
• An incorrect, incomplete, unsuccessful, premature, unauthorized, ambiguously timed, or untraceable initiation constitutes nonconformance with this requirement.

Verification includes:

• Inspection of the Node identity, Test Execution, and authorization
• Inspection of validation and readiness results
• Inspection of the authorized execution procedure and responsible authority
• Inspection of execution preconditions, parameters, sequence, timing, Node Bindings, and Test Resources
• Observation of Node execution initiation
• Confirmation of the initial execution state
• A negative assessment involving premature initiation
• A negative assessment involving duplicate or out-of-sequence initiation
• A negative assessment involving an unavailable mandatory Node Binding or Test Resource
• A negative assessment involving interrupted or timed-out initiation
• Confirmation that unsuccessful initiation prevents continued Test Execution
• Inspection of initiation records, findings, exceptions, corrective actions, Evidence, and Traceability

• Add links to the architecture sections governing Node execution initiation, Node lifecycle state, execution authorization, Test Execution coordination, Evidence, 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-005b-initiate-node-execution#Statement&noheader&nofooter&noeditbtn}}