CS246 Object-Oriented Software Development
Spring 2018

Student Assessment

Assignments	Number	Tentative Due Date	Marks	Totals
	0	May 8 (Tues.)	0
	1	Due Date 1: May 14 (Mon.) Due Date 2: May 22 (Tue. since Mon. is a holiday)	5
	2	Due Date 1: May 28 (Mon.) Due Date 2: June 4 (Mon.)	7
	3	Due Date 1: June 11 (Mon.) Due Date 2: June 18 (Mon.) Due Date 3: June 25 (Mon.)	7
	4	Due Date 1: July 3 (Tue. since Mon. is a holiday) Due Date 2: July 9 (Mon.)	9
	5	Due Date 1: July 16 (Mon.) Due Date 2: July 25 (Wed.)	12
			40	40
Tests	Midterm	June 21, 04:30-06:20Th, Location M3 1006, DC 1351	20	20
	Final	TBA, scheduled by the registrar	40	40
				100

Note: you cannot get credit for assignments 1-5 until you have achieved 100% on assignment 0.

Note: These due dates are tentative only, and are subject to change.

Note: The final assignment is a project to be done in groups of three. You may do the project in pairs or individually, but you will be expected to produce the same output as a group of three. Be sure to work with people whom you trust; we will not arbitrate disagreements. Part of the evaluation of your project will consist of a live demo in front of a TA. This is mandatory.

• A passing mark in the weighted test portion of the final grade AND at least 45% in the average of assignments 1-4 must be achieved to pass the course. The final grade is calculated using the following formula:

      if ( testing_average < 50% or a1-a4_average < 45% ) then
          final_grade = MIN( weighted_testing_average, a1-a4_average, normally_calc_grades )
      else
          final_grade = normally_calc_grades
  

  In other words, good assignment marks alone cannot get you a passing mark in this course. Neither can good exam or project marks alone.

Tests

Both the midterm test and the final exam are closed book.

A missed test/exam receives a mark of 0, unless there is a documented reason. If a documented reason is provided for missing the midterm, its weight is applied to the final exam. If a documented reason is provided for missing the final exam, a grade of INC MIGHT be given, and the final exam must be written at the end of the next term the course is offered. A copy of the documented reason must be given to and approved by the instructor.

Assignments

All assignments must be done individually, unless the assignment is explicitly designated as a group assignment. All members of a group receive the same grade (no exceptions). The instructors/staff do not arbitrate group disputes; group members must handle any and all problems. A group assignment may be done individually, but it must be understood that the amount of work is significantly greater and no extra marks are given for this additional work.

Note: Marmoset is not a compiler! Do not submit C++ code to Marmoset, without first attempting to compile it yourself. For each problem on Marmoset where the deliverable is C++ code, if you have three or more submissions marked "Did not compile", a mark will permanently be deducted from your score on that problem.

Assignment Submissions

Assignments must be submitted using the Marmoset Submission and Testing Server.

The release test for a problem gives you the result of running your program on one basic test case (usually a case that appears in the assignment specification). The remaining test cases are secret tests, the results of which are revealed after the assignment is due. So be sure to test your code thoroughly, so that you pass as many of our secret tests as possible.

Lates

• Assignments are due on the due-date at the time specified on the top of the assignment.
• Late assignments are not accepted.
• An assignment not handed in receives a mark of 0, unless there is a documented reason.
• If a documented reason is supplied, and instructors decide that accommodation is warranted, the weight of the missing assignment is distributed across future assignments (assignments 1-4 only) and/or exams (instructors will decide on the appropriate distribution). A copy of the documented reason must be given to and approved by the instructors (submit it to Caroline Kierstead).

Marking

• Assignments are marked on some or all of the following criteria:
  1. testing
  2. correctness
  3. hand-marking
• Note that correctly-working code is only one component of an assignment mark.

Remarking Policy

• Make a written request clearly stating the questions you want remarked.
• Include any supporting evidence for your case.
• No more than two weeks after the assignment or test is handed back, return your assignment or test with the remark page to the tutor during a tutorial or an office hour.
• All requests are processed after the deadline to ensure fairness and consistency in marking.
• Changes to your code are not permitted as part of a remark request.

Note: The entire assignment or test is examined when remarking; therefore, the grade could decrease.

Course Communication

The primary form of communication of information outside of lectures will be through Piazza. It is thus very important that you read it daily! Since it is very common for the number of posts to get very large, very quickly, we have posted some guidelines to using Piazza in Piazza to help make everybody's lives easier. Please make sure that you read the guidelines before you post.

---