Obligatory Problem Sets in INF4820
As a software engineering class, this course has a substantial practical component. Thus, a central element in the class will be hands-on exercises throughout the semester. Exercises will typically consist of a programming assignment, implementing or refining (in terms of functionality and efficiency) the techniques taught in the class. Some exercises may include a few theoretical questions, but if so these serve to lay the ground for other, hands-on parts of the exercise. Exercises often build on each other, and we will provide model solutions as we go along. Thus, we will need to have to enforce a strict schedule: for each exercise, there will be a hard deadline; both for scheduling and fairness reasons, we will not be able to accept late submissions, i.e. only submissions received before the announced deadline will be counted against the assignment. Furthermore, there is no room for re-submission of incomplete or partially erroneous exercise solutions. Each submission will be reviewed by at least one of the instructors and rated on a point scale from zero to one hundred (corresponding to how many per cent of the exercise were successfully solved). Through interaction with instructors in the laboratory (gruppe) sessions and, where required, individual consultation outside of class hours, students will have the opportunity to gauge the quality of their solutions prior to submission. There will be a total of four obligatory problem sets, each worth 100 points. To qualify for the final exam, students will be required to have accumulated a minimum of 200 points, i.e. at least half of the total points available. In this scheme, failing to deliver an assignment by its deadline will be counted as zero points. However, it will be possible to make up for that in later exercises, as long as the sum of points over all assignments exceeds the 200 point minimum threshold.
Each problem set will have at least two weeks between the date it is released and its submission deadline. Typically, we will release a fresh exercise for the laboratory session and then use that session on working towards the solution already. Submission deadlines will tend to be 12:00 noon on Tuesdays, i.e. right before the lecture. Thus, students will have the opportunity to work through an assignment during the first laboratory session, possibly bring further questions and discussion into the lecture session, and if need be continue work on the current exercise in at least another laboratory session (although in some cases, a new exercise may have been released already). In addition to the two laboratory hours of joint work with instructors on each assignment, each problem set will be designed to require another few hours of individual work outside of class, typically around four extra hours per week, on average, for the average student. We cannot accept group submissions, and each student is expected to produce their solution in independent, individual work. Copying of solutions or group submission cannot be accepted.
Finally, the most important bit. Exercise submission deadlines will be as follows:
|1||Lisp Essentials||Friday, September 19, 12:00 noon|
|2||FSA Operations||Tuesday, October 7, 12:00 noon|
|3||Sequence Classification||Tuesday, October 28, 12:00 noon|
|4||DAG Unification||Tuesday, November 18, 12:00 noon|