STA Mastery · All levels
View Mismatch Triage: Review Checklist
Review Checklist for View Mismatch Triage.
Review checklist
Review Checklist for View Mismatch Triage focuses on slack delta between views, SPEF tag mismatch count. 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 owner, extraction owner, CAD owner.
Sign-off ownership
OWNERSHIP MAP — View Mismatch Triage
artifact owner
---------------- -----------------
timing report STA owner
SDC/constraint extraction owner
implementation CAD owner
Every WNS cluster needs a named owner before ECO.STA deep dive
Debug hygiene separates senior STA leads from report readers.
Concept diagram
DEBUG ORDER
1. same tags? 2. constraints? 3. view? 4. real path? 5. ECOMetric graph
ROOT CAUSE MIX (typical)
constraint bugs ████████ 35%
view mismatch ██████ 25%
real path ██████ 25%
methodology ████ 15%Reports and artifacts
run manifest
SDC diff
SPEF tag
scenario isolation
Mini case study
Mystery regression: SPEF corner tag typo in run script — not a design bug.
Debug branches
Manifest every run
War room by path group
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
Different SPEF, RC corners, or parasitic modes between runs explain apparent regressions without any design change.
Metric: slack delta between views, SPEF tag mismatch count