431 Fall 2004 Evaluation Criteria for Final Demonstration
Section: Date:
Team:
Starting Time:
Specific Criteria:	Quality Points 1-5*	Comments:
1. Exhibit knowledge of the subject matter in an organized fashion including an introduction with purpose and objectives to capture audience’s attention.
2. The body of the presentation should flow in a logical sequential order, highlighting the main points.
3. Effective verbal communication should include clarity of voice, proper grammar, eye contact, expression in voice and talking to the group; rather than reading a script.
4. PP slides should be used to develop presentation, to pique audience attention and provide a clear understanding of subject matter
5. Team Responsibilities were clearly stated.
6. Effectively were able to answer/handle questions.
7. Software Engineering Topics. See table below
8. At the end of presentation, a summary and conclusion should be given to highlight main points.
9. Prototype demonstration
10. CD submitted
11. Ending Time
Other (e.g., O-O implementation)

1 = poor, 5 = excellent

Table 1. Software Engineering Terms Per Team
Section 501 (12/02/04)	Section 502 (12/01/04)	Section 503 (11/29/04)
Team 501-1 * Design rationale capture * V&V	Team 502-1 * Software configuration management * V&V	Team 503-1 * Cost estimation * V&V
Team 501-2 * Software development environment CASE * Management (plan, estimate, scheduling)	Team 502-2 * White box/black box testing * Management (plan, estimate, scheduling)	Team 503-2 * Life cycle model * Management (plan, estimate, scheduling)
Team 501-3 * Requirements * V&V	Team 502-3 * Automated software development - AP * V&V	Team 503-3 * Visibility * V&V
Team 501-4 * Product, Process, People, Project * Management (plan, estimate, scheduling)	Team 502-4 * Scale-up * Management (plan, estimate, scheduling)	Team 503-4 * Iterative * Management (plan, estimate, scheduling)