Department of Information Technology

Operating Systems IT & DVK Spring 2009, Project Assignment

Note that the DVK-project is 10 Hp while the IT-project is 5 Hp.


The project starts after the exam of part I of the course, and runs up until the summer break. This is the timeplan for the project (subject to change):

Date Activity Time Room Description
12/3 Kick-Off 13:15 - 15:00 P1211 Official starting date of the project. Guest lecture by Mikael Bergqivst introducing Simics.
25/3 Deadline Appoint a group leader. Submit your 1st weekly report.
27/3 Deadline Hand-in project description (your interpretation of the requirements).
1/4 Meeting 1 Architecture sketch due, Goal setting meetings with all groups.
22/4 Deadline System design due (originally 8/4 but postponed due to easter break).
Week 19 Meeting 2 30 minute Progress Meetings for all groups.
3/6 Deadline 08:15 - 12:00 P1245 Demonstration and final hand-in: DVK-2
4/6 Deadline 13:15 - 17:00 P1245 Demonstration and final hand-in.

Progress Report Meetings

Each group will present their design sketch and receive guidance and feedback on progress to date from the teaching staff.
This meeting will take approximately 30 minutes. During the first 15 minutes the group presents progress towards implementation of the specification based on the goals set by the group for themselves at the first meeting. A minimum goal is to produce an implementation of the minimum requirements for a pass in the course.

During the spring there will be two scheduled progress report meetings for each project group with the teaching staff. These meetings provide an opportunity to follow up problems with realizing the goals the group has set up and to make work plans for the following two week period in collaboration with the staff guiding the project.


The grades for the project are pass or fail (G or U). However, groups that do a very good project can raise their grades on the exam from a pass (3) to a higher grade (4 or 5) provided they score close to a higher grade on the exam. Doing a very good project is defined as completing one or more extra credit requirements, as found in the specification of the project.

All projects are to be handed in at at the final demonstration day before the summer break. If the project does not fulfil the basic requirements at this point, you will need to give a good structured explanation for why your project failed to produce the required output to pass the project. There will be no extensions given.


Before writing specifications, you need to understand the architecture and tools used in the project:

  • Do the Simics introduction lab.
  • Understand the example files. To make sure you understand, try for example to combine the three examples into one, i.e. with a single exception handler that can handle timer interrupts, serial communication (UART) and system calls.

It is a good idea to familiarize yourself with the tools you will be using early on in the project. For example, make sure to setup cvs and do the Simics introduction lab.

On the hand-in day (TBA), there will be a final handin session . Each group is given approximately 45 minutes to demonstrate their OS implementation.

Updated  2009-04-02 13:37:21 by Karl Marklund.