|
Review Design and Cells in Context
Review the Design, library state, cell(s) and cell hierarchy against the intent in the CR. This can be achieved in
various ways but the parties refer to the CR and the updates to evaluate completeness. The aim is decide on either
additional changes or a “ready for release” agreement. In rare cases, if significant difficulties arise then work may
be halted pending some additional expert input.
Remote screen sharing, remote view or by providing library and deign tool access to the Design Authority to navigate
and view the cell within its context.
|
Approve as Ready for Release (optional)
| Depending on the process it can be used to mark as ready for release, pending grouping of multiple cells into one later
library release. It is possible for this to be an option on the CR through a modified template; otherwise a comment can be
added to the CR. This may be done progressively as different colleagues contribute to review or issues are progressively
closed. |
Reject for Rework (optional)
| Depending on the process it can be possible to mark as rejected. It is possible for this to be an option on the CR through
a modified template, otherwise a comment can be added to the CR. |
Request a Formal Design Review (optional)
| Depending on the scale and criticality of change a structured multi-party design review may be needed prior to commitment
of the design and its libraries for release. This would be arranged through a specific work item. Decorated with the
relevant library information calling for the required participants. |
Make Updates (optional)
| Updates may be made to the cell(s) or CR during the review. The design review records should note this with before and
after states being saved if necessary. |
Update the Change Request and Review Record
| Update the CR to reflect completion of the review and any additional information used within the review or produced by it.
Complete CR approvals if these are being used. |
|
