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, four 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 20 points. At the end of the course, the point totals on the
obligatory work will be summed, resulting in a number between 0 and 100 inclusive. This
number will constitute 10% of the final examination 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 the C programming language. The rules governing submission are as
follows.
- The project will be given 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.
- Exercises 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, ten 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 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 two or three persons may submit one solution. 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.
- Grading resources are limited. Therefore, work submitted well after the deadline may not
be graded at all. If you must submit work late, discuss this with the course assistant.
- All obligatory exercises must be submitted for grading on or before the third and final
examination (on June 08, 2009). No exercises will be accepted after that date.
10.4 Obligatory Work Completed in Previous Years
- Points for obligatory exercises do not carry over from previous years.
- If all of the obligatory exercises from a previous year were completed, then credit for
completing the obligatory exercises, with zero points, will be awarded for the current year
upon explicit request on the part of the student. This will not be done automatically; the
student must make an explicit request.
- Submissions from different years cannot be mixed. Either credit is awarded for all exercises
completed in a previous year, or else all exercises for the current year must be completed.
- To the extent that the problems are similar, work from solutions developed in previous
years may be used in solutions for the current year. Such re-use must be explicitly
acknowledged, and may not be shared with partners who were not part of development
of the original solutions.