Note: This unit is an archived version! See Overview tab for delivered versions.
COMP5211: Algorithms (2011 - Semester 1)
Unit: | COMP5211: Algorithms (6 CP) |
Mode: | Normal-Day |
On Offer: | Yes |
Level: | Postgraduate |
Faculty/School: | School of Computer Science |
Unit Coordinator/s: |
Wolle, Thomas
|
Session options: | Semester 1, Semester 2 |
Versions for this Unit: | |
Site(s) for this Unit: |
http://thomaswolle.net/COMP5211/index.html |
Campus: | Camperdown/Darlington |
Pre-Requisites: | None. |
Brief Handbook Description: | The study of algorithms is a fundamental aspect of computing. This unit of study covers data structures and algorithms, and it gives an overview of the main ways of computational thinking from simple list manipulation and data format conversion, up to shortest paths and cycle detection in graphs. Students will gain essential knowledge in computer science, including basic concepts in data structures, algorithms, and intractability, using paradigms such as dynamic programming, divide and conquer, greedy approaches, local search, and randomisation, as well NP-hardness. |
Assumed Knowledge: | This unit of study assumes that students have general knowledge of mathematics (especially Discrete Math) and problem solving. Having moderate knowledge about Data structure can also help students to better understand the concepts of Algorithms will be taught in this course. Some knowledge of computer programming is required. |
Lecturer/s: |
Wolle, Thomas
|
||||||||||||||||||||
Timetable: | COMP5211 Timetable | ||||||||||||||||||||
Time Commitment: |
|
||||||||||||||||||||
T&L Activities: | Lecture: Lecture Tutorial: Tutorial |
Attributes listed here represent the key course goals (see Course Map tab) designated for this unit. The list below describes how these attributes are developed through practice in the unit. See Learning Outcomes and Assessment tabs for details of how these attributes are assessed.
Attribute Development Method | Attribute Developed |
Understand main concepts of Algorithms | Design and Problem Solving Skills (Level 4) |
For explanation of attributes and levels see Engineering/IT Graduate Attribute Matrix 2009.
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.
Design and Problem Solving Skills (Level 4)Assessment Methods: |
|
||||||||||||||||||
Assessment Description: |
Homework Assignment: Every week, small assignments are handed out and/or announced that are to be done by the students as homework. These homeworks have to be independently solved (approximately) within one week, and handed in by email. These homeworks will be marked, and these marks contribute 50% to the final mark of the course. Handing in homework as a group of students is not allowed. However, students are allowed to discuss homework and class material with peers. Also, using additional resources, such as (other) books, the Internet, scientific papers etc. is allowed. When formulating and writing down solutions, students have to work alone, and they have to cite all the sources/references that were used. Representing other people`s work as your own, is plagiarism and is in violation of university policies. Note that we reserve the right not to hand out homework assignments strictly every single week. Also, we reserve the right to have an oral examination of the assignments if we believe it is necessary (for instance, when there is too much similarity between two students homework, etc.). Final Exam: Written Final Exam. The mark of the exam contributes 50% to the final mark of the course. It is a policy of the School of Information Technologies that in order to pass this unit, a student must attain a mark of at least 40% in the written examination as well as any other major component of Assessment nominated by the lecturer. A student must also achieve an overall final mark of 50 or more. Any student not meeting these requirements can achieve a maximum mark of no more than 45. Late work: In the interest of fairness to all students, the School of Information Technologies policy states that late work cannot be accepted. In exceptional cases late work must be submitted directly to the unit of study coordinator accompanied by an application for Special Consideration as outlined on page 16 of the School of Information Technologies Postgraduate Enrolment Guide. |
||||||||||||||||||
Grading: |
|
||||||||||||||||||
Policies & Procedures: | IMPORTANT: School policy relating to Academic Dishonesty and Plagiarism. In assessing a piece of submitted work, the School of IT 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 Faculty policies regarding academic honesty and plagiarism, special consideration and appeals in Engineering and Information Technologies can be found on the Faculty's policy page at http://www.eng.usyd.edu.au/policies"> http://www.eng.usyd.edu.au/policies. School and Faculty policies are governed by Academic Board resolutions whose details can be found on the Central Policy Online site at http://www.usyd.edu.au/policy/"> http://www.usyd.edu.au/policy/. Policies regarding assessment formatting, submission methods, late submission penalties and assessment feedback depend on the unit of study. Details of these policies, where applicable, should be found above with other assessment details. |
Prescribed Text/s: |
Note: Students are expected to have a personal copy of all books listed.
|
Online Course Content: | http://thomaswolle.net/COMP5211/index.html |
UniKey Login Required
Only current University of Sydney students may view this content.
If you are an existing student, please login with your UniKey here.
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 |
Design and Problem Solving Skills (Level 4) | Yes | 0% |
These goals are selected from Engineering/IT Graduate Attribute Matrix 2009 which defines overall goals for courses where this unit is primarily offered. See Engineering/IT Graduate Attribute Matrix 2009 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.