CS 452 CS 652
Introductory assignment (Single) (due Sep 15) 5 5
Real-Time Operating System (Groups)
part 1 (Groups) (due Sep 29) 5 5
part 2 (Groups) (due Oct 6) 5 5
part 3 (Groups) (due Oct 20) 10 10
Real-Time Application (Groups)
train tracking part 1 (due Nov 3) 5 5
proposal and plan in class (due TBA) - -
train tracking part 2 (due Nov 10) 10 10
documentation submission (due Nov 30) - -
demonstration in class (due Dec 4) 10 10
final code submission (due Dec 4) 20 20
Final Examination 30 30
Project (CS652 students only) - 20
=== ===
Total 100 120
Each due date is firm. Each project or assignment must be handed in by 4:30 p.m. on the due date, except the train tracking assignments which will be due at the start of the demo session (TBA). Documentation is a critical aspect of your submission. Your documentation must give an overview of the design, explain choices that were made, and clearly explain any limitations or assumptions of your system. Although we will look at your code, if we have to look at your code to understand what you are doing, you will lose marks. The onus is on you to convince the marker that your project works.
Each kernel assignment is expected to include a thorough test suite to convince the marker that your OS works! Building a good set of tests from the start will make your life significantly easier.