STA Mastery · All levels
Path Group Prioritization: Review Checklist
Review Checklist for Path Group Prioritization.
Review checklist
Review Checklist for Path Group Prioritization focuses on WNS by path group, reg2reg vs in2reg vs reg2out slack. The goal is to connect the observable symptom to timing mechanism, ownership, and regression risk.
SDC revision and implemented clock/exception policy are named.
Clock/reset and CDC assumptions are reviewed.
Path groups, IO delays, and exception rationale are documented.
MMMC scenario list maps back to signoff requirements.
WNS/TNS artifact stored with corner/mode/view tags.
Owners signed: STA lead, synthesis owner, PD owner.
Sign-off ownership
OWNERSHIP MAP — Path Group Prioritization
artifact owner
---------------- -----------------
timing report STA lead
SDC/constraint synthesis owner
implementation PD owner
Every WNS cluster needs a named owner before ECO.STA deep dive
Slack is a path story — read the graph, not just the number.
Concept diagram
TIMING GRAPH
FF --cell-- logic --net-- logic --cell-- FF
launch captureMetric graph
SLACK TAIL
paths | ***
| *******
|********* <- fix WNS firstReports and artifacts
WNS/TNS
path slack histogram
cell vs net %
path group summary
Mini case study
WNS -90ps but 80% net delay on one congested route — PD route fix beat upsizing three cells.
Debug branches
Cell-heavy -> sizing/VT
Net-heavy -> route/layer
Check launch/capture clocks
Senior review question
Ask: what corner/mode/view proves this topic is closed or failing?
Key takeaways
State corner, mode, view, and database tag with every slack claim.
Run setup and hold plus MMMC regression after every ECO.
Common pitfalls
Comparing STA runs with different SPEF or SDC tags.
Broad false_path to green-wash violations.
Setup-only ECO without hold check.
Principal STA review addendum
Path groups classify timing intent so optimization and debug focus on the paths that matter for signoff and product modes.
Metric: WNS by path group, reg2reg vs in2reg vs reg2out slack