CS 402

Peer Evaluation 25%

Team members will give a numeric evaluation for all members on their team, including themselves, using the webpage for the class. There is also space to make additional comments to reflect the contributions of each member. Finally, each member should tell how a total of (10*number of team members) points should be distributed. For example, if a team has 4 members, they should distribute 40 points among the members. If everyone participated the same amount, each would get 10. If not, one might get 15, another 12, another 8, and the other 5, making a total of 40.

Documentation 30%

User Guide

Complete instructions for a user of the software should be given. This may be a combination of on-line help and a paper document. Included with this guide should be steps needed to start the system. In some cases this will mean installation instructions, while in other cases, it will mean telling what website to go to, and/or how to get a password for using the system.

Programmer’s Guide

Everything necessary for programmers who must maintain the system should be included. The code itself is part of this. There should definitely be a graphical description of the system design to show how the components relate to each other. To tell whether you have adequate documentation, assume that you need to make an addition or modification to the software. Examine the documentation to see whether it is adequate for finding which components must be worked on to effect the required modification.

Test Plan 15%

Each team should give a detailed description of their test plan. This should include an explanation of why the test plan is adequate (what classes of data are tested) and what test data have been used.

Correct Working Program 30%

Each team will demonstrate what their program does. They should give some convincing arguments as to why they believe their program is correct. Be sure to talk about verification and validation.