The Hardware Design Process

Hardware design is rarely a single pass from idea to working chip. Engineers move through a repeating process: define specifications for the intended behavior, produce an initial design that should meet them, run design verification to check the design against the specification, build a prototype implementation, and test it before trusting it in real hardware.

Each pass is small and verifiable. A specification can be as compact as a truth table; an initial design is a first pass at the circuit's structure; design verification runs that design and reports what actually happens. When the result does not match the specification, the discipline is to check whether the mismatch is minor (make corrections and retest) or major (redesign from the initial design) — never to rewrite the specification to fit whatever the design already does.

Every lesson in this course practices a fast, simulation-only pass through this same process: write a specification, describe a circuit in Verilog, run design verification against a supplied checker, and fix what does not match before calling the result done.

Proof is design verification's saved output, and the word is used the same way everywhere in SkillLift: the saved, checkable record of what you claimed and what the tools actually reported. It is not a feeling of confidence and not a grade someone gave you — it is an artifact another person can open and check.