ITX8040 - Redigeerimiste ajalugu

Olaf: /* Schedule */

2016-01-17T19:09:06Z

Schedule

Olaf: /* 19.01 */

2016-01-17T11:24:22Z

19.01

Olaf: /* 19.01 */

2016-01-17T10:55:41Z

19.01

Olaf: /* 20.10 */

2016-01-17T10:22:39Z

20.10

Olaf: /* 20.10 */

2016-01-17T09:25:55Z

20.10

Olaf: /* Guidelines on Presentations */

2016-01-16T12:20:20Z

Guidelines on Presentations

Olaf: /* Schedule */

2016-01-16T12:18:58Z

Schedule

Olaf: /* Schedule */

2016-01-16T11:52:43Z

Schedule

Olaf: /* Schedule */

2016-01-13T08:08:44Z

Schedule

Olaf: /* 12.01 */

2016-01-03T15:40:19Z

12.01

@@ 97. rida: / 97. rida: @@
 * Carlos
 * Raimo
 === 12.01 ===
@@ 105. rida: / 107. rida: @@
 === 19.01 ===
 * Tõnu
 * Akashkumar
 * Rashadul
 * Mikk
 * Avtandil
 * Taavi T.
 * Vijay
 * Jaanus
 === Guidelines on Presentations ===

@@ 116. rida: / 116. rida: @@
 * Wael
 * Vijay
-* Jaanos
+* Jaanus
 * Andrea
 * Luis

@@ 106. rida: / 106. rida: @@
 === 19.01 ===
-* Tabu
+* Tõnu
 * Akashkumar
 * Karl
@@ 119. rida: / 119. rida: @@
 * Andrea
 * Luis
 === Guidelines on Presentations ===

@@ 40. rida: / 40. rida: @@
 * Sho
-* Nahum (ois)
+* Nahum
 === 27.10 ===

@@ 40. rida: / 40. rida: @@
 * Sho
-* Nahum
+* Nahum (ois)
 === 27.10 ===

@@ 125. rida: / 125. rida: @@
 The purpose of the seminar is two-fold: (a) share ideas about recent research in the field of cyber security; and (b) provide help with progress on the MSc thesis.  Conducting an academic literature review is an essential part of writing a MSc thesis and typically also influences the thoughts on what to write in the thesis.  For this reason the literature review should be done early on.  And while reviewing academic literature (probably) never stops until the final version of the thesis is submitted, the majority of the papers will/should probably be read in the beginning of the process.  The work on the thesis then goes a step further and everyone will bring their unique research contribution to the table (written-up in the form of the MSc thesis).
-Of course, it is an option for this seminar to present your own research work (for example, practice the MSc defence).  However, generally this is '''not''' the expected level.  It is more expected that the presenter reviews and presents '''one'''( or two) selected paper(s).  The presentation should give an overview of what research question/problem the authors of that paper tried to solve, it should present a bit of context (e.g., why is that research question interesting and relevant) and the presentation should at least go a bit deeper at one aspect discussed in the paper (e.g., highlight the methodological approach used by the authors / how the problem was solved).  The student should be able to present the paper, as if it would be his/her own paper, which means a good understanding of the problem space in which context the paper was written.  Therefore, it is '''not''' sufficient to just read one or two papers and superficially present the work of the authors.  It should be appreciated that to fully understand the work the authors (of the selected paper) have done, several other related work papers need to be read.  Those other papers don't have to be presented in detail, but they should influence the presentation in a way that the student is confident in their understanding of the area of research.  A slide should be included in the presentation that lists the most relevant papers read in preparation for the talk.
+Of course, it is an option for this seminar to present your own research work (for example, practice the MSc defence).  However, generally this is '''not''' the expected level.  It is more expected that the presenter reviews and presents '''one''' (or two) selected paper(s).  The presentation should give an overview of what research question/problem the authors of that paper tried to solve, it should present a bit of context (e.g., why is that research question interesting and relevant) and the presentation should at least go a bit deeper at one aspect discussed in the paper (e.g., highlight the methodological approach used by the authors / how the problem was solved).  The student should be able to present the paper, as if it would be his/her own paper, which means a good understanding of the problem space in which context the paper was written.  Therefore, it is '''not''' sufficient to just read one or two papers and superficially present the work of the authors.  It should be appreciated that to fully understand the work the authors (of the selected paper) have done, several other related work papers need to be read.  Those other papers don't have to be presented in detail, but they should influence the presentation in a way that the student is confident in their understanding of the area of research.  A slide should be included in the presentation that lists the most relevant papers read in preparation for the talk.
 Overall, the presentation should be very brief:  ~ 12 minutes for the presentation of the selected paper.  This must include the research hypothesis of the presented paper, methodology, results and validation (what did the authors do to believe their results are accurate, has there been other work that questions those findings, etc.).  Note that the student presenting does not necessarily have to have the same opinion as the authors of the selected paper.  Going beyond the paper is very good, as long as the view-point of the authors and methodology/some results can still be communicated.  If the presenter has already his/her own research hypothesis (which is expected for semester 3 students, but not required for 1st-year students), the student is welcome to include that in the presentation as well and illustrate how the given paper presented has influenced the thesis process/how the paper relates to the thesis overall.

@@ 36. rida: / 36. rida: @@
 * Martin
 * Allan (no show!)
 === 20.10 ===
@@ 98. rida: / 97. rida: @@
 * Carlos
 * Raimo
 === 12.01 ===
 * Kaspar
 === 19.01 ===

@@ 30. rida: / 30. rida: @@
 * Allyson
 === 13.10 ===
@@ 37. rida: / 36. rida: @@
 * Martin
 * Allan (no show!)
-* (free)
 === 20.10 ===
@@ 43. rida: / 42. rida: @@
 * Sho
 * Nahum
 === 27.10 ===
@@ 64. rida: / 61. rida: @@
 * Michal
 * Shota
 === 17.11 ===
@@ 104. rida: / 100. rida: @@
-=== 12.01  16.00-17.00 only ===
+=== 12.01 ===
 * Kaspar
@@ 114. rida: / 110. rida: @@
 * Karl
 * Rashadul
 * Danish
 * Mikk