DenseChip

SoC Integration · All levels

Abstract Models (LEF/DEF/Timing): Step-by-Step Walkthrough

Step-by-Step Walkthrough for Abstract Models (LEF/DEF/Timing).

Step-by-step analysis walkthrough

Use when you own Abstract Models (LEF/DEF/Timing) in a top-level integration review.

  1. Open latest integration baseline and manifest.

  2. Inspect failing metric by domain.

  3. Trace first failing contract boundary.

  4. Collect artifacts and assign single-thread owner.

  5. Define minimal proof experiment.

  6. Apply smallest reversible fix.

  7. Run focused check then full regression.

  8. Update dashboard and governance log.

  9. Decide: close, waive with expiry, or escalate.

  10. Publish final review memo.

Artifacts to collect

  • abstract model manifest, LEF/DEF consistency report, timing-model diff

  • baseline manifest

  • owner matrix

  • regression summary

  • risk memo

Decision memo template

diagram
SOC DECISION MEMO — Abstract Models (LEF/DEF/Timing)
baseline:
metric:
root cause:
fix:
residual risk:
owners: PD owner, IP physical owner, STA owner

Reference visuals

Abstract model layering

diagram
ABSTRACT MODEL LAYERS

logical model  <-> timing model <-> physical abstract (LEF/DEF)
must remain version-aligned at every integration cut.

SoC deep dive

IP handoff quality and version governance drive integration velocity.

Concept diagram

diagram
IP HANDOFF PIPELINE
IP package -> baseline lock -> integration build -> bring-up

Metric graph

diagram
INTEGRATION CHURN
collateral gaps ██████
version drift █████
real logic bugs ███

Reports and artifacts

  • handoff completeness score

  • manifest diff report

  • model mismatch log

  • bring-up issue tracker

Mini case study

Most top-level debug time was spent on collateral drift, not RTL defects.

Debug branches

  • Validate handoff checklist

  • Lock manifest hashes

  • Correlate issue to owner boundary

Senior review question

Ask: what baseline, owner, and artifact prove this topic is truly closed?

Key takeaways

  • State baseline manifest and owner with every closure metric.

  • Run cross-domain regression after every top-level fix.

Common pitfalls

  • Comparing results across different manifests.

  • Unowned issues slipping through review cycles.

  • Waiving risks without expiry and validation plan.

Principal SoC review addendum

Top-level integration relies on abstract views (timing, physical, power) that must remain aligned with evolving implementation details.

Metric: abstract-model mismatch defects, floorplan integration churn

Practice this lesson