DenseChip

DFT / ATPG ยท All levels

Scenario: Coverage Storm

DFT Interview Prep: Coverage crises require separating true untestable faults from constraint/model issues and choosing the smallest high-impact closure plan.

What this topic teaches

Scenario: Coverage Storm turns DFT intent into measurable release confidence. Coverage crises require separating true untestable faults from constraint/model issues and choosing the smallest high-impact closure plan. The senior challenge is proving whether a metric move came from real quality gain, setup drift, or hidden regression.

The senior-engineer question

When coverage shortfall under schedule pressure, pattern growth slope moves, can you identify mechanism, evidence quality, owner, and the minimum safe next action?

diagram
DFT CLOSURE FLOW - Scenario: Coverage Storm

scan/test architecture
        |
        v
ATPG constraints + fault models
        |
        v
pattern generation + compression
        |
        v
timing/power/physical validation
        |
        v
silicon diagnosis and release signoff

Debug rule: always state metric, run tags, and owning team with any claim.

Picture the closure flow

Draw the causal flow before opening tools. Use these diagrams to anchor architecture, constraints, and silicon behavior discussions.

Coverage crisis triage

diagram
coverage gap
  -> untestable? constraint? model?
  -> targeted fixes
  -> pattern budget check

Process sequence

diagram
DFT FLOW - Scenario: Coverage Storm

scan insertion -> chain stitch -> compression map -> ATPG -> tester apply -> diagnosis
      |                |                |            |             |
 controllability   shift balance    channel use   coverage     silicon correlation

Primary metric: coverage shortfall under schedule pressure, pattern growth slope

Ownership layers

diagram
DFT OWNERSHIP LAYERS - Scenario: Coverage Storm

layer              owns                         failure mode
----------------   --------------------------   -------------------------
rtl/architecture   scanability hooks            uncontrollable logic
atpg/constraints   legal pattern intent         aborts, low coverage
physical/clocking  chain route + test clocks    shift hold/timing escapes
tester/program     pattern apply integrity      false binning / bad fails
quality signoff    release criteria             escapes or schedule slip

Evidence to collect

  • Primary metric: coverage shortfall under schedule pressure, pattern growth slope.

  • Primary artifact: coverage gap snapshot, fault bucket analysis, closure plan.

  • Owners to bring into review: ATPG owner, DFT lead, product quality owner.

  • One failing signature and one reduced reproduction path.

  • Exact run tags for constraints, patterns, and tester program.

Ownership map

diagram
OWNERSHIP MAP - Scenario: Coverage Storm

artifact              owner
----------------      -----------------
architecture/report ATPG owner
constraints/setup   DFT lead
physical/test       product quality owner

Name an owner for each failing metric cluster.

Subpages in this topic

Each topic includes mechanism, inputs/outputs, reports, debug, worked example, pitfalls, interview, checklist, theory, design space, expanded case study, walkthrough, comparison matrix, software view, and silicon impact.

Key takeaways

  • State metric and run tags with every claim.

  • Connect every fix to a regression matrix.

  • Treat quality, timing, and power as coupled.

Common pitfalls

  • Coverage-centric decisions without legality checks.

  • Pattern changes without tester correlation.

  • Release calls without owner signoff.

DFT deep dive

Senior DFT interviews test tradeoff judgment under imperfect data.

Concept diagram

diagram
INTERVIEW ANSWER LOOP

state metric -> explain mechanism -> request evidence -> propose fix -> list regression

Metric graph

diagram
ANSWER QUALITY

mechanism clarity + ownership clarity + regression discipline

Reports and artifacts

  • whiteboard rubric

  • scenario scorecard

  • trap checklist

  • follow-up depth index

Mini case study

Candidate improved from tool-only answers to mechanism-first narratives by using metric->artifact->decision template.

Debug branches

  • Always state assumptions

  • Name cross-team owners

  • Discuss risk and fallback plan

Senior review question

Ask: what evidence proves this DFT decision is safe for production?

Key takeaways

  • State metric, lot/corner context, and pattern tag with every claim.

  • Treat timing, power, and quality as one signoff problem.

Common pitfalls

  • Chasing coverage without legality checks.

  • Ignoring test-power side effects of pattern changes.

  • Debugging silicon without reproducible tags.

Practice this lesson