Skip to content

Cairn Documentation

Verification & Traceability

Verification confirms that your system meets its requirements. Traceability connects everything — requirements to nodes, verifications to requirements, decisions to rationale.

Verification Methods

Four standard methods:

Test: Physical or functional testing that measures performance.

"Conduct range test: drive vehicle until battery depletes, measure total distance traveled."

Analysis: Calculation or simulation that demonstrates compliance.

"Power budget analysis shows 18% margin under worst-case assumptions."

Demonstration: Operational exercise that shows capability.

"Demonstrate successful delivery sequence with live operator monitoring."

Inspection: Visual or physical examination.

"Inspect connector pinout against ICD; verify thermal compound application."

Verification Titles

Beyond the method and description, every verification carries a short title — the line that appears in the Inspector heading and in cascade previews when you delete the requirement it verifies. AI-generated verifications come with a title by default; rewrite it in the Inspector at any time.

Coverage and Closure

Cairn counts verification by requirement. A requirement with no activity has no method. It is in progress while its activities are drafts or planned, passed once every activity verifying it has passed, and failing as soon as one fails or is blocked. The Verification lens shows that split as a closure bar, for the selected node alone or with everything below it. Overview's Verification card and Quality use the same rule.

Flowdown

A requirement can be derived from a requirement on a node above it: a system requirement flows down into subsystem requirements that together meet it. Set the parent when you add a requirement or in the inspector, and the Requirements lens's Flowdown view nests each derived requirement under its parent across levels.

Trace Links

Trace links connect entities across your model:

  • satisfies: A design element satisfies a requirement
  • verifies: A verification record verifies a requirement
  • derives: A child requirement derives from a parent
  • depends_on: One node depends on another

The Traceability tool (⌘⇧X) shows a matrix view with gaps immediately visible: each requirement, the parts that satisfy it and its verifications. A row that isn't fully traced has Link, which adds the part that satisfies the requirement and points to the Verification lens for the other half. Other kinds of link are made in the Trace lens.

Impact Analysis

Trace links enable impact analysis: "If I change this requirement, what's affected?" The Traceability tool highlights the impact chain when you select any entity.

This is a core advantage of connected models over disconnected documents. When everything links to everything else, you can actually answer "what does this affect?"