0% found this document useful (0 votes)
203 views17 pages

Introduction Cont.: Compsci 726 Network Defence and Countermeasures

This document provides guidance for students presenting individual seminars as part of the COMPSCI 726 course. It outlines expectations for seminar presentations, including time limits, grading criteria, and tips for effective presentations. Students are expected to critically analyze assigned research articles and present summaries in 7-10 slides. Presentations will be followed by Q&A sessions. Group reports on selected topics are also required, with guidelines provided for report structure and formatting.

Uploaded by

Michael C
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
203 views17 pages

Introduction Cont.: Compsci 726 Network Defence and Countermeasures

This document provides guidance for students presenting individual seminars as part of the COMPSCI 726 course. It outlines expectations for seminar presentations, including time limits, grading criteria, and tips for effective presentations. Students are expected to critically analyze assigned research articles and present summaries in 7-10 slides. Presentations will be followed by Q&A sessions. Group reports on selected topics are also required, with guidelines provided for report structure and formatting.

Uploaded by

Michael C
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

INTRODUCTION CONT.

Lecture 2
COMPSCI 726
Network Defence and Countermeasures

Muhammad Rizwan Asghar

July 21, 2021


SEMINAR: INDIVIDUAL

▪ Grading
– 4% introduction (motivation, background, and problem)
– 4% solution (idea, details, and results)
– 4% criticism (summary, issues, and improvements)
– 3% review of one assigned presentation

▪ Duration
– Up to 2 presentations per lecture
– Every presenter will get ~20-25 minutes
▪ 15 minutes for presentation (a strict limit!)
▪ ~5-10 minutes for QA

▪ Feedback
– Lecturers
– Students

2
SEMINAR TIME AND PRESENTATION

▪ You will have 15 minutes for your presentation

▪ There are ~5-10 minutes for QA and discussion

▪ On average, you can have around 7-10 slides


– Introduction: 2-3 slides
– Solution: 2-3 slides
– Criticism: 2-3 slides

▪ Your slides should be neither too simple nor too dense

▪ Use visuals

▪ Assume that your audience might not know the article


3
SOME TIPS ABOUT SEMINAR

▪ Minimise reading from slides or notes!


▪ Present article in your own words
▪ Your presentation will be uploaded on the course
website so that others can benefit from it
▪ To save time, you should copy your presentation to the
PC in the class before the lecture
▪ Alternatively, if you are using your laptop, make sure
you connect and check it before the lecture
▪ Be on time!

4
INDIVIDUAL SEMINAR

▪ It is not a group seminar

▪ You are responsible for your article

▪ Having said that, you can give a rehearsal talk


to your group member, if you want

▪ You should share your opinion in the criticism


part

5
HOW TO CRITICISE?

▪ Does your article meet expectations you have from it?

▪ If you were user of this system, would it work for you?


– Share your reasoning why yes or why not

▪ What would have you done differently if you could be


the author?

▪ Share limitations you identify

▪ Your ideas to address identified issues


6
GROUP REPORT

▪ Group size: 2
▪ Page limit: 7-10
▪ For your report (in PDF only), use the following format
– Times New Roman
– Font 12
– Single column
– Single line spacing
– 1 inch margin

▪ For grading purposes, you also have to submit


– Percentage contribution of each group member
– List of tasks each group member was involved in

7
STRUCTURE OF REPORT

▪ Abstract (~1 paragraph)


– Context (1 sentence)
– Problem (1 sentence)
– State-of-the-art (1 sentence)
– Solution (1 sentence)
– Novelty (1 sentence)

▪ Introduction (~1.5 to 2 pages)


– Context (1 paragraph)
– Problem (1 paragraph)
– State-of-the-art (1 paragraph)
– Solution (1 paragraph)
– Novelty

8
STRUCTURE OF REPORT (2)

▪ Related work (~1.5-2 pages)


– Highlight how your idea is different from existing research
– Cite 5 ‘strong’ research articles including at least one from this list
– One paragraph per research article

▪ Proposed idea (~2-3 pages)


– Core idea and details
– Bonus: experiment and comparison

▪ Conclusion (~0.5 page)


– Summary of your report (~1 paragraph)
– Future work (~1 paragraph)

▪ References

9
EXAM

▪ Lectures
▪ Lecture resources
▪ Seminars
– Including presented articles

▪ Class discussions
▪ Online exam
▪ 7-10 questions
– Each question might have sub-questions

▪ 2 hours

10
RECOMMENDED BOOK

▪ Network Security Essentials – Applications and


Standards
Fourth Edition
William Stallings
Prentice Hall
ISBN 0-13-706792-5

11
LECTURE UPLOAD POLICY

▪ Presentation slides will be uploaded after the lecture

12
CANVAS AND COURSE WEBSITE

▪ Canvas for almost everything


– [Link]

▪ We will try to make lecture recordings available within a


day after we receive recording links
– Note that we have requested to record all the lectures

▪ Course website for lectures and seminars


– [Link]

▪ Piazza
– [Link]

13
READING: HOW TO READ A
RESEARCH ARTICLE

▪ How to Read an Engineering Research Paper


William G. Griswold
CSE, UC San Diego
[Link]

▪ How to Read a Paper


S. Keshav
University of Waterloo
[Link]

▪ How to Read a Technical Paper


Jason Eisner (2009)
[Link]

14
READING: HOW TO PRESENT
A RESEARCH ARTICLE

▪ How To Make an Oral Presentation of Your Research


Center for Undergraduate Excellence
University of Virginia
[Link]
and-publish/presentation-tips

▪ Notes on Presenting a Paper


Matthew O. Jackson
[Link]

15
READING: HOW TO WRITE A REPORT

▪ How to Write a Research Paper


Charles King
[Link]
[Link]

▪ How to Write a Great Research Paper


Jon Turner
Computer Science & Engineering
Washington University
[Link]
[Link]

▪ Tips for Writing Technical Papers


Jennifer Widom
January 2006
[Link]

16
Questions?

Thanks for your attention!

17

You might also like