10 Obligatory Work

10.1 Weekly Obligatory Work

The course includes five obligatory written and short computer exercises. The rules governing these submissions are as follows.

• Points will be assigned to the submitted solutions for each exercises. These points will be based upon the quality of the solutions, as well as their timeliness.
• Exercises will furthermore be graded as satisfactory or unsatisfactory. To receive a passing grade in the course, the student must have submitted a satisfactory solution to each exercise.
• Each exercise will have a due date. For each working day or fraction thereof that the submission is late, five points will be subtracted from the grade. (The grade may never be less than zero, of course.)
• Exercises marked as unsatisfactory may be resubmitted, in order that a satisfactory evaluation be obtained. However, resubmitted work will never receive any additional points.
• Each exercise will be worth 30 points.

10.2 Obligatory Programming Project

In addition to the weekly obligatory exercises, there will be one larger programming project, involving interfacing to a relational database using CLI/ODBC (Call-Level Interface / Open Database Connectivity) and either the C or else the Python programming language. The rules governing submission are as follows.

• The project will be given up to 50 quality points, as well as marked as satisfactory or unsatisfactory. To receive a passing grade in the course, a student must have submitted a satisfactory solution for the project.
• Submissions marked as unsatisfactory may be resubmitted, in order that a satisfactory evaluation be obtained. However, resubmitted work will never receive any additional points.
• For each working day or fraction thereof that the submission is late, five points will be subtracted from the grade. (The grade may never be less than zero, of course.)

10.3 General Remarks on the Obligatory Work

• The obligatory exercises and project may be completed in groups, and collaboration is permitted on the software exercises, roughly as described in the documents Riktlinjer vid labgenomförande (Policy for Obligatory Exercises) and Hederskodex (Honor Code). More details will be provided later, when the descriptions of these exercises are distributed.
• The written exercises, as well as the programming project, may be submitted individually or in groups. However, once a solution is submitted, only those named on the submission will receive credit for it. Partners in solution may not be added after the initial submission

10.4 Deadlines for Submission of Obligatory Work

• The deadlines for exercise submissions are as follows.

  Exercise	Deadline	Deadline Type
  Exercise 1	February 02, 2015 at 08:00	Initial
  Exercise 2	February 09, 2015 at 08:00	Initial
  Exercise 3	February 16, 2015 at 08:00	Initial
  Exercise 4	February 23, 2015 at 08:00	Initial
  Exercise 5	March 02, 2015 at 08:00	Initial
  ODBC Project	March 09, 2015 at 08:00	Initial
  All	May 04, 2015 at 08:00	Second
  All	June 08, 2015 at 08:00	Final

• The initial deadlline for each exercise is the time at which points begin to be deducted for lateness.
• An exercise solution which is submitted in advance of its initial deadline will be graded in a timely fashion, and students will be given the opportunity to improve unsatisfactory submissions and to resubmit them for an additional evaluation.
• For each obligatory exercise, there will be a resubmission deadline, defined to be five working days after the graded initial submission is returned. The resubmissions will be graded within ten working days of the resubmission deadline. This applies only to resubmissions of initial submissions which were received no more than four days after the deadline. For initial submissions which are more than four days late, there are no guarantees.
• Re-grading of submissions, other than for first resubmissions which are received no more than four working days after the initial deadline, is entirely at the discretion of the grader. The only exception is that all remaining submission will be graded within ten working days of the resubmission dates of May 4 and June 8.
• With the exception of extenuating circumstances (which will generally require written documentation), no submissions will be accepted after June 08, 2015.

10.5 Obligatory Work Completed in Previous Years

• Credit for individual exercises may not be carried over from previous years. A student who does not already have a satisfactory grade recorded for the exercise part of the course must complete all requirements for that part as defined by this offering of the course.
• Quality point from previous years may not be carried over to the current year. Students who have already completed the laboratory exercises for previous years may however re-submit solutions for the current year in order to obtain quality points.