Course Outline - Operating Systems Implementation Skip navigation Operating Systems Implementation ANU College of Engineering & Computer Science Search query Search ANU web, staff & maps Search COMP3300/6330 menu Search query Search ANU web, staff & maps Search COMP3300/6330 Course Outline Lectures Labs Assignment 1 Assignment 2 Marks and Lab registration Announcements Discussion Reading Material People Course Outline Without Operating Systems todays computers would be nothing more than ugly expensive paper weights. Operating systems are programs that act as intermediaries between user programs and the physical hardware of the computer. First, they provide a layer which simplifies and standardizes the operation of the computer system. Second, they act as resource managers controlling the resources of the computer system. These resources include the following: CPU, memory, keyboards, screens, printers, storage devices, etc, or even more abstract resources such as: file systems, windows, processes, etc. The purpose of a good operating system is to provide these services in a reliable, convenient and efficient manner. The Operating System is a non-trivial program and quickly descends into the tar-pit of complexity. This unit takes a detailed look at the services provided by, and the internals of, an existing operating system to see how each part is constructed and integrated into the whole. The lectures will also address recent literature describing advances in operating systems. The following topics are addressed: system programming and its facilities (including I/O, signals, job control, interprocess communication, sockets, transport layers, remote operations), system calls and their relation to the system libraries, process management and coordination, implementation of message passing, memory management, interrupt handling, real-time clocks, device-independent input/output, serial-line drivers, network communication, disk drivers, deadlock avoidance, scheduling paradigms, file systems, security. Lecturers Dr Eric McCreath - email : ericm@cs.anu.edu.au (Chair of Examiners) Unit Prerequisites To enrol in this course you must have completed COMP2300 and COMP2310; and COMP1600 or COMP2600 or 6 units of 2000 MATH courses. Text Book The text book for this course is Operating Systems: Three Easy Pieces, Arpaci-Dusseau 2014, http://www.ostep.org Expected knowledge Note that, it is expected that students : have a basic understanding of computer system structures, operating systems, networks and concurrency (aspects that should be covered in COMP2300, COMP2310), have done some programing in a language that uses procedures such as Java, c, c++, python, etc. (We will use c in the course however I will spend some time teaching this as most people no longer have a background in it.) (so Java is covered in COMP1110), can use UNIX (from a users perspective), and basic maths skills. Learning Outcomes At the completion of this course the student will be able to: identify and evaluate features of the system library of a particular operating system, and be able to apply this knowledge to program small applications describe and analyse the actual algorithms and data structures that are used in a particular operating system define and analyse the structure of operating systems in general, especially those that support communicating processes identify and describe the reasons for many architectural features of contemporary machines demonstrate experience in the design and implementation of a large software system Assessment For both COMP3300 and COMP6330 students the final mark is composed of four components: Assessment Item Weight Learning Outcomes Week Due (on Fridays 6pm) Final Exam (this is a hurdle - you must get over 50% in this to pass the course) 30% 2,3,4 - Individual Labs 20% 1,3 3(extended to week 4),5,7,9,11 Individual Assignment 20% 2,3 6 Group Assignment 30% 2,5 12 From the date that your assessment marks are released, you have a period of two weeks in which to question your mark. After this period your mark will be final. Note that consistent scaling for each of the courses may occur with the final marks. Students must get a minimum final overall mark of at least 50% to pass the subject. Final marks are moderated by a Research School of Computer Science examiners meeting. Supplementary assessment will be awarded to those students with an overall course mark of between 45 and 49. Students who fail the hurdle and gain an overall mark of at least 45 will be given the opportunity of supplementary assessment. This will likely take the form of an oral examination. More generally oral examinations will likely be used in the following situations: deferred assessments or if the convener believes a particular student’s assessment has not been adequately or fairly assessed. This is done under Assessment Rule 2016 11(4): “(4) Before submitting recommendations under subsection (3)(c), the Chair of Examiners may require a student to take a further assessment to ensure that the academic performance of the student in the coursework is adequately and fairly assessed. The further assessment may be oral, written or practical.” Please check the ANU web pages for policy statements concerning special consideration and deferred and supplementary examinations. Quality and integrity are expected from all students. Students should also expect this from the lecturing/tutorial staff. Please read over the ANU’s policy on this matter: http://academichonesty.anu.edu.au/. Given the weight of assessment on labs and assignments for this course the integrity of these will be checked closely. If I have reason to believe that students have colluded or contracted out assessment items I will both pursue the matter in terms of the academic integrity process and may also under 11(4) of the assessment rule use an oral examination for the student’s entire assessment. Assessment Due Dates Extensions will only be granted in unforeseeable circumstances beyond the control of the students, and will require supporting documentation (e.g. serious illness supported with medical certificates). Labs and assignments will be submitted via git lab and there is an expectation that students commit and push their changes as the assessment develops. As such there should always be some partial work to mark. The late penalty policy is that standard ANU policy of a 5% deduction per working day (or part thereof). This will apply for a maximum of 10 working days, after which the assingment will not be marked. That means if the deadline is 6pm Fri and you submit it a few hours after that, that counts as 5%. The next 5% penalty is applied after 6pm the following Monday. Updated: 08 Sep 2020/ Responsible Officer: Head of School/ Page Contact: Dr Eric McCreath Contact ANU Copyright Disclaimer Privacy Freedom of Information +61 2 6125 5111 The Australian National University, Canberra CRICOS Provider : 00120C ABN : 52 234 063 906 You appear to be using Internet Explorer 7, or have compatibility view turned on. Your browser is not supported by ANU web styles. Learn how to fix this Ignore this warning in future
