A specification says what the chip must do; a budget says what each part may spend doing it. Between the two sits the integrator's most leveraged work: converting every paragraph of the specification into a constraint with an owner and a number, finding the paragraphs that convert into nothing, and proving the numbers add up before anyone writes RTL. This topic teaches that conversion on NanoSoC, ending in a full requirement-to-budget trace that the rest of the course spends.
Lesson | After it you can... |
|---|---|
Convert a requirement into a constraint, a budget and an owner. | |
Find the untestable sentence and rewrite it as a checkable claim. | |
Walk the full trace from requirements to power, area, bandwidth and boot time. |
Suggested order: top to bottom. The method, then the hunting, then the trace that uses both. The trace is the reference the later sections draw on: when a lesson quotes 82.74 mW or 12.581 ms, this is where the number was earned.
A number, a condition and an owner: how many milliseconds, measured from what event to what event, under which image size, and who signs the measurement.