CS 330 Software Engineering

There will be two grading schema, with your grade being the maximum of the two. The following is the anticipated assignments and grading. If because of unforeseen scheduling issues an item removed, its weighting will be spread proportionally amount the rest of the items.

Homework weighted grading	Activity	Original Weight	Revised Weight
	Midterm	15%	20%
	Final	20%	26%
	Graded Hw (essay/Mozilla install)	6%	3%
	Quizes	9%	4%
	Online/Debugging exam	4%
	Maintenance Team Initial Report	4%	5%
	Maintenance Team Final Report	5%
	Requirements team Initial (req doc)	4%	6%
	Requirement final doc	5%	7%
	SQA #1 team grade	3%	5%
	Specification Team Initial Report	3%
	Specification Team Final Report	5%
	SQA #2 team grade	3%
	Design Team Initial Report	4%	8%
	Design Team Final Report	5%	8%
	SQA #3 team grade	3%	4%
	Class participation (2 grades 1% each)	2%	4%
	Under this opinion who have an B or better before the final have the choice of not taking the final (and having its its weight spread out)
Exam weighted grading	Activity	Original Weight	Revised Weight
	Midterm	25%	28%
	Final	35%	40%
	Online/Debugging exam	4%
	Maintenance Team Initial Report	2%	4%
	Maintenance Team Final Report	3%
	Requirements team Initial (req doc)	2%	3%
	Requirement final doc	4%	5%
	SQA #1 team grade	2%	4%
	Specification Team Initial Report	2%
	Specification Team Final Report	3%
	SQA #2 team grade	2%
	Design Team Initial Report	2%	4%
	Design Team Final Report	4%	6%
	SQA #3 team grade	2%	4%
	Class participation (2 grades 4% each)	8%	8%

Each assignment/exam/team will be graded on a curve, and for each assignment letter grades will be assigned (F=0 thru A+=4.33). A curve per assignment will be used for all students (with assignments not turned in not affecting the curve). In general each curves will have a mean between B- and B+, depending on my assessment of the overall performance. Individual "conceptual" assignments will have point values which reflect their relative weight. Class participation grade will be based on my assessment of the students voluntary contribution, plus their response to questions I ask them during class. Interactions with the instructor outside of class (such as in office hours) is also considered "class" participation. Business/BIS majors (if there are any) with should contact the instructor about an alternative "management" grading schema.

There will be a number of chances for extra credit which is added to your final letter grade with 300pts extra credit = 1 letter grade.

Homework Policies and expected workload

• I expect students to devote an average of 7-10 hours, outside class, per week on the work for this course, of which 2-3 hours are expected to be reading. (Unlike some of my courses, in this class the average student should, if their team works effectively, finish the assignments. Team assignments imply 18-24 hours TEAM (5-7 hours per member) given a reasonable level of knowledge, communication and cooperation. Part of the "philosiphy" of this course is to make things big enough that if you don't follow good SE practice, you will feel it. If, as sometimes happens, your team does not work effectively, the time required for completion will be higher, and could double or triple). (Poor preparation, poor communication or poor cooperation can significantly increase the amount of time required). Poor debugging can add significantly to the time needed of those assignments requiring use of the computer.
• If an assignment is given multiple weeks, do NOT wait until the last few days to start. Don't count on putting in 20 hours in 3 days, because you might just need to ask me, the grader or other team members a few questions. Assignment, like real world problems, are often somewhat vague and may require clarification (that I don't provide until asked specific questions.)
• The course will have numerous computer-based assignments; some teams assignments will use UNIX, other Windows.. Individual assignments and individual reports for each team assignment will be turned in on paper. Team reports will all be via web pages (collected by a script at the specified time). Executables programs be required for some assignments as well.
• Teams will be organized by sign-up, with the limitation that any two students CANNOT be on more than 2 teams together. Teams will generally be 4 students (but may vary depending on team purpose). Every team project will call for a group report as well as a shorter individual report for each team member. Each team assignment will be given a total number of points. Based on the teams reports, each team will receive a total number of points. These points will be shared, NOT NECESSARILY EQUALLY, among team members. The individual report for a teach should address your contribution to the team and how you feel the teams grade should be divided and why. Long term teams will be able to "fire" members (based on a process to be described in class). Fired student may find them selves on a team of 1 or 2.
• The course will have "conceptual" assignments and quizzes. These are to be done as INDIVIDUAL Assignment. Do not discuss them with other class members until after the solutions are posted. There may also be non-graded homework that will help prepare you for the quizes. There will also be some homework that is graded. Even if you are taking the exam weighted option you should look them over, some of them could be on the exam.
• The answers to all assignments should be typewritten--get used to using your favorite editor. Fancy formatting is generally not needed. If you make assumptions, state them clearly. Unless otherwise stated in class or via email individual homework is due at the beginning of class (05:50) on the day assigned. Homework is not a reason to miss class or be late. Late assignments will incur 10% off per calendar (not class) day. Bringing it late to class is one day late. You will have plenty of notice on assignments so if the machines are down 12 out of the last 24 hours before the due-date, don't automatically expect an extension. You should, however, check email regularly before an assignment.