Traceability - Backlinks [Dido Solutions, Inc Wiki]

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

3.2.2 Explicit Separation of Interpretive Concerns
1.1 Purpose
1.2 Scope
1.3 Intended Audience
1.4.1 Why a Wiki
1.4.3 Using the Wiki
1. Introduction
2.1 Operational Need
2.2 Mission and Expected Outcomes
2. Operational Need and Mission
3.1 Connectivity Conditions
3.2 Deployment Environments
3.3 Security Domains and Transfer Boundaries
3. Operational Environment
4.1 Human Actors
4.3 External Systems
5.1 Select and Compose Baselines
5.2 Construct Images
5.3 Capture and Preserve Dependencies
5.4 Assess Compliance
5.5 Deploy the Environment
5.6 Validate the Result
5.7 Preserve Evidence and Lifecycle Records
5. Operational Concept
6.2 Deploy in a Connected Environment
7.4 Import the Transfer Bundle
MO-001a — Infrastructure Environment Creation
MO-001b — Deployment Duration
MO-001c — Reproducibility
MO-001d — Security Baseline Conformance
MO-001e — Compliance Baseline Conformance
MO-001 — Repeatable, Compliant, and Secure Infrastructure Environments
MO-002a — Maximum Platform Deployment Duration
MO-002b — Platform Deployment Duration Reduction
MO-002 — Reduced Platform Deployment Timelines
MO-003a — Cross-Platform Deployment
MO-003b — Provider-Independent Crucible Description
MO-003c — Provider-Independent Infrastructure Baseline
MO-003d — Limitation of Provider-Specific Dependencies
MO-003 — Cloud-Agnostic Deployment
MO-004a — Connected Environment Operations
MO-004b — Disconnected Environment Operations
MO-004c — Authorized Resource Use
MO-004d — Disconnected Resource Availability
MO-004 — Connected and Disconnected Operations
MO-005a — Infrastructure Baseline Artifact Management
MO-005b — Infrastructure Baseline Identification
MO-005c — Infrastructure Baseline Revision Control
MO-005d — Approved Infrastructure Baseline Selection
MO-005e — Infrastructure Baseline Reuse
MO-005f — Approved Infrastructure Baseline Preservation
MO-005g — Infrastructure Deployment Baseline Traceability
MO-005 — Reusable and Version-Controlled Infrastructure Baselines
MO-006a — Operational Lifecycle Association
MO-006b — Infrastructure Lifecycle Initiation
MO-006c — Infrastructure Lifecycle State Recording
MO-006d — Infrastructure Lifecycle Transition Execution
MO-006e — Infrastructure Environment Retirement
MO-006 — Infrastructure Lifecycle Management
OR-001a — Developer Operations
OR-001b — DevSecOps Engineer Operations
OR-001c — Platform Engineer Operations
OR-001d — System Administrator Operations
OR-001e — Security Engineer Operations
OR-001f — Compliance Officer Operations
OR-002c — Deployment Acceptance Record
OR-003a — Classified Environment Operations
OR-003b — Unclassified Environment Operations
OR-003 — Classified and Unclassified Environments
FR-CFG-002 — Infrastructure as Code
C.3.1 Configuration Management
C.3.2 Image Management
C.3.3 Deployment Orchestration
C.3.4 Multi-Cloud Management
FR-AG-005 — Deployment Traceability Across Disconnected Environments
C.3.5 Air-Gapped Operations
C.3.6 Compliance Management
C.3.8 DevSecOps Integration
C.3.9 Baseline Composition and Workspace
C.3.10 Dependency Capture and Offline Transfer
C.3.11 Crucible Interfaces
Crucible
MO-001 — Governed Distributed Test Environments
MO-002a — Reproducible Test Environments
MO-002b — Reproducible Test Execution
MO-003 — Automated 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-006a — Application-Independent Testing
MO-006b — Infrastructure-Independent Testing
MO-006 — Application-Independent and Infrastructure-Independent Testing
MO-007a — Connected Environment Operation
MO-007b — Disconnected Environment Operation
MO-007c — Air-Gapped Environment Operation
MO-007 — Connected, Disconnected, and Air-Gapped Operation
MO-008a — Test Result Traceability
MO-008b — Evidence Traceability
MO-008 — Traceable Test Results and Evidence
MO-009a — Test Resource Description
MO-009b — Test Resource Control
MO-009c — Test Resource Applicability
MO-009d — Test Resource Use Traceability
MO-009 — Reusable Test Resources
C.1 Mission Objectives
ENV-001c — Identify Included Test Objects
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-003a — Apply Required Baseline
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-004f — Control Execution Ordering
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-006 — Reproduce Real-World Conditions
NOD-001a — Identify the Node Role
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-001g — Define Node Observability Requirements
NOD-001h — Validate the Node Definition
NOD-001 — Define 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
NOD-002g — Record Node Provisioning
NOD-002h — Validate the Provisioned Node
NOD-002 — Provision a Node
NOD-003a — Select the Node Configuration
NOD-003b — Resolve Node Configuration Values
NOD-003c — Apply the Node Configuration
NOD-003e — Protect Sensitive Configuration Values
NOD-003f — Record Node Configuration
NOD-003g — Validate the Configured Node
NOD-003 — Configure a Node
NOD-004a — Establish the Initial Node State
NOD-004b — Start the Node
NOD-004c — Confirm Node Readiness
NOD-004d — Transition the Node State
NOD-004e — Stop the Node
NOD-004g — Handle a Node Lifecycle Exception
NOD-004h — Record Node Lifecycle Activity
NOD-004 — Control the Node Lifecycle
NOD-005a — Authorize Node Execution
NOD-005b — Initiate Node Execution
NOD-005c — Provide Node Inputs
NOD-005d — Observe Node Execution
NOD-005e — Control Node Execution
NOD-005f — Handle a Node Execution Exception
NOD-005g — Complete Node Execution
NOD-005h — Record Node Execution
NOD-005 — Execute a Node
NOD-006 — Isolate a Node
NOD-007 — Identify a Node
NOD-008a — Establish Node Observation
NOD-008b — Observe Node State
NOD-008c — Observe Node Activity
NOD-008d — Observe Node Resource Use
NOD-008e — Detect a Node Deviation
NOD-008f — Record Node Observations
NOD-008 — Observe a Node
NOD-009a — Establish Node Resource Controls
NOD-009b — Allocate Node Resources
NOD-009c — Control Node Resource Use
NOD-009d — Handle a Node Resource-Control Exception
NOD-009e — Release Node Resources
NOD-009f — Record Node Resource Control
NOD-009 — Control Node Resources
NOD-010a — Specify a Node Fault
NOD-010b — Authorize Node Fault Injection
NOD-010c — Prepare Node Fault Injection
NOD-010d — Inject a Node Fault
NOD-010e — Control a Node Fault
NOD-010f — Recover from a Node Fault
NOD-010g — Record Node Fault Injection
NOD-010 — Inject Node Faults
NOD-011a — Specify Node State Preservation
NOD-011b — Capture Node State
NOD-011c — Protect Preserved Node State
NOD-011d — Verify Preserved Node State
NOD-011e — Retain Preserved Node State
NOD-011f — Restore Preserved Node State
NOD-011g — Dispose of Preserved Node State
NOD-011h — Record Node State Preservation
NOD-011 — Preserve Node State
NOD-012 — Reset a Node
NOD-013 — Maintain Node Traceability
C.3.2 Node Requirements
C.3.3 Twin Node Requirements
TWIN-001c — Identify a Twin Realization
TWIN-002c — Preserve Twin Realization Association
TWIN-005f — Preserve Twin Realization State Provenance
TWIN-010 — Maintain Twin Traceability
CON-006 Define Traceability Relationships
CON-009 Define Requirements Traceability
Conceptual Semantics
Conformance Semantics
Datatype Semantics
Graph Semantics
Implementation Semantics
Lifecycle Semantics
Ontological Semantics
OWL Semantics
Policy Semantics
Report Semantics
Rule Semantics
Schema Semantics
Terminological Semantics
Type Semantics
Vocabulary Semantics
Taxonomy of Semantics
Access Control
Actor
Application Independence
Authorization to Operate (ATO)
Audit and Provenance State Record
Audit Recording Role
Authority
Architectural Element
Candidate Solution
Catalog
Catalog Entry
Community of Interest
Compliance
Concept of Operations (ConOps)
Configuration Precedence
Configuration Record
Configuration Source
Configuration Validation
Configuration Value
Conformance Model
Contract State Management Role
Controlled Input
Cost
Credential
Cryptographic Material
Deployment Target
Deployment Target Catalog
Energy Consumption
Evaluation Characteristic
Exception Handling
Execution Facility
Executable Instruction
Executable Instruction
Execution Path
Expected Result
Functional Correctness
FX Audit and Provenance Node
FX Audit Record
FX Audit Record Endpoint
FX Cash-Flow Obligation
FX Cash-Flow Obligation Endpoint
FX Command Acknowledgement
FX Contract State
FX Contract State Endpoint
FX Contract State Node
FX Contract State Transition
FX Endpoint Traceability
FX Evidence Traceability
FX Information Structure Traceability
FX Interaction Traceability
FX Logical Admission Rules
FX Logical Change Control
FX Logical Compatibility
FX Logical Ownership of Definitions
FX Logical Policy Constraints
FX Logical Versioning
FX Node Traceability
FX Provenance Record
FX Provenance Record Endpoint
FX Release Package
FX Release Package Endpoint
FX Replay and Reconstruction Node
FX Replay Request
FX Replay Request Endpoint
FX Replay Result
FX Replay Result Endpoint
FX Runtime Plane Traceability
FX Semantic Assertion
FX Semantic Interpretation Endpoint
FX Transaction Intake Endpoint
FX Transaction Intake Node
FX Transaction Lifecycle State
FX Transaction Record
FX Validation Result
FX Validation Result Endpoint
Git
Git Operations (GitOps)
Governance Policy
Governed
Infrastructure as Code (IaC)
Image Promotion
Image Provenance
Incomplete Test Run
Infrastructure Independence
Interpretation-Controlled Transition
Inventory
JSON Schema
Logical Node
Maintainability
Ontology
Operational Resource
Operational Stability
Organization
Oversight Consumption Role
Part 1 Concept to FX Logical Profile Element
Part 1 Concept to FX Logical Profile Element
Performance Efficiency
Policy
Provenance
Provenance Recording Role
Pull Lock
Quality Characteristic
RDF Triple
Record
Recoverability
Registry
Registry and Coordination Role
Reliability
Replay and Reconstruction Role
Repository
Requirement
Resource
Resource Consumption
Role
Semantic Business Vocabulary Model (SBVM)
Scalability
Security Control Traceability Matrix (SCTM)
Security
Semantic Interpretation Role
Sequenced Test Object
Sequence Step
Software Supply Chain
Structured Query Language (SQL)
Starting Condition
Storage Consumption
T
Test Argument
Test Argument Value
Test Case
Test Definition
Test Executable
Test Execution
Test Execution Exception
Test Execution Exception Type
Test Input
Test Item
Test Object
Test Outcome
Test Result
Test Run
Test Run State
Test Run Termination Reason
Test Set
Test Step
Timeout
Timing Condition
Transaction Intake Role
Twin Identifier
Twin Identifier
Twin Realization Type
User
Validation
Validation-Controlled Transition
Validation Criteria
Validation Decision
Verdict
Version
Version Pinning
P1-REQ-13-4-001
P1-REQ-13-4-010
P1-REQ-13-5-010
P1-REQ-13-6-001
P1-REQ-13-6-006
P1-REQ-13-6-008
P1-REQ-13-6-012
P1-REQ-13-7-001
P1-REQ-13-7-006
P1-REQ-13-7-007
P1-REQ-13-7-008
P1-REQ-13-7-009
P1-REQ-13-8-004
P1-REQ-13-8-006
P1-REQ-13-9-003
P1-REQ-13-9-006
P1-REQ-13-10-008
P2-REQ-16-3-006
P2-REQ-16-7-007
P2-REQ-16-8-005
P2-REQ-16-9-002
P2-REQ-16-9-010
P2-REQ-16-9-011
P2-REQ-16-9-012
P2-REQ-16-9-013
Foreword
Introduction
1. Scope
3.1 Traceability to SIP-RA
3.2 Alignment with FDIS-RA
3.4 Traceability Position
3. Traceability to Parent and Source Architectures
4.5 Traceability
5.6 Classification Values and Runtime Identifiers
6.5 Classification Inheritance for FX Profiles
7.1 Overview
7.10
8.1 Overview
8.7 Cross-Plane Relationships
9.1 Overview
9.8 Cross-Concern Relationships
10.1 Overview
10.2 Traceability Across Layers
10.3 Conceptual Element to Logical Element / PIM
10.4 Logical Element / PIM to Implementation Artifact / PSM
10.7 Bidirectional Review and Impact Analysis
10.8 Traceability Boundaries
11.9 Traceability Preserves Layering
11.11 Conceptual Constraints Summary
12.4 Logical Architecture Remains Platform Independent
12.7 Traceability from Part 1 to Part 2
13.1 Overview
13.4 Core Conceptual Element Requirements
13.5 Runtime Plane Requirements
13.6 Separation of Concerns Requirements
13.7 Traceability Requirements
13.8 Evidence Requirements
13.9 Relationship to Logical Architecture / PIM Requirements
13.10 Profile and Layering Requirements
Foreword
2. Relationship to Part 0 and Part 1
3.1 Traceability to SIP-RA
3.2 Alignment with FDIS-RA
3.3 Traceability to Part 1 Conceptual Architecture
3.5 Traceability Position
3. Traceability to Parent and Source Architectures
4.6 Traceability from Concept to Logical Model
5.3 Distributed Logical Node Network
5.4 Logical Communication Model
5.5 Logical Information Model
5.7 Logical Traceability Model
7.1 Overview
7.12 Communication Direction and Coupling
10.1 Overview
10.4 Publish Domain Information
10.5 Subscribe to Domain Information
10.6 Issue Control Command
12.1 Overview
12.9 Logical Traceability Summary
13.1 Overview
13.2 How Domain Profiles Specialize the Logical Architecture
13.3 Domain Profile Additions
13.4 What Domain Profiles Preserve
13.5 Relationship to the FX Demo Logical Profile
13.6 Boundary Between Part 2 and Domain Logical Profiles
14.2 Logical Elements Prepared for Technology Mapping
14.6 Implementation Mapping Boundaries
14.8 Boundary Between Part 2 and Implementation Profiles
15.6 Logical Interactions Remain Traceable
15.8 Logical Architecture Does Not Prescribe Communication Pattern Implementation
15.10 Domain Profiles Preserve the Logical Architecture
15.12 Logical Constraints Summary
16.1 Overview
16.3 Logical Node Requirements
16.7 Logical Interaction Requirements
16.8 Logical Governance Requirements
16.9 Logical Traceability Requirements
Foreword
3.1 Traceability to SIP-RA
3.2 Alignment with FDIS-RA
3.3 Traceability to Part 1 Conceptual Architecture
3.4 Traceability to Part 2 Distributed Node-Based Logical Architecture / PIM
3.6 Traceability Position
3. Traceability to Parent and Source Architectures
4.2 FX Domain Scope before Implementation
4.4 Explicit FX Communication Endpoints
4.5 FX Information Structures before Serialisation
4.7 Traceability from Concept to Logical Profile
4.8 Evidence-Oriented FX Logical Design
5.1 Overview
5.2 FX Demo Classification Path
5.4 FX Demo Logical Node Network
5.5 FX Demo Logical Communication Model
5.8 FX Demo Logical Traceability Model
8.1 Overview
12.1 Overview
12.5 Validate FX Transaction Candidate
12.6 Interpret FX Transaction Semantics
12.8 Compute FX Cash-Flow Obligations
12.10 Release FX Information to Oversight Participant
13.1 Overview
13.8 FX Logical Governance Summary
14.1 Overview
14.10 FX Logical Traceability Summary
15.1 Overview
15.2 FX Logical Elements Prepared for Technology Mapping
15.6 Boundary Between Part 3 and Part 4
16.3 FX Logical Endpoints Remain Distinct from Communication Technologies
16.4 FX Logical Data Structures Remain Distinct from Serialisation Formats
16.6 FX Logical Interactions Remain Traceable
16.8 FX Demo Logical Profile Does Not Prescribe Communication Pattern Implementation
16.10 FX Demo Logical Constraints Summary
17.1 Overview
1. Scope
2. Relationship to Parts 0, 1, 2, and 3
3.1 Traceability to SIP-RA
3.2 Alignment with FDIS-RA
3.3 Traceability to Part 1 Conceptual Architecture
3.4 Traceability to Part 2 Distributed Node-Based Logical Architecture / Platform-Independent Model (PIM)
3.5 Traceability to Part 3 FX Demo Logical Profile
3.7 Traceability to the Phase 0 Developer Handbook
3.8 Traceability Position
3. Traceability to Parent and Source Architectures
4.1 Overview
4.2 Phase 0 Implementation Scope
4.3 Phase 0 Implementation Baseline
4.4 Phase-Specific Nature of the Profile
4.5 Relationship to the FX Demo Logical Profile
4.6 Relationship to Later Development Phases
4.7 Phase 0 Implementation Profile Summary
4. Phase 0 Implementation Profile Overview
5.1 Overview
5.3 Traceability Before Code
5.4 Developer Handbook Before Coding
5.7 Runtime Plane Discipline in Implementation
5.9 Minimal Phase 0 Scope Before Expansion
5.10 Phase 0 Implementation Principles Summary
6.1 Overview
6.2 Part 3 Working Baseline
6.3 Phase 0 Developer Handbook
6.4 Repository Baseline
6.7 Traceability Baseline
6.8 No-Code-Before-Handbook Constraint
6.9 Phase 0 Implementation Preconditions Summary
7.3 IDL as Phase 0 Data Definition Mechanism
7.6 Python as Phase 0 Implementation Language
7.7 Scripts as Phase 0 Build and Execution Helpers
7.8 Repository Structure as Phase 0 Implementation Organization
7.9 Technology Selection Boundaries
8.1 Overview
8.10 FX Audit and Provenance Node Mapping
8.15 FX Logical Node Mapping Summary
9.1 Overview
9.17 Endpoint-to-Topic Mapping Summary
10.1 Overview
10.2 Information Structure Mapping Principles
10.20 Information-Structure-to-IDL Mapping Summary
13.2 QoS Profile Purpose
13.3 QoS Profile Mapping Principles
13.4 Control Plane QoS Profile
13.5 Data Plane QoS Profile
13.6 Health and Observability Plane QoS Profile
13.7 Policy and Release Plane QoS Profile
13.8 Audit and Provenance Plane QoS Profile
13.10 QoS Boundaries and Non-Goals
14.1 Overview
14.2 Repository Organization Principles
14.4 IDL Directory Model
14.7 Script Directory Model
14.8 Documentation Directory Model
14.9 Traceability Artifact Model
14.13 Repository and Build Artifact Summary
15.2 Purpose of the Developer Handbook
15.4 File-Header Requirements
15.5 Generated-File Header Requirements
15.6 Naming Convention Requirements
15.7 Coding Style Requirements
15.10 Traceability Convention Requirements
15.11 Repository Workflow Requirements
15.12 Script Usage Requirements
15.13 Review Checklist Requirements
15.14 Developer Handbook Summary
16.4 Type Generation
16.9 Script Logging and Error Handling
16.10 Script Approval and Baseline Status
16.11 Script Model Summary
17.2 Implementation Ownership
17.3 Implementation Versioning
17.4 Implementation Compatibility
17.5 Implementation Change Control
17.6 Generated Artifact Governance
17.7 Repository Governance
17.8 Developer Handbook Governance
17.9 Implementation Governance Summary
18.1 Overview
18.2 Part 3 FX Logical Element to Part 4 Implementation Artifact
18.3 Implementation Artifact to Part 3 FX Logical Element
18.4 Node Implementation Traceability
18.5 Topic Implementation Traceability
18.6 IDL and Generated Type Traceability
18.7 Runtime Plane Implementation Traceability
18.8 Script and Repository Traceability
18.9 Developer Handbook Traceability
18.10 Implementation Traceability Summary
19.1 Overview
19.2 Boundary Between Part 4 and Part 5
19.3 Implementation Artefacts Prepared for Deployment
19.4 Implementation Artefacts Prepared for Testability
19.6 Implementation Artefacts Prepared for Evidence
19.7 Part 5 Handoff
19.8 Relationship to Deployment, Testability, and Evidence Plan Summary
20.3 DDS Topics Do Not Redefine Logical Communication Endpoints
20.4 IDL Structures Do Not Redefine Logical Information Structures
20.5 Generated Types Do Not Redefine Logical Information Structures
20.6 Runtime Processes Do Not Redefine FX Logical Nodes
20.7 Repository Layout Does Not Redefine Architecture
20.8 Scripts Do Not Redefine Interaction Patterns
20.9 Developer Handbook Does Not Replace the Implementation Profile
20.10 Phase 0 Does Not Define Later Phase Implementation Profiles
21.1 Overview
Foreword
Introduction
1.1 Purpose of the Handbook
1.4 How to Use This Handbook
2.2 Relationship to SIP-RA
2.6 Relationship to Generated Code and Runtime Artefacts
3.1 Purpose of the Phase 0 Baseline
3.6 Baseline Change Control
7.4 Generated File Naming
7.11 Spelling, Grammar, and Style
7. Naming and File Conventions
8.1 Purpose of Generated Artifacts
9.2 IDL Source Location
12.1 Purpose of the Data Plane in Phase 0
12.7 Data Plane Non-Goals for Phase 0
9.5 Evidence-Based Assignment and Review

dido/99_annexes/annex-b-terms-and-definitions/t/traceability.txt
Last modified: 2026/08/04 07:09
by nick_dido