15.07.2013 Views

Software Project Management Plan (SPMP) - Southern Polytechnic ...

Software Project Management Plan (SPMP) - Southern Polytechnic ...

Software Project Management Plan (SPMP) - Southern Polytechnic ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Appendix C: Code Review Checklist<br />

Page 49 of 60<br />

Test <strong>Management</strong> Tool (TMT)<br />

<strong>Software</strong> <strong>Project</strong> <strong>Management</strong> <strong>Plan</strong> (<strong>SPMP</strong>)<br />

TMT-<strong>SPMP</strong>-1.2<br />

27-Sep-2010<br />

Use this symbol to check and use this to uncheck.<br />

Author:<br />

Moderator:<br />

Date:<br />

Purpose:<br />

Review code considerations:<br />

Is the code complete?<br />

Does it promote information hiding and reuse?<br />

Is it highly cohesive/loosely coupled?<br />

<br />

<br />

<br />

Does the data item meet standards?<br />

Has persistent data been considered in code?<br />

Can it be changed without excessive impact on other items?<br />

Have approved methods been followed?<br />

Does documentation conform to standards?<br />

Does it compile cleanly?<br />

Review auto-generated code:<br />

<br />

Is the code work product is too-generated output, does this output pass the<br />

tool’s syntactic and semantic checks?<br />

Does it compile cleanly?<br />

Review interfaces:<br />

<br />

<br />

<br />

Are the interfaces specified?<br />

Are the interfaces sufficient?<br />

Are they consistent with the interfaces capture in the requirements and design?<br />

Review prologue/comments:<br />

<br />

<br />

<br />

Are comments meaningful and accurate?<br />

Are special cases/conditions described?<br />

Is all code marking requirements satisfied?<br />

Review source product completeness:<br />

<br />

<br />

<br />

Are the current requirements and design correct?<br />

Are all requirements and design aspects addressed by the code?<br />

Are there any open action items that might affect the code?<br />

Review coding standards:<br />

<br />

<br />

<br />

Has the approved method been followed?<br />

Does the documentation conform to standards?<br />

Does the code meet defined standards?<br />

Review traceability:<br />

<br />

Is each item in the code directly traceable to one or more items in the<br />

requirements and design?<br />

Has this traceability been captured in the coding according to standards?

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!