Skip to content
DenseChip
Learn
PracticeCode labInterview

DenseChip

Navigate

Menu

LearnPracticeCode labInterview

Tools

All toolsSV editorCode repoResume
DenseChip

Practice, courses, and chip-design tools in one focused workspace.

LearnPracticeCode labInterviewToolsLearning paths

© 2026 DenseChip

AboutRoadmapCareersInternshipsFAQContactPrivacyTerms
Skip to lesson

Course contents

  • How to Use This Course
  • The NanoSoC Tour
  • Reading Path
  • SoC Glossary10
  • SoC Metrics Reference
  • SoC Cheatsheet
  • What SoC Integration Is12
  • Architecture and Budgets21
    • Partitioning and Hierarchy
    • Area Budgets
    • Timing Budgets Across Hierarchy
    • Power Budgets
    • Bandwidth Budgets
    • Budget Governance
      • Contracts with Owners
      • Margin Burn-Down
      • Budget-Change Process
    • Multi-Die and Chiplet View
  • Memory Maps and Address Decode26
  • Interconnect and Bus Fabrics26
  • Clock and Reset Architecture24
  • Power Architecture21
  • Interrupts, DMA and Peripherals15
  • Memories, Boot and Security21
  • IP Integration and Handoff21
  • Top-Level Verification and Bring-up21
  • Package, Pads and I/O18
  • Chip Signoff and Tapeout18
  • SoC Interview Prep16
  • Capstone: Integrate NanoSoC14
Loading lesson

←Architecture and Budgets
  1. Topics
  2. SoC Design
  3. Architecture and Budgets
  4. Budget Governance

Part 2 of 14Part 2 of 14/Architecture and BudgetsAll levels

Budget Governance

Contracts, margin burn-down over the project, escalation, and the budget-change process.

  • 3topics
  • 3lessons

Budgets decay. Every block spends a little more than planned, every estimate sharpens upward, and without governance the project discovers at tapeout that the die, the package and the schedule no longer agree. This topic teaches the machinery that stops that: budget tables with named owners, margin tracked as it burns down, a defined escalation when a budget breaks, and a change process that keeps the books balanced. For the negotiation side see Budget Negotiation; for signoff criteria see Architecture Signoff.

Lesson

After it you can...

Contracts with Owners

Write a budget table where every row has an owner and a number.

Margin Burn-Down

Track margin over the project and read the burn-down.

Budget-Change Process

Run an escalation and a budget change without breaking the books.

Suggested order: top to bottom. Write the contract, track it, then change it by the rules. This topic assumes at least one budget topic read first; its examples draw on area, power and bandwidth alike.

Check yourself What makes a budget a contract rather than a target?

An owner who signed it, a margin policy that bounds misses, and a change process that records every move. A number without those is a wish.

Expect a scenario: your block is 10% over with a month to go. Answer with the escalation order: cover (trades and restructuring), margin spend, replan, escalate with data — and say who decides each.

PreviousNext: Contracts with Owners

Up next

Up nextContracts with Owners

Sign in to save progress

Practice this lessonPrevious lessonReport an error

See also

  • Partitioning and Hierarchy
  • Area Budgets
  • Timing Budgets Across Hierarchy