Timetables

FIT2022 Timetable | Lectures | Tutorials | Laboratories

FIT2022 Timetable

Lectures

The lectures define the formal content of the unit, and will be used as the initial point of reference for unit knowledge outcomes. This knowledge will be built upon by the tutorials and laboratories in order to address the higher level objectives relating to skills and and application.

The lectures will be held at 12noon in S5 on Mondays, 1pm in S9 on Tuesdays and 1pm in S5 on Thursdays.

The lectures slides are taken from the instructors notes from the textbook by Gary Nutt, published by Addison-Wesley, and available from Pearson Australia. You are allowed to access and take a copy of the slides for the purpose of self-study, but you must not redistribute them.

The content field identifies the relevant section of the text book, and is a link to the slides for the lecture. Interspersed into the timetable are the tutorial and laboratory topics, with links to the relevant web pages. Each lab session is preceeded by a tutorial which discusses the important issues in the lab session. Feedback on the previous lab session will also be made available in the tutorials.

Under 'Book', the timetable shows the relevant sections of this year's text (Nutt), and last year's text (SGG = Silberschatz, Galvin, Gagne) used for background reading.

The current edition of Silberschatz et al has an on-line set of lecture notes.

Please bear in mind that at the time of writing, not all materials to be used in the lectures have been identified. This page will be updated regularly to reflect past practice, current happenings, and future intentions. Lines in red represent completed activities.

Tutorials

The tutorials are designed to reinforce lecture understandings, and to prepare the student to apply these understandings towards building the skills required to complete the laboratory sessions.

Tutorial sessions have been scheduled for (check your Allocate+ for details!)

Alternatively, you can go to the Main Allocate+ page and navigate to Student Login.

Laboratories

The laboratories are designed to give the student hands-on development of various computer systems concepts. Each lab is offered as a partial developed set of program exercises, where demonstrations show the student what is required, and extensions to complete or extend the exercise are required to be completed by the student. This is called the lab work, and it is a required part of the assessment for the unit. Students may work together in pairs (if they wish) for this purpose.

The laboratories are structured around using the programming language Python to develop the various subsystems of an operating system, and to use these components to explore the working behaviour in a very hands-on way. The labs culminate in the development of a complete working Python Operating System (PythOS) written entirely in Python.

An introduction to the topic of the lab will be provided in the tutorial in the week preceeding the lab. (Students should attend all tutorials, and a roll will be kept.) Students should read through the lab sheet in the week between the tutorial and corresponding laboratory, and should prepare their lab work as required.

Laboratory Hurdle

The laboratories are compulsory, and attendance records will be kept. A mark will be allocated for each lab attended, on the following scale:

A total mark of 8 or more (over 6 laboratories) is required to complete the laboratory hurdle.

Laboratory Journal

Students should keep a journal of work done for and in the laboratory. This journal may be kept electronically or on paper, but it must be written up as a text or LaTex document (no Word documents will be accepted!) and recorded in your svn repository.

The journal should contain the material prepared in advance to the lab session, together with answers to each of the exercises attempted during the lab session.

You are asked to keep your laboratory journals on-line, using the svn repository provided, for the reason that I will be reviewing these at the end of semester with a view to see what things worked well, and what didn't. This information will be used to improve next year's unit.

Document History

This page maintained by John Hurst. Copyright Monash University Copyright Policy	3833 accesses since 07 Jun 2007
Generated at 20090703:0216 from an XML file modified on 20070918:1553 Maintainer use only; not generally accessible: Local ServerWork ServerCSSE Server

3922 accesses since 07 Jun 2007, HTML cache rendered at 20091122:2358