CS 407 Software Engineering II: Spring 2000
Evaluation Scheme

                        Course Evaluation                                     Team Project Evaluation and Due Dates

Homeworks
Lab Assignments		 5% Weekly presentations       Evaluation Meeting Minutes format 10%
Midterm Examination
 		 10% Revised Design document (Version 0.8:  2/10, Version 0.9: 2/24, Version 1.0: 3/2) 10%
Team Project 70% Final Project Report : Includes Requirements, Design, User Manual, Glossory,and Appendices containing complexity information on components of the product and controbutions of individual team members. On line help is required and must match the User Manual. Version 0.9: 3/30, Version 1.0: 4/24) 15%
Final Examination 15% Final Presentation and Demo 35%
TOTAL 100% TOTAL 70%
                           All project related documents must be available on the team's WEB site by 10am on the specified due date.
                          Homeworks are to be worked on and submitted individually. Lab assignments are to be worked on by team
                          members and submitted by the Team Leader. Final examination and the midterm will include questions related
                          to homeowrks and lab assignments.
 
All members of a team are exepected to contribute equally to the progress made by that team. Lack of participation in team meetings, inability to meet individual deadlines, and non-cooperation will result in severe grade penalities. There is no guarantee that all members of a team will get the same grade. Every member of a team will be graded individually based on his/her contributions towards the progress made by that team.

BACK TO CS407 HOMEPAGE
BACK TO PROJECT
COURSE GRADE DETERMINATION
 
 

  Last revised: December 28, 1999

 
 
 

Grading of the Prototype 

1. Prototype:     50% (How well it meets the requirements)
2. Presentation: 20% 
3. Design:         30% 

Note: 

1. Rehearse the presentation; it is suggested that one person do the talking and the other work on the laptop. Coordination between these two persons is cdrucial for the success of the presentation. No points will be deducted for any network or machine related problems that might crop up during the presentation.

3. Using one or two slides explain, very briefly, the correspondance between your system and the design of the prototype.

4. At the outset make it very clear what you are going to demonstrate, what features are in the prototype, and what features are not in it.

 

BACK TO CS406 HOMEPAGE
BACK TO PROJECT