1

Verify Quality

• Ensure that the design is testable. Does it build code that cannot be verified or validated in a reasonable manner? If so, there is no way to ensure the quality of the code and the design must be reworked.
• Examine the design documents for problems that will lead to coding errors. Look for incorrect interface descriptions, design mistakes, or naming confusion.
• Compare the design documents against existing criteria such as operator interface standards, safety standards, production constraints, design tolerances, or parts standards.
• Create bug work items describing any flaws found in the design documents. Assign them to the responsible developer.

2

Verify Extensibility

• Ensure that the design is written so it can be extended if it is the intention to do so, or reused in other areas of the product.

3

Verify Security

• Check the design for the protection of assets, privilege levels, and the use of data at entry points. For more information, check MSDN for practices relating to security for your application type.<TBD: Tie into security activity when available><TBD: Add redirector link to MSDN security info>

4

Create Review Work Item

• A review work item is created documenting the results of the design review. The review team must decide on the next steps for the design depending on the magnitude of the changes necessary.
• If no changes are necessary, document this fact in the review work item and that coding can begin on the design.
• If minor changes are necessary, mark the review work item as Accepted with changes which indicates that coding can begin once the minor changes are implemented in the design.
• If major changes are necessary, mark the review work item as Rejected. The design must be reworked, and another design review must be performed before coding can begin on the design.

A review work item is created capturing the decisions and problems discovered during the review.

Bug work items are created for any flaws found in the design that must be fixed.