Assessments

The assessment is divided into three major components, namely a final exam and two coding assignments. The weightings of each component are designated above. The Final exam will be held in rooms designated by the university during the exam period. Exams will be on iLearn. Questions will likely include short answer, fill in the blank, and multiple choice. More details will be posted on iLearn later in the term.

The coding assignment will be divided into two major subcomponents or labs, with lab 1 due mid semester (week 7) and lab 2 due at the end of the term (week 13). Each lab will have a code contribution component. Each lab will also have a viva component as part of the assessment where you will be asked to explain your code. See iLearn for more details. Lab assignments will primarily use the C programming language, but may include other components involving Makefiles, scripting, etc.  

Late Assessment Submission

Late assessments are not accepted in this unit unless a Special Consideration has been submitted and approved.

Requirements to Pass this Unit 

Whilst there are a number of learning activities and assessments that make up the unit, in order to pass the unit the only requirement is that you achieve a total mark equal to or greater than 50%.

There are no hurdle requirements for the unit. 

Assessment Tasks

Name	Weighting		Due
Final exam	50%		Exam Period
Assignment 1	25%		Week 7
Assignment 2	25%		Week 13

Final exam

Assessment Type ¹: Examination Indicative Time on Task ²: 40 hours. Due: Exam Period. Weighting: 50%.

An examination allows us to individually and securely assess student's mastery of the coursework material.

On successful completion you will be able to:

• Demonstrate an ability to apply resource management concepts and principles to application design and execution (CPU, memory, storage/files, network/I/O, processes).
• Explain the structure/architecture and function of an Operating System.
• Demonstrate an understanding and ramifications of security and fault isolation.
• Demonstrate an understanding of virtualisation concepts.

Assignments 1 and 2

Assessment Type ¹: Practice-based task Indicative Time on Task ²: 29 hours each. Due: Week 7 and 13. Weighting total: 50%.  Release dates: Assignment 1 released by week 2 by Friday 11:55 pm, Assignment 2 released by week 7 Friday 11:55 pm.

A semester-long programming task where students put all their skills to work creating operating system components or modules.

On successful completion you will be able to:

• Demonstrate an ability to apply resource management concepts and principles to application design and execution (CPU, memory, storage/files, network/I/O, processes).
• Develop software programs that support concurrency and multi-threading.
• Develop a simple device driver that demonstrates the connection between operating systems and hardware.
• Demonstrate an understanding and ramifications of security and fault isolation.
• Demonstrate an understanding of virtualisation concepts.

¹ If you need help with your assignment, please contact:

• the academic teaching staff in your unit for guidance in understanding or completing this type of assessment
• the Writing Centre for academic skills support.

² Indicative time-on-task is an estimate of the time required for completion of the assessment task and is subject to individual variation

 

Classes 

Each week you should attend two hours of lectures, and a two hour practical workshop. For details of scheduled classes consult publish.mq.edu.au. 

Note that practicals workshops (lab sessions) commence in week 1. The week-by-week details of the practical (lab) classes will be available from iLearn. 

You must attend the practical that you are enrolled in. 

Textbook and Reading Materials 

Required Text Book 

"Operating Systems Concepts" 10th edition, by Silberschatz, Gagne and Galvin. 2021. We will assign weekly readings from the textbook during lecture and/or on iLearn. 

The text book is available in electronic form online, or you can purchase a printed copy from a book seller of your choice. It may be available in the Library. 

Recommended Text 

"The C Programming Language" 2nd edition, Brian W Kernighan and Dennis M Ritchie, Prentice-Hall 1988. 

This small book is the classic reference on C programming. 

Unit Websites 

COMP2291 / COMP6291 is administered via iLearn (http://ilearn.mq.edu.au/). 

This unit outline can be found in the university's unit guides 

We will use iLearn as our main platform for making announcements, posting assignments, releasing lecture slides and other content, submitting assignments, conducting exams, and posting results. We will use the announcements forums on iLearn to post important messages to the class. Students may ask questions in a separate general iLearn forum, where we will answer them. 

Lecture Recordings 

Digital recordings of lectures may be available. They will be linked from iLearn. 

Technologies Used and Required 

COMP2291 / COMP6291 is a BYOD (Bring Your Own Device) unit. You will be expected to bring your own laptop computer (Windows, Mac, or Linux) to the workshop, install and configure the required software, and incorporate secure practices into your daily work (and play!) routines. 

General Notes 

In this unit, you should do the following:

• Review recorded lecture materials. 

• Attend your weekly Practical session. 

• Attend lectures, take notes, ask questions. 

• Work on any assignments that have been released. 

Note that Workshops commence in week 1.

Students will attend weekly workshops in person, where they will receive additional explanations on class assignments and topics, and may be asked to explain their code in vivas, etc. Students should use these workshops to ask questions of their tutor.

Communication Methods in COMP2291 / COMP6291 

All announcements about unit-related matters will be communicated through iLearn. It is the student's responsibility to ensure they check iLearn announcements, forums, and other sections regularly. 

Students are encouraged to use the iLearn forums for asking questions about unit content and concepts. Where questions are about specific details in an assessment submission. 

Emails to the convenor, lecturer and/or tutors need to be preceded with a title identifying the class: COMP 2291 or 6291.  Any one-on-one commiunication with unit staff that is via email must be done through the student's official university email account (the one ending with '@students.mq.edu.au'). There may be occasions where unit staff will email a student directly to their @students.mq.edu.au email address. It is the student's responsibility to ensure they check their official university email regularly for communications from the university staff. 

Students may contact the convenor at the posted email above to have questions that cannot be otherwise answered by tutors or in the general forum, such as questions about policy in the class, but should avail themselves first of the general forum and tutors at their workshops to have technical questions about their assignments answered. 

Results will be released on iLearn in a timely manner, subject to certain acceptable delays such as accommodating special consideration late assessments.

Drop-In Centre 

There may be support at the Drop-In Centre in 4RPD.  Please contact them for more details.

The tentative weekly schedule is as follows, and may be subject to change. See iLearn for more details. 

Week 1: Introduction to C and OS  

Weeks 2-3: Processes, threads, synchronization and deadlock 

Week 4: CPU Scheduling 

Weeks 5-6: Virtual memory 

Weeks 7-8: Input/Output 

Weeks 9-10: Storage and File Systems 

Week 11: Networking and Security 

Week 12:  Virtual Machines 

Week 13: Review 

Changes from the prior offering include the following:

• Remove midterm exam
• Create cumulative final exam
• Remove weekly quizzes
• Separate lab assignment into two separate coding projects