CDC / RDC · All levels

CDC Tool Flow: Review Checklist

Review Checklist for CDC Tool Flow.

Review checklist

Review Checklist for CDC Tool Flow focuses on analysis runtime, violation classification completeness, delta noise between runs. The goal is to convert issue observations into mechanism-backed closure decisions.

Crossing and reset intent are explicitly classified.
Protocol assumptions are documented and checked.
Critical issues have owners and dates.
Waivers include mechanism, containment, and expiry.
Regression matrix includes stress and milestone modes.
Owners signed: CDC lead, CAD owner, verification owner.

Signoff ownership

diagram

OWNERSHIP MAP — CDC Tool Flow

artifact                  owner
----------------------    -------------------------
design intent           CDC lead
verification evidence   CAD owner
signoff decision        verification owner

Every open CDC/RDC issue needs one accountable owner before waiver or fix.

CDC/RDC deep dive

Signoff is an evidence governance problem across teams.

Concept diagram

diagram

CDC SIGNOFF LOOP

analysis -> triage -> fix/waive -> review gate -> dashboard

Metric graph

diagram

CRITICAL OPEN COUNT

week1 34
week2 22
week3 10
week4 0

Reports and artifacts

critical by owner
waiver quality
review gate status
closure trend

Mini case study

Pass rates improved while critical waivers aged out of policy; dashboard exposed hidden risk.

Debug branches

Separate quality from quantity metrics
enforce waiver expiry
run gate checklists consistently

Senior review question

Ask: what evidence proves this risk is closed for silicon, not just tool-clean?

Key takeaways

State crossing class, assumptions, and owner with every issue.
Run structural and dynamic regressions after each fix.

Common pitfalls

Treating all warnings as equivalent risk.
Waiving issues without containment evidence.
Skipping reset and reconvergence stress after CDC fixes.

Principal CDC/RDC review addendum

Robust CDC signoff combines structural analysis, protocol checks, reset analysis, and targeted formal/simulation evidence with consistent setup tagging.

Metric: analysis runtime, violation classification completeness, delta noise between runs

Practice this lesson