Assignments and deadlines
The programming assignment and written assignment
should be considered to be assignments given in parallel. Try to spend a number of hours per week on
both a programming assignment and a written assignment.
Deadlines are still tentative and thus subject to change.
The following deadlines exist, ordered by deadline date.
- Data flow analysis written assignment [Deadline tue May 16th 2006, 12:45]
- Monotone framework programming assignment part one submit as monotone1 [Deadline Wed May 31st 2006, 23:59]
- Control flow analysis written assignment [Deadline tue June 13th 2006, 12:45]
- Type and effect systems written assignment [Deadline tue June 20th 2006, 12:45]
- Abstract interpretation written assignment [Deadline fri June 30th 2006, 12:45]
- Monotone framework programming assignment part two submit as monotone2 [Deadline wed July 5th 2006, 23:59]
The deadlines for the various assignments and parts of assignments to be submitted are listed above. Try to be on time; this greatly simplifies the administration task. People who submit too late, should take into account that they will get at least a one point penalty for the overhead (out of ten), depending on how much too late the submission is.
The programming assignments should be in the form of a single zip file including the necessary code and documentation, as explained on the page for the assignment. They should be submitted to me using
I prefer that you put a printed version of your document into my hands at a lecture,
or put it in my CGN post box (top floor).
If submitted electronically, then you may do so by sending an e-mail to
with your entry attached.
Every answer you give for the written assignment should include an explanantion why you think it is correct.
Make sure your names and student numbers are at the top of each hand-in, and in the case of software being handed in, in your documentation file and in the main source file.