Change control and governance run across every chip lifecycle. Each flow here shows who takes part, the steps and decisions as a diagram, the records it produces, how impact is judged, who may approve what, and where it applies in each lifecycle, with a procedure document to read or download.
How a change to anything already baselined is requested, assessed, approved, made and closed: change requests, specification change after freeze, engineering change orders before and after tape-out, waivers, errata, customer notices, and new IP, PDK or tool versions.
The common front door for any change to something that has been baselined: a specification, a design database, a test program, a package drawing, a process recipe or a released document. A change request records what is to change and why, the owners of every affected area assess the impact, and a change board approves, rejects or defers it before anyone edits the baseline. It starts as soon as a frozen item needs to change, whoever spots the need.
How a requirement or specification is changed once it has been frozen at a gate. The change is traced to every requirement, interface, design block and test it touches, judged against the frozen interfaces and safety requirements, and approved at the level that matches its reach. The specification is then reissued as a new controlled version and every downstream plan is brought into line.
18 more flows for registered members.
The full lifecycle detail, with its charts, flows, tables and every section, is for registered members. Registration is free and takes a minute. You come back to this page afterwards.