ExpertQuestion 6 of 10Source page 17

Why might the globally worst-WNS scenario not be enough, by itself, to decide which views can be removed from a signoff plan?

From PDVerse MMMC Interview Masterclass, part of the pdVerse Mentor Series

Direct answer

Different analysis views have different critical paths. The worst-WNS scenario may constrain the high-speed functional datapath, while another scenario with lower WNS may be the only view that exercises scan test chains, asynchronous interfaces, or low-power retention paths.

Technical Reference DiagramWhy might the globally worst-WNS scenario not be enough, by itself, to decide which views can be removed from a signoff plan?

Mentor explanation

Signoff coverage requires checking all unique path endpoints, not just the single worst WNS.

Key terms

  • Path dominance vs WNS โ€” a view with small WNS can be the dominant and only constraint for a specific sub-block or test mode.
  • Endpoint coverage matrix โ€” auditing that every timing endpoint is constrained across its worst operating condition.
  • Asymmetric datapath activation โ€” test modes and low-power modes activate logic paths that are completely inactive during functional mode.

Removing a view based purely on a WNS ranking table leaves unique mode-specific paths completely unverified, risking silicon failure.

Practical example

Dominance Migration Example:

Baseline Run:
  โ€ข View 1 (func_ss_125c_rcmax): WNS = -150 ps (Rank 1 - Worst)
  โ€ข View 2 (func_ss_m40c_cmax):  WNS = -40 ps  (Rank 2)
  โ€ข View 3 (scan_ff_m40c_rcmin): WNS = -15 ps  (Rank 3 - Hold Only)

After fixing ALU paths in View 1:
  โ€ข View 1 WNS -> +10 ps (Clean)
  โ€ข View 2 WNS -> -40 ps (Now the new failing critical limiter!)
  โ€ข If View 2 had been pruned based on baseline ranking, this failure would be missed!

Interview trap

Pruning signoff views based exclusively on a WNS ranking table. A view with minor WNS may be the only view testing critical test-mode or interface paths.

Key takeaways

  • WNS only reflects the single worst path at a specific design snapshot.
  • Different views cover unique clock domains, test modes, and endpoint populations.
  • Optimizing the worst path causes secondary views to become the new critical limiters (dominance migration).
Self-check: can you answer this aloud?

Try a 45-second answer using this structure:

  1. State the direct answer.
  2. Explain the timing or physical reason.
  3. Name one caveat.
  4. Say how you would verify it in a real flow.

MMMC Signoff Guide

Explore the full 10-chapter MMMC guide on modes, PVT corners, RC parasitics, analysis views, and correlation between implementation and signoff tools.

Offline PDF Bundle

Want all 1109 questions offline?

Get the complete 4-book PDF bundle (PnR, STA, MMMC, Low Power) with a clickable table of contents - no ads, no internet needed.

See what's inside the bundle
Timing Constraints (SDC) Handbook โ€” nine chaptersSDC ConstraintsNine chapters on clocks, exceptions, and constraint linting.