Traceability Dashboard¶
Link-health monitor — instantiates Traceability Linking
Watches the health of an existing link set — surfacing unowned items, unresolved exceptions, and links that have gone stale or broken since the work was done.
Trace links are easy to create and quietly easy to rot; a link drawn correctly today points at nothing after next quarter's refactor. Traceability Dashboard is the standing monitor that keeps a link set alive after the initial linking work is done. It does not draw links or decide what should be linked — it watches the ones that exist and continuously flags the three ways traceability decays: items with no owner to keep them current, exceptions (waived, missing, or not-applicable links) that were logged but never resolved, and links that have gone stale or broken because the artifacts they connect changed or moved. Its distinguishing stance is temporal and custodial: every other mechanism in the archetype acts at the moment a link is made; the dashboard is the one that notices, weeks later, that the link is no longer true.
Example¶
Three weeks before a design certification review, the chief engineer of a large aerospace program opens the Traceability Dashboard first each morning. It does not create a single link — those already exist across requirements, tests, and design artifacts. What it shows is the state of them: requirement-to-verification coverage sitting at ≈87%, and, more usefully, the specific rot. After last month's avionics spec change, 40 previously-valid verification links now point at superseded requirement versions — stale. Twelve requirements have no assigned owner, so no one is accountable for closing their gaps. Nine logged exceptions ("verification deferred to flight test") remain open past their promised resolution date. None of this is new linking work; it is the maintenance backlog the dashboard makes impossible to ignore, sorted so the team burns it down — owners assigned, stale links re-pointed, exceptions resolved or formally accepted — before the auditor finds it first.
How it works¶
- Poll the link set against expectations. Read the existing links and the coverage rules defined elsewhere, and render — continuously, as counts and drill-downs rather than a one-time report — where reality falls short.
- Detect the decay modes. Flag unowned items (no
link_owner), exceptions left unresolved past due, and links whose endpoints changed version, moved, or vanished (stale or broken). - Track state over time. Because it watches the same links repeatedly, it records how link health trends — improving before a milestone, decaying after a big change — which a snapshot cannot show.
Tuning parameters¶
- Staleness definition — how much change to a linked artifact makes a link "stale" (any edit versus a material version bump). Sensitive settings catch drift early but generate noise after routine edits.
- Metric selection — which health signals earn a panel (coverage %, unowned count, overdue exceptions, broken-link count). Choosing the wrong headline invites gaming the visible number.
- Alert threshold — the level at which a decay signal escalates from a dashboard row to a notification. Aggressive alerting drives fast maintenance but risks fatigue.
- Aggregation grain — program-wide rollup versus per-team or per-subsystem views. Rollups suit governance; fine grain suits the people who must actually fix the links.
When it helps, and when it misleads¶
Its strength is sustaining traceability past the moment of creation: it converts silent link rot into a visible, ownable backlog, and it is what lets a team walk into an audit knowing the gaps rather than discovering them.
It misleads when the dashboard becomes the goal. A single reassuring headline — "94% coverage" — can stay green while the underlying links quietly go stale, a classic vanity metric: the number trends well precisely because it is the thing being managed, not the traceability it stands for.[n1] The related misuse is optimizing for the panel rather than the property — re-pointing links to clear a "stale" count without checking they are still meaningful, or waiving exceptions to zero the overdue list. The discipline is to treat the dashboard as an attention-router, not a verdict: it tells you where to look, and someone still has to open the link and confirm it says something true.
How it implements the components¶
Traceability Dashboard fills the monitoring and custodial components — the ones that keep a link set healthy rather than create it:
link_owner— surfaces items with no responsible owner, the precondition for anything getting maintained, and routes them to be assigned.exception_record— tracks logged exceptions (waived, missing, not-applicable) and flags the ones left unresolved past their promised date, so gaps can't hide as "exceptions."audit_trail— because it watches the same links over time, it records how they were created, changed, went stale, or were retired: the trend history a one-shot check can't provide.
It creates none of the links it watches: trace_link, link_semantics, and source_reference come from Source Control Linkage, Test Coverage Link, and Citation Chain, and it evaluates but does not author the coverage_rule (Requirements Traceability Matrix / Test Coverage Link).
Related¶
- Instantiates: Traceability Linking — the maintenance layer that keeps the archetype's links trustworthy after they are drawn.
- Consumes: every link-creating sibling — it monitors the output of Source Control Linkage, Test Coverage Link, Requirements Traceability Matrix, Data Lineage Record, and others.
- Sibling mechanisms: Test Coverage Link · Source Control Linkage · Requirements Traceability Matrix · Change Impact Report · Audit Trail Record · Data Lineage Record · Decision Log · Citation Chain · Chain-of-Custody Record
Editorial Notes¶
Form Classification¶
Form family: Monitoring, Sensing & Alerting
Rationale: Traceability Dashboard operates as ongoing observation, sensing, or alerting that detects and surfaces state without itself executing the response because it watches the health of an existing link set — surfacing unowned items, unresolved exceptions, and links that have gone stale or broken since the work was done.
Independent corroboration: The frozen evidence defines Traceability Dashboard as 'Watches the health of an existing link set — surfacing unowned items, unresolved exceptions, and links that have gone stale or broken since the work was done', so its operative form is Monitoring, Sensing & Alerting.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Engineering & Design
Origin pattern: Convergent development
Present-day reach: Universal
Rationale: NASA Systems Engineering Handbook requires bidirectional requirements traceability and continuing verification that links remain owned, current, and satisfied. This directly supports engineering design as the best-evidenced historical home of the operation—Watches the health of an existing link set — surfacing unowned items, unresolved exceptions, and links that have gone stale or broken since the work was done.—while the alternates record adjacent lineages rather than mere domains of later use.
Related originating lineages:
- Computer Science & Software Engineering — Computer science and software-engineering practice supplies a parallel or contributing lineage for the mechanism's defining operation: watches the health of an existing link set — surfacing unowned items, unresolved exceptions, and links that have gone stale or broken since the work was done.
- Logistics & Supply Chain Management — Logistics supply chain supplies a historically relevant adjacent lineage or formative practice for the operation—Watches the health of an existing link set — surfacing unowned items, unresolved exceptions, and links that have gone stale or broken since the work was done.—but the researched evidence more directly locates the defining lineage in engineering design.
- Organizational & Management Science — Organizational design, management, and operational governance supplies a parallel or contributing lineage for the mechanism's defining operation: watches the health of an existing link set — surfacing unowned items, unresolved exceptions, and links that have gone stale or broken since the work was done.
- Systems Thinking & Cybernetics — Systems thinking, feedback control, and cybernetics supplies a parallel or contributing lineage for the mechanism's defining operation: watches the health of an existing link set — surfacing unowned items, unresolved exceptions, and links that have gone stale or broken since the work was done.
Review resolution: The blind reviewers disagree on primary lineage (logistics_supply_chain versus engineering_design). The defining operation is: Watches the health of an existing link set — surfacing unowned items, unresolved exceptions, and links that have gone stale or broken since the work was done. The researched NASA Systems Engineering Handbook requires bidirectional requirements traceability and continuing verification that links remain owned, current, and satisfied. That is mechanism-specific evidence for engineering design as the historical origin. Logistics supply chain remains represented among the uncapped alternates where it contributes a genuine formative practice, but broad deployment or governance of the operation is not by itself evidence that the mechanism originated there. origin_mode=convergent records lineage; domain_reach=universal separately records later applicability.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Researched adjudication after independent review; medium confidence.
Sources consulted:
Notes¶
The dashboard depends entirely on links other mechanisms create; it can only reveal problems in traceability that has actually been attempted. A domain with no trace links to begin with produces a dashboard that looks perfectly healthy — nothing to flag — which is its most dangerous failure: absence of links read as absence of problems.
[n1] Vanity metric — a headline figure that trends reassuringly while the underlying property it is meant to represent does not. Coverage percentages on a status dashboard are a common example: easy to move by managing the number itself rather than the traceability it is supposed to reflect. ↩