| Code Printout | 30 marks
|
|---|
| How clearly the code is written | 5
|
| Good variable and subroutine naming | 5
|
| Good comments on methods, classes, files, in-code | 5
|
| Clarity of small-scale coding constructs | 5
|
| Good design into classes and/or subroutines | 5
|
| Appropriate architecture | 5
|
| Release Plan | 30 marks
|
|---|
| Is the date section present and correct? | 5
|
| Is the status summary complete and correct? | 5
|
| Are work factors appropriately estimated, justified, and adding up? | 5
|
| Are features assigned to coders and have reasonable estimates? | 5
|
| Are features well chosen? | 5
|
| Are features divided into A and B sets appropriately | 5
|
| Specification | 40 marks
|
|---|
| Does the spec give sufficient background on the feature? | 10
|
| Does the spec explain the behavior of the feature? | 10
|
| Does the spec give enough info on the UI to code from? | 10
|
| Is there an explanation of the feature sizing and is it reasonable? | 10
|
| (if number of features spec'd is unusually low, scale back proportionately)
|