Configuration - Backlinks [Dido Solutions, Inc Wiki]

This is a list of pages that seem to link back to the current page.

MO-002a — Reproducible Test Environments
MO-002 — Reproducible Test Environments and Test Execution
MO-004a — DIDO Baseline Comparison
MO-004b — Validation Decision Based on DIDO Baseline Comparison
MO-004 — DIDO Baseline Comparison and Validation
MO-005 — Comparative Evaluation of Candidate Solutions
MO-008a — Test Result Traceability
ENV-001a — Define Test Environment Purpose
ENV-001b — Identify Applicable Test Definitions
ENV-001d — Identify Included Nodes
ENV-001e — Identify Required Test Resources
ENV-001g — Define Configuration Values
ENV-001k — Define Version and Baseline Information
ENV-001 — Define Test Requirements
ENV-002a — Apply Controlled Descriptive Information
ENV-002b — Instantiate Included Test Objects
ENV-002c — Instantiate Included Nodes
ENV-002d — Provision Required Test Resources
ENV-002e — Apply Configuration Values
ENV-002f — Establish Communication Relationships
ENV-002g — Enforce Environmental Constraints
ENV-002h — Enforce Security Constraints
ENV-002i — Enforce Deployment Constraints
ENV-002j — Apply Version and Baseline Information
ENV-002k — Record Test Environment Configuration
ENV-002l — Validate Test Environment Configuration
ENV-002 — Configure Test Environment
ENV-003b — Apply Required Configuration Values
ENV-003c — Initialise Participating Nodes
ENV-003d — Initialise Test Objects
ENV-003e — Provision Required Test Resources
ENV-003f — Load Required Test Inputs
ENV-003g — Establish Required Communication Relationships
ENV-003h — Apply Applicable Constraints
ENV-003i — Remove or Isolate Residual State
ENV-003j — Validate Controlled Starting State
ENV-003k — Record Controlled Starting State
ENV-003l — Prevent Execution from Invalid Starting State
ENV-003 — Establish Controlled Starting State
ENV-004a — Define Deterministic Environmental Conditions
ENV-004b — Control Baselines and Configurations
ENV-004c — Control Test Inputs
ENV-004d — Control Time Sources
ENV-004e — Control Random Values
ENV-004g — Control Resource Allocation
ENV-004h — Control External Dependencies
ENV-004i — Control Communication Conditions
ENV-004j — Detect Environmental Variation
ENV-004k — Record Environmental Variation
ENV-004l — Validate Environmental Determinism
ENV-004m — Prevent Execution Under Uncontrolled Conditions
ENV-004 — Provide Deterministic Test Environment
ENV-005a — Emulate Distributed Topology
ENV-005b — Emulate Participating Nodes
ENV-005c — Emulate Communication Behaviour
ENV-005d — Emulate Time and Clock Conditions
ENV-005e — Emulate Resource Conditions
ENV-005f — Emulate Node Failures
ENV-005g — Emulate Communication Failures
ENV-005h — Emulate Network Partitions
ENV-005i — Emulate Membership and Topology Changes
ENV-005j — Emulate Recovery Behaviour
ENV-005k — Observe Distributed Interactions
ENV-005l — Record Distributed-System Emulation
ENV-005m — Validate Emulation Fidelity
ENV-005 — Emulate Distributed Systems
ENV-006 — Reproduce Real-World Conditions
ENV-007 — Support Repeatable Test Environments
NOD-001b — Identify the Node Type
NOD-001c — Define Node Interfaces
NOD-001d — Define Node Dependencies
NOD-001e — Define Node Resource Requirements
NOD-001f — Define Node Lifecycle Behaviour
NOD-001h — Validate the Node Definition
C.3.3 Twin Node Requirements
TWIN-001c — Identify a Twin Realization
TWIN-002c — Preserve Twin Realization Association
TWIN-003 — Configure a Twin Relationship
TWIN-003a — Identify Represented Twin Characteristics
TWIN-003b — Configure Twin Data Mappings
TWIN-003c — Identify Eligible Twin Data Sources
TWIN-003d — Configure Twin Source Selection
TWIN-003e — Configure Twin Communication Parameters
TWIN-003e — Configure Twin Communication Parameters
TWIN-003g — Configure Twin Synchronization Parameters
TWIN-003h — Configure Twin Fidelity Criteria
TWIN-004 — Select a Twin Realization
TWIN-005 — Access Twin Realization State
TWIN-005a — Establish the Initial State of a Twin Realization
TWIN-005b — Determine the Current State of a Twin Realization
TWIN-005c — Access Twin Realization State Values
TWIN-005d — Identify the State Data Source
TWIN-005e — Associate Twin Realization State with Time
TWIN-005g — Detect an Invalid or Unknown Twin Realization State
TWIN-006 — Synchronize Twin Realization State
TWIN-006a — Synchronize State Between Twin Realizations
TWIN-006b — Limit Synchronization to Represented Characteristics
TWIN-006c — Apply Synchronization Parameters
TWIN-006d — Detect Synchronization Failure
TWIN-007 — Simulate Twin Behavior
TWIN-010 — Control Twin Interaction
TWIN-010a — Identify Permitted Twin Interactions
TWIN-010b — Specify Twin Interaction Direction
TWIN-010c — Require Authorization for Resource State Changes
TWIN-010d — Prevent Unauthorized Resource State Changes
TWIN-010e — Reject Prohibited Twin Interactions
Application Independence
Candidate Solution
Compliance
Data Source
Digital Twin
Energy Consumption
Evaluation Characteristic
Infrastructure Independence
Maintainability
Operational Stability
Performance Efficiency
Qualified Node
Recoverability
Reliability
Resource Consumption
Scalability
Source Selection
Starting Condition
Storage Consumption
Test Execution Exception
Test Execution Exception Type
Twin Node
Twin Realization Type
Twin Relationship
19.3 Implementation Artefacts Prepared for Deployment
19.6 Implementation Artefacts Prepared for Evidence
20.3 DDS Topics Do Not Redefine Logical Communication Endpoints
20.7 Repository Layout Does Not Redefine Architecture
Introduction
1.1 Purpose of the Handbook
1.3 Intended Audience
2.2 Relationship to SIP-RA
2.6 Relationship to Generated Code and Runtime Artefacts
3.1 Purpose of the Phase 0 Baseline
3.3 FX Demo Logical Profile Baseline
3.5 Repository Baseline
4.1 Repository Design Principles
4.3 Source Directories
4.4 Generated Artefact Directories
4.5 Configuration Directories
4.6 Script Directories
4.7 Test Directories
4.9 Git-Controlled and Non-Git-Controlled Content
4. Repository Layout
5.2 VS Code / Code
5.3 Python Environment
5.5 DDS Tooling
5.7 Git Environment
6.5 Prerequisite Validation
6.7 Tool Baseline Checklist
6.8 Multiple Products, Platforms, and Implementations
7.1 General Naming Principles
7.2 Directory Naming
7.3 Source File Naming
7.6 Configuration File Naming
7.8 Node Naming
7.10 File Headers and Inline Documentation
7.11 Spelling, Grammar, and Style
8.1 Purpose of Generated Artifacts
8.2 Generated Versus Handwritten Files
8.4 Python-Generated Support Artifacts
8.5 Generated Documentation
8.6 Regeneration Rules
8.7 Protecting Handwritten Code from Overwrite
10.3 Node Startup Behavior
10.8 Node Configuration
10. Node Implementation Pattern
13.8 buildContainers.sh
13.9 runAll.sh
13.10 runNode.sh
13.13 Script Exit Codes
13.14 Script Logging
14.1 Purpose of Containerisation in Phase 0
14.4 Container Runtime Configuration
14.7 Container Logs
14.8 Container Cleanup
16.1 Purpose of Exception Handling Rules
16.4 Configuration Errors
16.6 Container Errors
16.7 Recoverable and Non-Recoverable Errors
16.8 Error Reporting
17.1 Repository Initialisation
17.4 Pull Request Expectations
17.6 Generated File Review Rules
17.7 Tagging the Phase 0 Baseline
17. Git and Review Workflow
18.4 Node Acceptance Criteria
18.8 Documentation Acceptance Criteria

dido/99_annexes/annex-b-terms-and-definitions/c/configuration.txt
Last modified: 2026/07/23 13:17
by nick_dido