[CSE]  Advanced Operating Systems 
 COMP9242 2010/S2 
UNSW
CRICOS Provider
Number: 00098G

PRINTER Printer-Friendly Version
Administration                        
- Notices
- Course Intro
- Times
- Lecture location/time
- Statistics
- Survey Results
 
Work
- Lectures
- Selected Papers
- Project Spec
- Exam
 
Support
- Forums
- Wiki
 
Resources
- Project Resources
- Slug Lab
- L4 Debugging Guide
- Developing on a Mac
- Developing on Linux
- SOS source browser
 
Documentation
- OKL4 reference manual
- Elfweaver user manual
- IXP42X hardware manual
- OKL Wiki
- NSLU2-Linux HomePage
- Intel IXP400 Software
 
Related Info
- IBM OS Prize
- OS Hall of Fame
 
History
- 2009
- 2008
- 2007
- 2006
- 2005
- 2004
- 2003
- 2002
- 2000
- 1999
- 1998
 
Staff
- Gernot Heiser
- Kevin Elphinstone (LiC)
- Guest Lecturers (TBA)
 
Stureps
- Student Reps

 
Valid HTML 4.0!

M9: System Documentation

Your final milestone is to complete the documentation of your system. Your documentation will describe your RPC interface and the internal structure of your operating system well enough that another student in your class could take the project over at this stage and debug or extend your system.

Be sure to point out any known limitations in your system, or any important assumptions you have made.

You also have a chance to clean up your codebase, so that it's readable by someone other than you.

At the very least you should document:

  • page-table structure,
  • system call dispatching,
  • I/O subsystem, and
  • process management.

If you completed any bonus features be sure to document them as well.

Hints

  • Use LaTeX.
  • Use diagrams.
  • Use a spell-checker.
  • Read Gernot's style guide.

Last modified: 20 Jul 2010.