Unit outline for Operating Systems (CITS2230).

6 points / Semester 2
Location: UWA (Crawley)

Handbook description

The most fundamental of all system programs is the operating system, which controls all of a computer's resources and provides the base on which application programs may be written. A modern operating system manages one or more processors, a hierarchy of memory, clocks, 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 among the programs competing for them. This unit introduces the key mechanisms of all operating systems—processes, memory management, file systems, and protection and security. The evolution of these key mechanisms is presented through an 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—their creation, scheduling, synchronisation and communication—is studied. This is followed by the study of storage management—static and dynamic allocation, paging and segmentation, virtual memory and demand paging, page replacement of algorithms and memory caches and their effect on performance. File system concepts are addressed, such as 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 studied—goals, authentication, access mechanisms, protection domains, access control lists and capabilities, and monitoring. Throughout the unit, constant reference is made to case studies from two of today's most successful operating systems—Linux and Windows. Laboratory and tutorial work compare and contrast the provision of the key operating system mechanisms in each environment.

Prerequisites: CITS2200 Data Structures and Algorithms

Unit aims

Students understand the role of an operating system in the wider computing context; appreciate the typical capacities, data transfer rates, and costs of contemporary hardware components, and the impact that lesser or greater capacity components have on an operating system's performance; understand the relationship and interactions between an operating system's critical software components; understand the relationship between contemporary operating systems, programming languages and user interfaces; and are able to make reasonable predictions about the future role and design of operating systems.

Teaching staff

Unit Co-ordinator: Dr. Lyndon While

Contact hours

56 (lectures: 25 hrs; tutorials: 7 hrs; labs: 24 hrs)

Assessment

This comprises a programming project, a mid-semester test and a final examination. The programming project develops the students' ability to identify problems and to formulate their solutions. The students develop the ability to apply fundamental knowledge through in-depth technical competence in their understanding of the subject. They complete the programming project in small teams consisting of two or three members. Hence, they learn to co-ordinate their programming activities and prepare documentation for both the design of the project and the code. The programming project enhances their ability to work in a team and improve their communication skills. Similarly, the final examination also requires students to undertake problem identification, formulation and solution. Both the programming project and the examinations test the students' understanding of operating system principles and their application of this understanding in developing non-trivial programs for operating system tasks. Supplementary assessment is not available in this unit except in the case of a bachelor's pass degree student who has obtained a mark of 45 to 49 and is currently enrolled in this unit, and it is the only remaining unit that the student must pass in order to complete the course.

Unsatisfactory progress

Any student who does not demonstrate satisfactory progress in this unit, as defined in the Faculty's policies 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.

Special consideration

Applications for consideration, deferral of tests or exams or extensions of time for assignments on medical, personal or other grounds must be lodged with the faculty office no later than three working days after the due date for the assessment in question. This rule will apply to all students, except in exceptional circumstances.

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 Faculty's policy on plagiarism.

Academic misconduct

The University of Western Australia strongly supports teaching and learning that promotes academic literacy and ethical scholarship for all students. As part of this commitment, UWA has recently developed new guidelines relating to Academic Misconduct (including plagiarism). It is also developing a range of resources for students and staff to further strengthen academic literacy and ethical scholarship at UWA. Further information is available on the Teaching and Learning website.

Academic Conduct Essentials (ACE)

All students who have not previously been enrolled at UWA are required to complete a short compulsory online module called Academic Conduct Essentials (ACE) within the first 10 weeks of semester. ACE introduces students to essential knowledge regarding ethical scholarship, helps prepare them for the expectations of their university career and informs them of correct academic conduct.

The unit can be accessed via WebCT. The final unit quiz must be completed with a mark of 80% or greater. Students may attempt the quiz as many times as they wish to gain the required pass mark. Completion of the unit will be recorded as an Ungraded Pass (UP) on students’ academic records. Non-completion (NC) within the required timeframe will also be documented on formal academic records.

Faculty Marks Adjustment Policy

Final assessment is subject to the Faculty's scaling policy.

Supplementary Examinations

Supplementary examinations will be awarded in accordance with the Faculty policy on supplementary assessment.

Student rights

Consult the University's Charter of Student Rights and Responsibilities.