Abstract
In assessing software development projects, we want to assess a range of characteristics of the finished product. These include the design, the code, and possibly of the process used. How does providing a grade for each of the desired characteristics compare with a setting a minimal standard for each characteristic? The holistic assessment strategy is discussed and compared to grading of the parts, each characteristic, independently. In doing so, we contend that the assessing by summing the parts is not equal to assessing the whole.
| Original language | English |
|---|---|
| Title of host publication | Proceedings of the seventeenth annual conference of the National Advisory Committee on Computing Qualifications |
| Place of Publication | New Zealand |
| Publisher | National Advisory Committee on Computing Qualifications |
| Pages | 440 |
| Number of pages | 445 |
| Publication status | Published - 2004 |