Development Code Reviews

Development QC Process

Code reviews are in place for the EPOD projects and must be followed.

Warning: The following is the old process. The new process requires the use of TFS and is documented separately.

The Supimix log must be referred to the Product Development Manager for assignation to a peer for review.

When assigned, the development will be reviewed for:

• Technical issues
• Adherence to standards in:
  • Modified Code
  • Existing Code (may be deferred)

A QC Document will be created for each module modified as part of this change, in the format as per the example P:\Product\EPOD\Procedure\EPOD .Net Development Guide & Process\Dev QC document example\312147 - Lanemark QC.doc.

QC review documents with any outstanding issues will be placed in an appropriately-named folder within the following folder: P:\Product\EPOD\_Development\QC Documents\Prog QC\.

For example: P:\Product\EPOD\_Development\QC Documents\Prog QC\324491 - Use auto-update to refresh load data for existing load

Any issues with code should be passed back to the developer, referencing the QC documents created. Any further changes will be reviewed again following this process.

If all code passes QC review at any time, the QC folder for this change will be moved to the following directory: P:\Product\EPOD\_Development\QC Documents\Prog QC\# Closed\.

If any changes are deferred and/or raised as another Supimix log for completion, the QC folder for this change will be moved to the following directory: P:\Product\EPOD\_Development\QC Documents\Prog QC\# Deferred (Passed)\.