B12 CB TA

What each thing means

Requirement

One thing the product must do or satisfy — the “what”.

Test Case

A defined check that proves one or more requirements — the “how we prove it”. A verified_by trace link ties a test case to the requirement(s) it covers; that link is exactly what Coverage % counts. (So: a test case refers to the requirements it verifies.)

Verification Plan

A named grouping of test cases, approved before a test campaign and optionally gated by a milestone.

Verification Record

The result of running one test case against one unit: pass / fail / error / na. This is the evidence a requirement is actually met.

DUT

Device Under Test — an individual physical unit (by serial number) that records and test data attach to.

Deviation

A documented waiver against a verification record (e.g. accept a known non-conformance, with justification).

Entry

A knowledge note: a decision (settled choice), notice (assumption / risk / open question), issue (tracked problem), or concept (idea under exploration). It can attach to any other entity.

Design Rule

A reusable, checkable engineering constraint. Running the checks turns each violation into a Conflict.

Conflict

An open flag raised by a failed design-rule check (or an end-of-life / component-library issue) that needs resolving.

Milestone

A dated gate; verification plans can be tied to it.

Field Issue (RMA)

A failure reported from the field on a returned unit; Root-Cause Analysis explains why it happened.

The Loop (S-16)

loop_trace reconciles a field issue against that unit’s own verification record (did it pass at the edge of the band?). closes_loop records the corrective decision or design rule so the lesson is captured — and clears the project’s open-loop count.

Interface / Port

A contract between projects; each port can be driven by a requirement (and cascade one into the connected project).

BOM Component

A part on this project’s bill of materials, optionally linked to the shared Component Library.

GRR Study

A Gauge R&R study measuring how repeatable a test case’s measurement is.

Test Data

Production / Maestro run results recorded against DUTs — the population behind a single verification record.