NOD-002g — Record Node Provisioning

Go to NOD-002 — Provision a Node

The DIDO-TE SHALL record each Provisioning activity performed for a Node.

• NOD-002 — Provision a Node
• NOD-002a — Select the Node Definition
• NOD-002b — Select the Node Implementation
• NOD-002c — Resolve Node Dependencies
• NOD-002d — Allocate Node Resources
• NOD-002e — Instantiate the Node
• NOD-002f — Establish the Node Initial State
• [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)

A provisioning record preserves the controlled history of how the DIDO-TE created or obtained a Node instance. It identifies the inputs selected, activities performed, outputs produced, decisions made, and conditions encountered during provisioning.

The record supports reproducibility, accountability, diagnosis, validation, and interpretation of subsequent Test Results. It also distinguishes the intended provisioning procedure from the procedure actually performed.

An incomplete, altered, or untraceable provisioning record prevents an assessor from determining whether the Node instance corresponds to its approved definition and implementation.

• DIDO-TE
• Node
• Node Definition
• Node Implementation
• Provisioning
• Dependency
• Test Resource
• Test Environment
• Evidence
• Traceability

Verification confirms that:

• Each Node Provisioning activity has a unique identity.
• The provisioning record identifies the provisioned Node instance.
• The provisioning record identifies the Node Definition and version.
• The provisioning record identifies the Node Implementation, version, build, variant, source, and integrity information.
• The provisioning record identifies each resolved mandatory Dependency.
• The provisioning record identifies each allocated Test Resource.
• The provisioning record identifies the applicable Test Environment and Test Definition.
• The provisioning record identifies the provisioning procedure, procedure version, tools, scripts, automation, commands, templates, and parameters used.
• The provisioning record identifies the person, organisation, service, or automated agent responsible for each material activity.
• The provisioning record identifies the start time, completion time, duration, and applicable time source.
• The provisioning record identifies the location, platform, infrastructure, runtime, network, storage, and middleware context material to provisioning.
• The provisioning record preserves the sequence of material provisioning activities.
• The provisioning record identifies the actual inputs consumed and outputs produced.
• The provisioning record identifies each selection, resolution, allocation, instantiation, and initial-state activity.
• The provisioning record identifies each validation, integrity, compatibility, and availability check performed during provisioning.
• The provisioning record identifies each warning, error, exception, retry, substitution, deviation, rollback, and recovery action.
• Each approved exception or deviation identifies its authority, rationale, scope, duration, and expected effect.
• The provisioning record identifies the final provisioning status and completion determination.
• The provisioning record distinguishes successful, unsuccessful, partial, interrupted, superseded, and rolled-back provisioning attempts.
• The provisioning record identifies any residual artifact, resource, process, allocation, or state produced by an unsuccessful attempt.
• The provisioning record uses stable identities for referenced artifacts and records.
• Each reference contained in the provisioning record resolves to the applicable artifact or record.
• The DIDO-TE protects the provisioning record against unauthorised access, alteration, substitution, and deletion.
• The DIDO-TE preserves the provenance and integrity of the provisioning record.
• The DIDO-TE applies the applicable retention, confidentiality, handling, and disposal requirements.
• The provisioning record contains sufficient information to repeat the provisioning activity and compare resulting Node instances.
• The DIDO-TE records the provisioning record as Evidence.
• The DIDO-TE maintains Traceability among the provisioning record, Node Definition, Node Implementation, implementation artifacts, Dependencies, Test Resources, Test Environment, provisioning activities, Node instance, initial state, validation result, and resulting Evidence.
• A missing, incomplete, altered, ambiguous, unauthorised, or untraceable mandatory provisioning record constitutes nonconformance with this requirement.

Verification includes:

• Inspection of the provisioning record identity and structure
• Inspection of recorded Node Definition and Node Implementation information
• Inspection of recorded Dependencies and Test Resources
• Inspection of procedures, tools, scripts, commands, templates, and parameters
• Comparison of recorded activities with observed provisioning activities
• Confirmation of actor, authority, location, and timing information
• Confirmation that findings, exceptions, retries, deviations, and recovery actions remain recorded
• Confirmation that references resolve to identified artifacts and records
• Integrity and provenance verification of the provisioning record
• Review of access-control, retention, confidentiality, handling, and disposal controls
• Reproduction of provisioning using the recorded information
• A negative assessment involving a missing provisioning input
• A negative assessment involving an altered provisioning record
• A negative assessment involving an unresolved record reference
• Inspection of Evidence and Traceability

• Add links to the architecture sections governing Provisioning records, provenance, integrity, Evidence, Traceability, configuration management, retention, and reproducibility.

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-002-provision-a-node:nod-002g-record-node-provisioning#Statement&noheader&nofooter&noeditbtn}}