Clark Thomborson University of Auckland

1. Software SecurityCompSci 725Handout 9: Oral Presentations, Projects and Term Reports5 August 2005(Slides 8 & 9 were revised 16 August 2005) Clark Thomborson University of Auckland Presentations

2. Assessment (copied from Handout 5) • 15% seminar, on one of the required readings: • You must prepare a slideshow, appropriate for an 8-minute oral presentation, focussing your classmates’ attention on one important topic. (7%) • You must present a draft of your slideshow to the instructors, one week before your scheduled presentation date. The instructors will give you some ideas on how to improve your presentation. (1%) • You must present your slideshow in 6 to 10 minutes. (2%) • There should be at least one thought-provoking question in your slideshow. (2%) • You must participate in the question-and-answer session run by the instructors after your presentation. (3%) Presentations

3. Your Oral Presentation • You should prepare six or seven slides: • A title slide, with full bibliographic information on the article you are presenting; • A one-sentence summary of the article; • Two or three critical or appreciative comments, indicating why you think your fellow students should read this article and what important results (or mistakes) they should watch out for; • An explanation (2 or 3 slides) of one of your comments; • A question to stimulate discussion • Your presentation should take six to ten minutes, excluding questions & discussion. Presentations

4. Critical and Appreciative Comments • An article might offer a good explanation, taxonomy, experimental measurement, security analysis, technology, or proof of correctness. • Your appreciative comments should indicate WHAT you think is good and WHY you think it is good. • Your critical comment might point out an error in an equation, an important part of an experimental setup that isn’t disclosed, or a limitation on the scope of applicability of the claimed results. • You should write at least one critical comment, and at least one appreciative comment. • Don’t include more than three comments in your presentation (perhaps two appreciative comments and one critical one). Presentations

5. How to Recognize a Good Question • Your question should challenge your fellow students to compare/contrast/combine the comments in your oral presentation, with • the articles (if any) that have been presented previously in this class, and • general knowledge of computer science. • Your question should be answerable by anyone who • has a broad undergraduate education in computer science, and • is able to reflect critically and appreciatively on all assigned readings, all oral presentations, and all prior discussions in COMPSCI 725 lecture periods. • Your question should stimulate creativity and analysis, not just memory. Presentations

6. Preparing your Oral Presentation • Write some critical & appreciative comments after reading your article very carefully. • Construct a first draft of your presentation: use PowerPoint or your favourite presentation builder (but not MS Word!). • Rehearse your draft presentation by yourself, and then rehearse with a friend. • Revise your draft presentation after each rehearsal. Add a question if you haven’t done so already. • Deliver your draft presentation at a tutorial, at least one week prior to your scheduled presentation date at COMPSCI 725 lectures. (Carry your presentation file to the tutorial room on a floppy disk or CD.) • Prepare a final version of your presentation slides, after hearing comments from the lecturer and other student(s) at tutorial. • Carry your final-version presentation slides to the COMPSCI 725 lecture on a floppy disk or CD, on the day scheduled for your presentation. Your presentation file will be mounted on the class website. • You’ll probably spend 10 hours preparing a 10-minute presentation! Presentations

7. Your Lecturer’s Expectations • Presenters should show appreciative and critical understanding of their article, through • the contents of their slides • their oral comments when presenting their slides, and • their handling of the discussion. • Non-presenters should have read the article before the presentation begins. • All students should have a working knowledge of what was presented & discussed in class. (This will be tested in your final examination.) Presentations

8. Your Term Paper or Project • When reading your article for your oral report, you should start thinking about how to use it as a basis for a term paper. • Compare/contrast your article’s technology (or analysis or research finding) to some other published work. • Discover another article, describing an extension or application of your first article’s technology. • Identify a point of confusion or difficulty in your article and explain this point “better than the author did” (with appropriate references). • You may choose to do a project report instead of a term paper, showing your competence & creativity in some practical application of one or more security techniques. Presentations

9. Requirements for Reports • Your report should consist of nine to thirteen pages of 12-point type with generous margins and 1.5 line spacing. • If you use someone else’s words, put these in quotation marks and add a reference to your source. (If you plagiarise, you will receive a failing grade.) • Your term paper must show your critical & appreciative understanding of at least three professional publications. • At least one of these works must be a required reading for this course. • At least one of these works must *not* be a required reading. • You must cite and (at least briefly) discuss any other required class readings that are related to the topic of your paper. • A term project report must cite, and at least briefly discuss in the context of your report, at least two of the required class readings. • Try to match the style of one of the articles you read in this class. • Technical words must be spelled and used correctly. • You should use a spell-checker and a grammar checker (e.g. MS Word), however we will not mark you down for grammatical mistakes and spelling errors on non-technical words (if your meaning is clear). • Reports are due at 4pm on the last day of lectures. Presentations

10. Assessment of Papers & Projects • 25% of your final mark • You may write a 10-page term paper, demonstrating your critical and appreciative understanding of at least three professional publications relevant to software security, with full and accurate bibliographic references. • You may write a 10-page project report, showing your competence and creativity in practical techniques of software security. • Technical words must be spelled and used correctly. • No plagiarism! Presentations

11. Final Examination • 60% of your total marks • To pass this examination, you must show good understanding of the required readings (approx. 400 pages of technical articles, plus a couple of introductory chapters from textbooks) • We’ll administer a 1-hour “practice midterm” (ungraded) during the term, tentatively on Friday 2 October. • You will be allowed two hours for your final exam. (There may be a brief “reading period” before the examination begins, during which you may read the examination but you may not write anything.) Presentations

12. Assignments #1 and #2 • By 5pm Friday 19 August 2005, you must send email to cthombor@cs.auckland.ac.nz containing • A one-sentence description of your term paper or project. • By 5pm Friday 16 September 2005, you must send a file to cthombor@cs.auckland.ac.nz, for display on the class website, containing • the title of your term paper or project, • your name, • (for term papers only) a one-paragraph synopsis, and a list of references, • (for project reports only) a goal statement, a one-paragraph discussion of your design methodology, and a list of any resources you require that you haven’t already obtained. • Examples from last year are available at http://www.cs.auckland.ac.nz/compsci725s2c/archive/2004/assignments/ Presentations