2 The University of Auckland - COMPSCI 725 S2 C

Computer Science


Lectures

This page was updated on 20 October 06.

Announcements

  • Princeton's Center for Information Technology Policy has released a white paper dated 13 September 2006 and a video describing their "Security Analysis of the Diebold AccuVote-TS Voting Machine".
  • Infoworld article referencing a technical report entitled "Nedap/Groenendaal ES3B voting computer: a security analysis", dated 5th October 2006, and authored by Rop Gonggrijp, Willem Hengeveld et al. of the English language website of the "We don't trust voting computers" coalition.
  • Handling absence or illness:
    1. If you must leave for family emergencies etc, PLEASE talk to the lecturer, or somehow get a message to the department. Very few problems are so urgent that we cannot be told quite quickly.
    2. For problems affecting assignments or tests, see the lecturer (or send email, or call on the telephone).  This must be done as soon as reasonably possible, if we are to make alternative arrangements that will prevent you from getting a poor mark on this test or assignment.
    3. For illness during exams (or other problems that affect exam performance) students MUST contact the Examinations Office within ONE WEEK of the last affected examination to apply for an aegrotat pass (for illness) or compassionate pass (other problems).  THE ONE WEEK LIMIT IS STRICTLY ENFORCED.  See the University's Current Students website, or the Computer Science Handbook.
    4. A lot of students have missed out on a whole semester of study because they just went away.  Many students have failed an examination because they did not report problems until they received the failing grade. In general, if there is a problem that will affect your study you should speak to someone as soon as possible.
    5. Students should sit the examination if at all possible, even if they do nothing much more than hand in a script with their name.
    6. It would also help if students read the examinations handbook that they receive, and double-check (triple-check?) the examination timetable.
  • Archived announcements.

Tentative Schedule

Note: the date listed for student presentation #x is the approximate date on which this presentation will occur; dates will be adjusted when students drop.  Students will be assigned numbers by a random process during the first week of classes.

  1. Week 1 (17 July - 21 July).  Select class representative
  2. Week 2 (24 July - 28 July). Select papers and dates for student oral presentations in Weeks 5-13.
  3. Week 3 (31 July - 4 August). Finalise the selection of papers and dates for student oral presentations.  Discuss how to prepare an oral presentation. Discuss term project requirements.
  4. Week 4 (7 August - 11 August).  Tutorial sessions: Students #1 - #4 give practice oral presentations. 
  5. Week 5 (14 August - 18 August). Student oral presentations #1 - #4: each presentation will be 10 minutes in length, with an 8-minute discussion period.  Tutorial sessions: Students #5 - #8 give practice oral presentations.
    • Assignment 1 due by email to instructor before lecture of Friday 18 August: Term paper or project proposal (one sentence).
  6. Week 6 (21 August - 25 August).  Student oral presentations #5 - #8. No lecture on Friday 25 August.

    Term break (28 August - 10 September)
     
  7. Week 7 (11 September - 15 September). Tutorial sessions: Students #9 - #12 give practice oral presentations. No lecture on Monday 11 September.
    • Assignment 2 due by email to instructor before lecture of Friday 15 September: first draft of title, synopsis and references (with complete bibliographic detail) for term paper; or goal statement of term project, list of software & hardware resources required and a plan for obtaining these, and proposed methodology.
    • [R17] M. Stamp, Information Security: Principles and Practice, John Wiley & Sons, Inc., September 2005, pp. 325-338.
    • Handout 11, Trusted Operating Systems (Mark Stamp's lecture slides).
  8. Week 8 (18 September - 22 September).  Student oral presentations #9 - #12. Tutorial sessions: Students #13 - #16 give practice oral presentations.
  9. Week 9 (25 September - 29 September). Student oral presentations #13 - #16. Tutorial sessions: Students #17 - #20 give practice oral presentations. No lecture on Monday 25 September and Wednesday 27 September.
    • Assignment 3 due Friday 29 September, by email to instructor, sent before lecture begins: title and abstract, for publication on class website; and a detailed outline of your term paper or project report.
    • Handout 13: practice final exam, administered in class on Friday 29 September.
  10. Week 10 (2 October - 6 October). Monday: student oral presentations #17 - #20. Tutorial sessions: Students #21 - #24 give practice oral presentations. 
  11. Week 11 (9 October - 13 October). Student oral presentations #21 - #24. Tutorial sessions: cancelled. 
  12. Week 12 (16 October - 20 October). Friday: discussion of student answers to sample final exam.
  13. Final Examination. Date and time to be arranged. This will be a 2-hour examination, with a brief settling-in and exam-reading period before the examination begins. Closed book, no calculators. The location will be announced on the morning of the exam (and possibly as early as 5pm on the day prior to the exam), at nDeva, at the Exams Office website, and by hardcopy postings on campus.


Apply now!


Handbook

Postgraduate study options

Computer Science Blog



Please give us your feedback or ask us a question

This message is...


My feedback or question is...


My email address is...

(Only if you need a reply)

A to Z Directory | Site map | Accessibility | Copyright | Privacy | Disclaimer | Feedback on this page