Note: This unit version is currently being edited and is subject to change!
COMP3520: Operating Systems Internals (2020 - Semester 2)
| Unit: | COMP3520: Operating Systems Internals (6 CP) |
| Mode: | Normal-Day |
| On Offer: | Yes |
| Level: | Senior |
| Faculty/School: | School of Computer Science |
| Unit Coordinator/s: |
Associate Professor Zhou, Bing Bing
|
| Session options: | Semester 2 |
| Versions for this Unit: | |
| Site(s) for this Unit: |
http://www.cs.usyd.edu.au/~comp3520 |
| Campus: | Camperdown/Darlington |
| Pre-Requisites: | (COMP2017 OR COMP2129) AND (COMP2123 OR COMP2823 OR INFO1105 OR INFO1905). |
| Brief Handbook Description: | An OS itself is a software program that manages the hardware and software resources of a computer. It makes the computer system convenient to use and solving user problems easier. Operating systems are an essential part of any computer system – a course on OS is thus an essential part of any computer science education. This unit will provide a comprehensive discussion of relevant OS issues and principles and describe how those principles are put into practice in real operating systems. The contents include internal structure of OS; several ways each major aspect (process scheduling, inter-process communication, memory management, device management, file systems) can be implemented; the performance impact of design choices; case studies of common OS (Linux, MS Windows NT, etc.). |
| Assumed Knowledge: | None. |
| Lecturer/s: |
Associate Professor Zhou, Bing Bing
|
|||||||||||||||
| Timetable: | COMP3520 Timetable | |||||||||||||||
| Time Commitment: |
|
|||||||||||||||
| T&L Activities: | Tutorial: Practical and theoretical exercises and discussion. |
Learning outcomes are the key abilities and knowledge that will be assessed in this unit. They are listed according to the course goal supported by each. See Assessment Tab for details how each outcome is assessed.
(6) Communication and Inquiry/ Research (Level 4)
1. Ability in technical writing to communicate complex ideas clearly
(8) Professional Effectiveness and Ethical Conduct (Level 4)
2. Knowledge of available OS systems
(4) Design (Level 5)
3. Ability to design algorithms to solve OS related problems
(2) Engineering/ IT Specialisation (Level 5)
4. Understanding of OS internale components
5. Ability to efficiently implement OS-related algorithms
6. Significance of OS concepts and its impact on the whole computer systems
7. Understanding of a range of algorithms for OS, their performance and how & where to apply them
| Assessment Methods: |
|
||||||||||||||||||||||||||||||
| Assessment Description: |
Programming Exercises. A set of programming exercises conducted in class. These exercises are essential preparation for the assignments that follow. Assignments 1, 2 and 3. Assignments based on the programming exercises conducted beforehand. Final Exam. |
||||||||||||||||||||||||||||||
| Grading: |
|
||||||||||||||||||||||||||||||
| Policies & Procedures: | IMPORTANT: School policy relating to Academic Dishonesty and Plagiarism. In assessing a piece of submitted work, the School of Computer Science may reproduce it entirely, may provide a copy to another member of faculty, and/or to an external plagiarism checking service or in-house computer program and may also maintain a copy of the assignment for future checking purposes and/or allow an external service to do so. Other policies See the policies page of the faculty website at http://sydney.edu.au/engineering/student-policies/ for information regarding university policies and local provisions and procedures within the Faculty of Engineering and Information Technologies. |
| Prescribed Text/s: |
Note: Students are expected to have a personal copy of all books listed.
|
| Recommended Reference/s: |
Note: References are provided for guidance purposes only. Students are advised to consult these books in the university library. Purchase is not required.
|
| Online Course Content: | http://www.cs.usyd.edu.au/~comp3520 |
Note that the "Weeks" referred to in this Schedule are those of the official university semester calendar https://web.timetable.usyd.edu.au/calendar.jsp
| Week | Description |
| Week 1 | Introduction |
| Week 2 | Operating System Structures |
| Week 3 | Processes and Threads |
| Week 4 | Process Synchronization |
| Week 5 | deadlocks |
| Assessment Due: Assignment 1 | |
| Week 6 | CPU Scheduling |
| Week 7 | Main Memory |
| Week 8 | Virtual Memory |
| Week 9 | File-System Interface and Implementation |
| Assessment Due: Assignment 2 | |
| Week 10 | Mass-Storage Structure |
| Week 11 | I/O Systems |
| Week 12 | Protection and Security |
| Week 13 | Review |
| Assessment Due: Assignment 3 | |
| STUVAC (Week 14) | This week is left free for independent study. |
| Exam Period | Any Exam or Quiz worth more than 30% of the final assessment will be scheduled in this two week period. |
| Assessment Due: Final Exam |
Course Relations
The following is a list of courses which have added this Unit to their structure.
Course Goals
This unit contributes to the achievement of the following course goals:
| Attribute | Practiced | Assessed |
| (6) Communication and Inquiry/ Research (Level 4) | No | 20% |
| (8) Professional Effectiveness and Ethical Conduct (Level 4) | No | 22% |
| (5) Interdisciplinary, Inclusiveness, Influence (Level 5) | No | 0% |
| (4) Design (Level 5) | No | 17% |
| (3) Problem Solving and Inventiveness (Level 5) | No | 0% |
| (2) Engineering/ IT Specialisation (Level 5) | No | 41% |
These goals are selected from Engineering & IT Graduate Outcomes Table 2018 which defines overall goals for courses where this unit is primarily offered. See Engineering & IT Graduate Outcomes Table 2018 for details of the attributes and levels to be developed in the course as a whole. Percentage figures alongside each course goal provide a rough indication of their relative weighting in assessment for this unit. Note that not all goals are necessarily part of assessment. Some may be more about practice activity. See Learning outcomes for details of what is assessed in relation to each goal and Assessment for details of how the outcome is assessed. See Attributes for details of practice provided for each goal.
