Accordion Test Adapter
ESH10000518 · Rev R1
in_progresselectronicstest
Everything here lives inside a Project (a code + revision, e.g. ESH10000540 R3).
The backbone is the V-model, read top-to-bottom: define what the product must do, plan how to prove it,
execute the proof on real units, then learn from the field — and the Loop closes back up to the top.
This map is live: a block is green with a count when this project actually has that entity,
and dashed/dim when it’s empty. Click any block to open its tab; hover for details.
Arrows are the meaningful links; the implicit “belongs to this Project” edge is left out for legibility.
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_tracereconciles a field issue against that unit’s own verification record (did it pass at the edge of the band?).closes_looprecords 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.
100%
Coverage
91%
Done
21
Requirements
21
Test Cases
7
Open Entries
Timeline
Color = derived gate state · hover a tile for its note.overdue / blocked
🏁 Release
Status & gates
Chronological — Release is the final gate. Derived & read-only; edit viatrace_milestone_* tools.Release / Readiness overdue / blocked 5/6 met1 failing
met
Requirements approved
met Coverage ≥ 100%
- 21/21 requirements covered (100%)
failing All test cases pass
- 19/21 passed
- 2 failing: V-10, V-20
met
No blocking issues open
met
Deviations resolved
met
Interfaces frozen
Test Cases
19 Pass
2 Fail / Deviated
0 N/A
0 Open0 / 21 Maestro impl.
Coverage — 100.0% · Done — 90.5%
| Code | Title | Category | Coverage | Status |
|---|---|---|---|---|
REQ-001 |
Local 2.5V voltage reference (VREF) | Functional | Covered | Done |
REQ-002 |
7× M3 fixating holes | Mechanical | Covered | Done |
REQ-003 |
Vertical USB connector | Mechanical | Covered | Done |
REQ-004 |
SO-DIMM connector within board outline | Mechanical | Covered | Done |
REQ-005 |
20V power input via USB PD | Functional | Covered | Done |
REQ-006 |
Power input from Com-Top module | Functional | Covered | Done |
REQ-007 |
Local 5V regulated supply rail | Functional | Covered | Done |
REQ-008 |
Local 3V3 regulated supply rail | Functional | Covered | Done |
REQ-009 |
Local 1V8 regulated supply rail | Functional | Covered | Done |
REQ-010 |
All supply rails distributed to all module slots | Functional | Covered | Not Started |
REQ-011 |
Per-module power switch for hot-swap (rated ≥1A) | Functional | Covered | Done |
REQ-012 |
Per-module shunt current measurement (0–1A range) | Functional | Covered | Done |
REQ-013 |
Power indicator LED per power source | Functional | Covered | Done |
REQ-014 |
N-Top module connector | Interface | Covered | Done |
REQ-015 |
SO-DIMM module connector | Interface | Covered | Done |
REQ-016 |
M2 module connector | Interface | Covered | Done |
REQ-017 |
Com-Top (regular) module connector | Interface | Covered | Done |
REQ-018 |
Com-Top (mini) module connector | Interface | Covered | Done |
REQ-019 |
FTDI USB-Serial interface with correct pull configuration | Interface | Covered | Done |
REQ-020 |
I2C bus routing via manual pin-strap | Functional | Covered | Not Started |
REQ-021 |
Accordion A2 DAQ interface | Interface | Covered | Done |