COMP2310 - assessment - CECS - ANU Skip navigation Computer Science Courses ANU College of Engineering & Computer Science EXPLORE ANU » Home About Study Research Giving Alumni Current students Staff News Events Maps Library Jobs ANU College of Arts & Social Sciences ANU College of Asia & the Pacific ANU College of Business & Economics ANU College of Engineering & Computer Science ANU College of Law ANU College of Medicine, Biology & Environment ANU College of Physical & Mathematical Sciences » more academic areas A-Z INDEX » A B C D E F G H I J K L M N O P Q R S T U V W X Y Z Search query Search button Computer Science Courses ANU College of Engineering & Computer Science Computer Science Courses School of Computer Science Current students Courses list COMP2310 Home COMP2310 P&C Entry COMP6310 P&C Entry Course Outline Entry Schedule Lectures Practicals Assignments Assessment Announcements Discussion Forum Textbooks and Reading Useful Links Past Exams Assistance Related sites Wattle Forums ANU College of Engineering & Computer Science Current students (ANU) COMP2310/6310 CDS: Assessment 2014 Proposed Assessment Scheme The proposed assessment scheme for Concurrent & Distributed Systems course in 2013 will be in the following parts: Assignments: 30% # weight wk out wk due 1 18 3 7 2 12 8 12 These will contain a significant programming component, plus a brief report. Assignment 1 will have a modelling component (FSP), with programming in Java. Assignment 2's programming component can be in C or Java. Quizzes and Exercises during Practical Sessions: 10% Eight of the sessions will have on-line quizzes and/or tutor-assessed exercises with a weight of 2%. The best 5 such scores will be added to compute this component. There will be no extensions for these components, as there is allowances to miss up to 3 sessions due to mischance (and you should not miss a session for any other reason). Mid-Semester Examination: 10% (proposed date: week 8) One A4 page of handwritten notes (both sides) is permitted; a calculator is not permitted. Final Lab Examination*: 50% One A4 page of handwritten notes (both sides) is permitted. These components are then added to give your final mark. This may then be scaled to give your overall course mark and grade. In particular, the final marks may be moderated by the Research School of Computer Science examiners meeting. Notes: We will discuss the proposed scheme in weeks 1 and 2. There is some scope for flexibility. *What is a Lab Examination? A Lab Exam is held in the CSIT student labs, which in `exam mode'. This means that you log in as normal but you will get a different home directory, which is uncustomized and only contains files relating to the exams. You put your answers for each question into the indicated files; these are collected and marked after you log out. Further details are here Why have a Lab Exam? A Lab Exam can have exactly the same style questions as a written one, except you type your answers instead of writing them. However, programming-related questions can now be sharpened well beyond what is possible in a written exam, testing practical skills such as debugging. Furthermore, the scope of questions can be broadened, since cut-and-paste from given code and on-line documentation can allow a relatively voluminous answer to be produced quickly. Extensions and Late Penalties for Assignments In general, there will be no extensions for assignments, the exception being for illness serious enough to keep you in bed, supported by a medical certificate. Other similarly un-foreseeable and serious circumstances may be considered (if similarly verified). Work and sporting commitments are not normally sufficient grounds. The failure of external computer systems used to undertake the assignment will not be considered. If you think you have grounds for an extension, you should notify the course coordinator as soon as possible and provide written evidence in support of your case (e.g. medical certificate). The course coordinator will then decide whether to grant and extension and inform you as soon as practicable. Extensions may be granted to a date that is not more than 1 week from the nominal deadline. Without an explicit extension from the course co-ordinator, late assignments will be penalised at the standard RSCS rate, which is 20% per day (for a maximum of 5 days, after which the assignment will not be accepted). The penalty will be calculated on an hourly basis. In the case of multiple files submitted at separate times, the penalty is calculated from the time of submission of the last file. There is a maximum period of 2 weeks after the return of a marked assignment (or quiz) in which the mark may be disputed. Plagiarism and Assisting Plagiarism in Assignments Assignments should be assumed to be individual. For the general RSCS policy, which applies to this course, you should read the chapter in the RSCS Student Handbook that discusses assessment (Chapter 6, pages 17-25), particularly the sections headed Misconduct in examinations (which also applies to assignments and other forms of assessment) and Guidelines for assignments. Please note the following: producing a solution with the aid of another's solution is cheating! providing a solution to another student is therefore assisting cheating and will be treated the same as cheating. working in close groups throughout the development of an assignment solution where members are inspecting each others' solutions is highly dangerous! It is highly likely to lead to unacceptable levels of collaboration and give members of the group an unfair advantage. Updated: 24 October 2014 / Responsible Officer: JavaScript must be enabled to display this email address. / Page Contact: JavaScript must be enabled to display this email address. / Powered by: Snorkel 1.4 Contact ANU Campus Map Copyright Disclaimer Privacy Freedom of Information +61 2 6125 5111 The Australian National University, Canberra CRICOS Provider : 00120C ABN : 52 234 063 906
