A block without its collateral is a netlist with a rumour attached. This topic lists everything a delivery must contain across RTL, constraints, power intent, verification and documentation, then versions it so that a redelivery is a decision rather than a surprise, and ends at the acceptance gate where the integrator either takes ownership or sends the block back. The automated-assembly side of this story, generating the top level from one description, is taught in the memory-maps part of the course; here is the collateral side: what the description must point at and what must arrive beside it.
Lesson | After it you can... |
|---|---|
Name the full cross-discipline delivery list and run the completeness checker. | |
Judge whether a version bump is safe to absorb and what it invalidates. | |
Score a delivery, grant or refuse acceptance, and age waivers honestly. |
Suggested order: top to bottom. The list first, because versioning versions the list; then change control, which is versioning under time pressure; then the gate, which enforces both. For the physical side of a hard-macro delivery see Macro Abstracts and IP Handoff with its IP Handoff Checklist.
The checklist asks whether everything arrived; the gate asks whether it is good enough to own. A complete delivery can still be refused when its collateral contradicts itself or its verification evidence does not cover the configuration used.