Software Engineering -- CS511
Boston University -- Fall 2001

Grading Method

Individual Grade

20% -- Class preparation (10 short quizes)
20% -- Mid-term exam
20% -- Final exam
10% -- Your part of team project

Team Grade

5% -- Class presentation
5% -- Project management and functional specification
5% -- Installation, user guide, reference
5% -- Test plan and testing
10% -- Technical specification and executable program

Notes

Many parts of the class will graded on a scale of 0 to 10. Here is what those grades mean...

0 to 6 -- Assignment not complete or completed with unacceptable quality.

7 -- Assignment is complete with minimally acceptable scope and quality.

8 -- Assignment is complete with good scope and quality. This will be the average grade for people who work hard.

9 -- Assignment is completed in an excellent manner. All aspects are very well-done, with no significant weaknesses.

10 -- Assignment is completed in an outstanding manner. All aspects are of top quality, with no weaknesses. Beyond what would be expected in this course. 

I will be as fair and objective as possible in grading all class tests and assignments. I will keep an eye on the grades given by the graders and work with them to be fair. Having said that, you should be aware that there is inherent subjectivity in most of the course grading. The quality of a spoken presentation, a user manual, or a block of code involves subjective judgment.

In general, I will be tough on grading throughout the course, then curve up the final grades if necessary. I will attempt to meet the university guideline of B- as the average grade. 

You are expected to read the class web site completely and keep up with the Announcements page. Items posted on the web site may affect your grade.

Copyright 2001 Charles H. Connell Jr.