Peer review procedures
- There will be regular code walkthroughs. They will be performed at
least once per each loop through the spiral model, and will be performed
in a circular fashion, (i-th developer will review i+1-th developer's
code). All deficiencies will be noted and used to improve the process.
- During each code walkthrough, two categories of measurements will be
taken (and deficiencies removed): relative and objective.
Relative deficiencies are: code efficiency (how few resources are consumed),
code accuracy (how close the given product comes to the given
specifications).
Objective deficiencies are: errors in formatting, non-standard variable
names, lack of inline documentation, and coding standards (such as
deallocation of all allocated memory).
- A checklist will be used during code
walkthroughs.
- Note: Should the full walkthough procedure be deemed not necessary by
the assembled managers, a shortened review session will be employed. In
the shortened session, each programmer will go through a representative
method/class with the rest of the programming team, answering and asking
questions about the code. Each programmer will then fix deficiencies
noted either before (critical errors) or after (non-critical errors) the
release date.
The notes of the last partial walkthough are here.
|