|
Operating Systems (230.205)
6 points / Semester 2
Handbook Description
The most fundamental of all system programs is the operating system.
The operating system controls all of a computer's resources, and
provides a base on which application programs can be written.
A modern operating system manages
one or more processors,
a hierarchy of memory,
clocks,
terminals,
disks,
network interfaces, and
other input/output devices.
The operating system's purpose is to provide an orderly and controlled
allocation of all of these resources amongst the programs competing for them.
cs205 introduces the key mechanisms of all operating systems -
processes,
memory management,
file systems, and
protection and security.
The evolution of these mechanisms is presented through a historical tour
of operating system development, leading to a study of
current hardware and operating system
speeds, capacities, and physical limitations.
The role of processes, and their creation,
scheduling, synchronization, and communication is covered.
This is followed by a study of storage management:
static and dynamic allocation,
paging and segmentation,
virtual memory and demand paging,
page replacement algorithms, and
memory caches and their effect on performance.
File system concepts are addressed:
input/output hardware and software,
files,
directories and access mechanisms,
file allocation and access algorithms, and
performance.
Finally, the increasingly important areas of protection and security
are introduced:
goals,
authentication,
access mechanisms,
protection domains,
access control lists and capabilities, and
monitoring.
Throughout the unit, reference is made to case-studies
from two of today's most successful operating systems, Linux and
Microsoft Windows. Laboratory and tutorial work compare and contrast the
provision of the key operating system mechanisms in each environment.
Prerequisites: Data Structures & Algorithms 223
Unit Aims
On completion of this unit, students should be able to
- apply their knowledge of the basic fundamentals of operating
systems to problems encountered in the setting up and tuning of computer systems
- understand the terminologies and concepts in the design, tuning, and use of operating systems,
and be able to communicate effectively with other engineers and users with regard to
the efficient use of operating systems,
- be able to identify problems users encounter in the efficient
use of computer systems and, if hardware resources allow, rectify them,
- understand how to make efficient use of existing tools and
thus contribute to sustainable development aims by not throwing
away extant systems in favour of newer ones,
- understand how use of a multi-user operating system affects other uses of the system, and
their professional and ethical responsibilities as a consequence,
- use their knowledge to understand future developments in operating systems,
i.e. to use this course as a foundation for lifelong learning in this area.
Teaching Staff
Textbook
William Stallings, Operating Systems: Internals and Design Principles, 5th edition (2005), Prentice Hall, ISBN 0-13-127837-1.
The text is available from United Booksellers, 126 Broadway.
Contact Hours
cs205 consists of
24 hours of lectures,
33 hours of laboratories, and
7 hours of tutorials.
Tutorials are held in even-numbered weeks, with a revision tutorial in Week 13.
It is expected that you will need to undertake additional study to achieve satisfactory progress in cs205.
One additional hour per hour of formal contact is a reasonable estimate (i.e. an additional 5-6 hours per week).
Assessment
The assessment scheme for cs205 consists of
- a 20% mid-semester test in September,
- a 40% practical project, due in October, and
- a 40% two-hour examination in November.
Before undertaking cs205, students should read the
Guidelines for Academic Assessment in the 2005 Interfaculty Handbook.
Attainment of the aims of the course will be assessed by testing
fundamental knowledge in the test and examination and
assessing application of that knowledge in the project and examination.
Students who do not obtain a mark of at least 40% in the
test and examination combined (i.e. at least 24/60)
will be deemed to have failed cs205.
Unsatisfactory Progress
Any student who does not demonstrate satisfactory progress in this
unit, as defined in the FECM
Policy on Assessment Practices and Procedures, may be refused admission to the
final examinations. The final deadline for notification of unsatisfactory progress is the
last day of Week 10.
Penalties
The School of Computer Science and Software Engineering has adopted a policy on
minimum penalties for late items of assessment.
This is the default policy of all units unless indicated otherwise, in writing, by the
specific unit coordinator.
This policy shall apply to all items of continuous assessment, whether
submitted either physically or electronically. Immediately after the submission deadline for an item of continuous
assessment, a penalty of 20 percent will be applied PER DAY or PART THEREOF.
The minimum mark possible for late submission is zero. The
percentage is based on the item´s total contribution to the unit´s
assessment. For example, a project contributing 40% to the unit´s
assessment will incur a penalty of 8 marks for each day late until it is submitted or
a mark of zero results.
A more detailed description is given in this School´s Policy on
Late Submission. The Faculty does have an appeals procedure, the details of which can found at the Policy for Appeals.
Plagiarism
Plagiarism is broadly defined to be when any portion
of the work presented for assessment, can be attributed
to another party. The student making the submission should acknowledge
what aspects of the presented work is not directly derived by
them. For the purposes of plagiarism it is irrelevant that you
have been given permission by someone to copy their work
and present it as your own.
You are directed to the School of Computer Science and Software Engineering Policy on Plagiarism and the Faculty of Engineering,Computing and Mathematics Policy on Plagiarism.
Faculty Scaling
Final assessment is subject to the Faculty Scaling Policy.
This information is correct as at 24-Jun-2005, but is subject
to change from time to time. In particular, The University
reserves the right to change the content and/or method of
presentation and/or the method of assessment of any unit of
study, to withdraw any unit of study or programme, and/or to
vary arrangements for any programme.
Copyright© 2005
School of Computer Science, & Software Engineering
The University of Western Australia
CRICOS Provider Code: 00126G
Last updated: 24-Jun-2005 |
