Faculty of Informatics
CSCI231 – Operating Systems
Subject Outline
Autumn session 2007
Head of
School –Professor Philip Ogunbona, Student Resource Centre, Tel: (02) 4221 3606
|
Subject Coordinator and Lecturer |
Mr Daniel
Saffioti |
|
Telephone
Number: |
02 4221
4357 |
|
Email: |
|
|
Location: |
Building 3,
Room 202 |
Mr. Saffioti’s Consultation Time During
Session
|
Day |
Time |
|
Monday |
15:30 – 16:30 |
|
Tuesday |
15:30 – 17:30 |
|
Wednesday |
15:30 – 17:30 |
|
Subject Coordinator and Lecturer |
Associate
Professor Willy Susilo |
|
Telephone
Number: |
02 4221
5535 |
|
Email: |
|
|
Location: |
Building 3
Room 203 |
Assoc Prof Susilo’s
Consultation Times During Session
|
Day |
Time |
|
Monday |
08:30 – 10:30 |
|
Thursday |
08:30 – 10:30 |
Subject
Organisation
|
Session: |
Autumn
Session, |
|
|
Credit
Points |
6 credit
points |
|
|
Contact
hours per week: |
3 hours lectures, 2 hours laboratory, 1 hour tutorial |
|
|
Lecture
Times & Location: |
||
|
Tutorial
Day, Time and Location can be found at: |
|
|
Students
should check the subject’s web site regularly as important information,
including details of unavoidable changes in assessment requirements will be
posted from time to time. Any
information posted to the web site is deemed to have been notified to all
students.
This
subject develops a thorough understanding of the principles and concepts of
modern computer operating systems. Topics covered will broadly include, process
management, resource allocation, OS kernel, memory management, concurrency and
file systems. Specifically the subject will include discussions on, process
concept, synchronization, concurrency control, threads, inter-process communication,
deadlock prevention, avoidance and detection, micro and monolithic kernels,
multi-tasking; interrupt handling, system and user processes. System calls,
problems of allocation, protection and sharing, memory mapping schemes, CPU
scheduling algorithms, real-time scheduling, naming and directory schemes, disc
space allocation, file protection and access control and operating system
security.
On
successful completion of this subject, students should be able to:
Attendance
Requirements
It is the responsibility
of students to attend all lectures/tutorials/labs/seminars/practical work for
subjects for which you are enrolled.
Attendance
and participation in lectures, tutorials and web-mediated activities is a
requirement for the successful completion of this course. Failure to do so may
result in a fail grade being recorded. A good indicator of satisfactory
attendance is approximately 80% of the allocated contact hours. Attendance per
se is not an assessable component of this course.
It should be noted that according to Course Rule 003{Interpretation Point 2 (t)} each credit point for a single session subject has the value of about two hours per week including class attendance. Therefore, the amount of time spent on each 6 credit point subject should be at least 12 hours per week, which includes lectures/tutorials/labs etc
Satisfactory
attendance is deemed to be attendance at approximately 80%* of the
allocated contact hours. Attendance rolls may be kept for lectures, TUTORIALS and laboratories. If you are
present for less than 80%* you need to apply for special consideration,
otherwise a fail grade may be recorded.
There will be 3 hours of lectures every week. There
is also 1 hour of tutorial. Satisfactory attendance at both lectures and
tutorials is a requirement for the successful completion of this course.
Failure to comply may result in a fail grade being recorded.
Lecture notes
and other subject resources will be available from the subject’s E-Learning website
at http://www.uow.edu.au/lol. These
notes do not include many of the examples and explanations given in lectures
for which attendance at lectures will be required. They also do not represent the entire content
of the course. Examples and further
material will be covered in lectures and supplemental notes will appear on the
subject website. Additional materials may be found in /share/cs-pub/231.
Lecture
Schedule
A proposed Lecture schedule for the subject is as
follows:
|
Week |
Topic |
Assessment Tasks Due |
|
1 |
Introduction Computer
System Structure |
|
|
2 |
Operating
System Structure |
|
|
3 |
Processes CPU
Scheduling |
End
of Week 3, Assignment 1 Due |
|
4-5 |
Process
Synchronization Concurrency
Control |
End
of Week 5, Assignment 2 Due |
|
5-7 |
Interprocess
Communication & API’s |
End
of Week 7, Assignment 3 Due Mid
session Examination, end of Week 7. |
|
8 |
Virtual Memory Memory
Management |
|
|
9-10 |
Storage Subsystems File
System Design, Implementation & API’s |
End
of Week 10, Assignment 4 Due |
|
11 |
Networking
and Communications |
|
|
12 |
Operating
System Access Control and Security |
End
of Week 12, Assignment 5 Due |
|
13 |
Overview
of Major Operating Systems e.g. BSD, Solaris, Windows etc |
|
Subject
Materials
The following texts are recommended for this subject:
|
|
Operating System Concepts by Silberschatz, Galvin and Gagne, Seventh Edition, John Wiley & Sons, ISBN: 0-471-69466-5 |
|
|
Operating Systems by Nutt, Third Edition, Adison Wesley, ISBN 0-321-189555-8 |
|
|
Operating Systems: Design and Implementation, Minix Book by Tannenbaum and Woodhull, Third
Edition, Pearson Prentice Hall, ISBN: 0-13-142938-8 |
These books can be purchased from the Unibookshop.
These books are recommended reading – it is up to you to decide if you wish to
acquire these texts.
|
|
Denotes a personal favorite of the lecturers. |
This
subject has the following assessment components.
|
Assessment Items & Format |
Percentage
of Final Mark |
Due Date |
|
Five Coding/Practical
Assignments |
30% |
See
remarks below on Assessment. General due dates are
as follows: End of Week 3,
Assignment 1 Due, End of Week 5,
Assignment 2 Due, End
of Week 7, Assignment 3 Due, End of Week 10,
Assignment 4 Due, End of Week 12,
Assignment 5 Due. |
|
Mid Session
Examination |
10% |
During Week 7
Lectures. See remarks below on
Assessment. |
|
Tutorial Class
Exercises |
10% |
During random tutorial classes. See remarks below on Assessment. |
|
Examination |
50% |
Examination Period. |
Unless
otherwise notified by the subject coordinator, all written assignments must be
submitted electronically.
1.
All assignments must be completed
independently. Plagiarism may result in
a FAIL grade being recorded for that assignment.
2.
All assessment work is to be submitted via
submit on the Unix hosts by the dates given above. The directive for submission
will be printed on the assignment specification.
3.
If you cannot submit an assessment item by the
stated time then it must be submitted to the subject coordinator as soon as
possible.
4.
Late submission of assessment item MUST be
accompanied by a special consideration item via SOLs
5.
An extension of time for the completion of an
assignment may be granted in certain circumstances. A request for an extension must be made to
the Subject Coordinator via SOLs before
the due date.
6.
Electronic submissions, faxes and un-receipted
mail submissions will NOT be accepted except via the turnin submission process.
7.
Penalties apply to all late work, except if
special consideration has been granted.
Late submissions will attract a penalty of 10% of the assessment mark per day including
weekends. Work more than 5 days late will be awarded a mark of
zero. Your tutor cannot grant you an extension.
8.
Assignments will be returned to students during
lectures generally within 1 week.
9.
This subject will consist of 5 assignments. The
assignments will be a mix of coding and theory. The assignments will due
roughly on two-week intervals commencing from week 2. Each assignment is to be
submitted electronically using the submit command.
10. The subject
will also consist of a mid session examination. The examination will be
administered in the lectures of Week 7.
11. There are
weekly tutorial classes in this subject. The tutorial classes will consist of
lectures. In five random tutorial classes there will be a small task to be
performed.
Students must refer to the Faculty Handbook or online references, which
contains a range of policies on educational issues and student matter.
Please note that if this is your last session and you are granted a supplementary exam, be aware that your results will not be processed in time to meet the graduation deadline.
Plagiarism
When you submit an assessment task, you are
declaring the following:
1.
It
is your own work and you did not collaborate with or copy from others.
2.
You
have read and understand your responsibilities under the
3.
You
have not plagiarised from published work (including the internet). Where you
have used the work from others, you have referenced it in the text and provided
a reference list at the end ot the assignment.
4.
Plagiarism
will not be tolerated.
This outline should be read in conjunction with the following documents:
|
Code of
Practice - Teaching and Assessment http://www.uow.edu.au/handbook/codesofprac/teaching_code.html |
Key Dates |
|
Code of
Practice - Students http://www.uow.edu.au/handbook/codesofprac/cop_students.html |
Information
Literacies Introduction Program |
|
Acknowledgement
Practice Plagiarism will not be
tolerated |
Student
Academic Grievance Policy http://www.uow.edu.au/handbook/codesofprac/cop_supervision.html#8 |
|
Special
Consideration Policy http://www.uow.edu.au/handbook/courserules/specialconsideration.html |
Code of
Practice-Honours |
|
Non-Discriminatory
Language Practice and Presentation |
Intellectual
Property Policy http://www.uow.edu.au/research/researchmanagement/1998IP.html |
|
Occupational Health and Safety http://staff.uow.edu.au/ohs/commitment/OHS039-ohspolicy.pdf |
SCSSE
Internet Access & Student Resource Centre http://www.sitacs.uow.edu.au/info/current/internet_access_and_resource.shtml |
|
SCSSE
Computer Usage Rules http://www.itacs.uow.edu.au/info/current/support/labs/rules.shtml |
SCSSE Style
Guide for Footnotes, Documentation, Essay and Report Writing |
|
SCSSE
Student Guide |
Informatics
Faculty Librarian, Ms
Annette Meldrum, phone: 4221 4637,ameldrum@uow.edu.au |
|
SCSSE
Subject Outlines |
|