MScSeminar 2017 Autumn - Redigeerimiste ajalugu

Juhan: /* November 17: Written related work section */

2017-10-20T09:32:33Z

November 17: Written related work section

Juhan: /* November 10: Written related work section */

2017-10-20T09:30:46Z

November 10: Written related work section

Juhan: /* Oct 6: One page problem statement */

2017-10-20T09:11:14Z

Oct 6: One page problem statement

Juhan: /* Oct 6: One page problem statement */

2017-09-22T10:28:24Z

Oct 6: One page problem statement

Juhan: /* Meetings */

2017-09-22T09:14:29Z

Meetings

Juhan: /* Meetings */

2017-09-22T09:07:32Z

Meetings

Juhan – 22. september 2017, kell 09:01

2017-09-22T09:01:15Z

Juhan: /* Meetings */

2017-09-08T09:25:30Z

Meetings

Juhan – 8. september 2017, kell 09:06

2017-09-08T09:06:22Z

Juhan: Uus lehekülg: '=Deadlines= ==Oct 6 Feb 21: One page problem statement== * Peer review of the problem statement, i.e. everybody will be required to read 2 problem statements by fellow students...'

2017-09-08T09:00:04Z

Uus lehekülg: '=Deadlines= ==Oct 6 Feb 21: One page problem statement== * Peer review of the problem statement, i.e. everybody will be required to read 2 problem statements by fellow students...'

Uus lehekülg

=Deadlines=

==Oct 6 Feb 21: One page problem statement==

* Peer review of the problem statement, i.e. everybody will be required to read 2 problem statements by fellow students and give detailed feedback. Deadline October 20. To be submitted to ained.ttu.ee, to the course ITX8302.

Questions that need to have answers:

# Is it clear what is going to be done? (Kas on selge, mida töös teha plaanitakse?)
# Have you stated the goals that you will attempt to achieve by doing the work? (Kas on püstitatud töös saavutatavad eesmärgid ja oodatav tulemus?)
# Is the student aware of alternative solutions and background? (Kas tudeng on teadlik valdkonna tasutast ja alternatiivsetest lahendustest?)
# Is it stated how the goals are going to be achieved? (Kas on kirjeldatud, kuidas plaanitakse eesmärke saavutada?)
# Is it clear how the results will be validated? Is it valid from the engineering point of view? (Kuidas plaanitakse kontrollida, kas saavutatud tulemus on adekvaatne? Kas see võrdlus on planeeritud insenerlikult?)
# How current/relevant/novel the topic is? (Kui aktuaalne/uudne teema on?)
# Is the planned solution realistic? (Kas planeeritav lahendus on realistlik?)
# How complex the planned task is on the scale easy/average/hard? (Kui keeruline ülesanne on (skaalal lihtne / keskmine / keerukas)?)
# Is the problem suitable for a MSc thesis? (Kas ülesanne on sobiv magistritöö raames lahendamiseks?)

==November 10: Written related work section==

The related work and background description should be at least 4 pages and should contain at least 15 references. The references need to be reliable and useful from the point of view of your thesis.

It is recommended that you add the 1 page problem statement to the document so that it will be possible to understand if the background and related work provided is relevant for the problem to be solved.

* Peer review of the related work, i.e. everybody will be required to read 2 related work submissions and give detailed feedback. Deadline November 24.

==November/December: Submission of the draft of the thesis==

By the time you give the talk you should submit your current draft of the thesis to the appropriate assignment in ITX8302 at https://ained.ttu.ee.

==Grading==

* 8% of 100%: 1-page problem statement, another 8% of 100% for giving feedback to problem statements submitted by others.
* 45% of 100%: background and related work submission.
* 9% of 100%: feedback to background and related work submissions by other students (3 each).
* 30% of 100%: Your mock defence talk and participation in seminars where other students give talks. Note that you will need to submit your current draft of the thesis by the time you give the talk. The draft is not marked, but it will be used for questions after your talk.

The final grade will be calculated as follows from the sum of the above results:

* 90% or more: 5
* 80% or more: 4
* 70% or more: 3
* 60% or more: 2
* 50% or more: 1
* less than 50%: 0

=Meetings=

* Sept 8: Introduction
* Sept 15: Discussion of write literature review. Review of the referencing guide provided by the university: [http://www.ttu.ee/public/i/infotehnoloogia-teaduskond/Tudengile/IT_teaduskond_Allikate_kasutamise_juhend.pdf Allikate kasutamise juhend], [http://isites.harvard.edu/icb/icb.do?keyword=k70847&tabgroupid=icb.tabgroup106849 Using sources].

@@ 27. rida: / 27. rida: @@
 It is recommended that you add the 1 page problem statement to the document so that it will be possible to understand if the background and related work provided is relevant for the problem to be solved.
-* Peer review of the related work, i.e. everybody will be required to read 2 related work submissions and give detailed feedback. Deadline November December 1.
+* Peer review of the related work, i.e. everybody will be required to read 2 related work submissions and give detailed feedback. Deadline December 1.
 ==November/December: Submission of the draft of the thesis==

←Vanem redaktsioon		Redaktsioon: 20. oktoober 2017, kell 09:11
3. rida:		3. rida:
	==Oct 6: One page problem statement==		==Oct 6: One page problem statement==

−	* Peer review of the problem statement, i.e. everybody will be required to read 2 problem statements by fellow students and give detailed feedback. Deadline October 20. To be submitted to ained.ttu.ee, to the course ITX8302.	+	* Peer review of the problem statement, i.e. everybody will be required to read 3 problem statements by fellow students and give detailed feedback. Deadline October 29. To be submitted to ained.ttu.ee, to the course ITX8302.

@@ 53. rida: / 53. rida: @@
 * Sept 15: Discussion of write literature review. Review of the referencing guide provided by the university: [http://www.ttu.ee/public/i/infotehnoloogia-teaduskond/Tudengile/IT_teaduskond_Allikate_kasutamise_juhend.pdf Allikate kasutamise juhend], [http://isites.harvard.edu/icb/icb.do?keyword=k70847&tabgroupid=icb.tabgroup106849 Using sources].
 * Sept 22: How to write reviews? [http://larc.unt.edu/ian/pubs/referee.pdf Ian Parberry's adivce], [http://se.ethz.ch/~meyer/publications/online/whysign/ Why some people sign their reviews?], [http://users-cs.au.dk/danvy/communication/cics_2015-09-14.pdf Olivier Danvy's slides on reviewing]
 =Thesis topics=
 [https://livettu-my.sharepoint.com/personal/juhan_ernits_ttu_ee/_layouts/15/guestaccess.aspx?docid=0503860647d77434d8dae0ac960affa63&authkey=ARg6jjw1kABuNZWf7ofnDmc Thesis topics at the Department of Software Science]

@@ 53. rida: / 53. rida: @@
 * Sept 15: Discussion of write literature review. Review of the referencing guide provided by the university: [http://www.ttu.ee/public/i/infotehnoloogia-teaduskond/Tudengile/IT_teaduskond_Allikate_kasutamise_juhend.pdf Allikate kasutamise juhend], [http://isites.harvard.edu/icb/icb.do?keyword=k70847&tabgroupid=icb.tabgroup106849 Using sources].
 * Sept 22: How to write reviews? [http://larc.unt.edu/ian/pubs/referee.pdf Ian Parberry's adivce], [http://se.ethz.ch/~meyer/publications/online/whysign/ Why some people sign their reviews?], [http://users-cs.au.dk/danvy/communication/cics_2015-09-14.pdf Olivier Danvy's slides on reviewing]
 =Thesis topics=
 [https://livettu-my.sharepoint.com/personal/juhan_ernits_ttu_ee/_layouts/15/guestaccess.aspx?docid=0503860647d77434d8dae0ac960affa63&authkey=ARg6jjw1kABuNZWf7ofnDmc Thesis topics at the Department of Software Science]

@@ 52. rida: / 52. rida: @@
 * Sept 8: Introduction
 * Sept 15: Discussion of write literature review. Review of the referencing guide provided by the university: [http://www.ttu.ee/public/i/infotehnoloogia-teaduskond/Tudengile/IT_teaduskond_Allikate_kasutamise_juhend.pdf Allikate kasutamise juhend], [http://isites.harvard.edu/icb/icb.do?keyword=k70847&tabgroupid=icb.tabgroup106849 Using sources].
 =Thesis topics=
 [https://livettu-my.sharepoint.com/personal/juhan_ernits_ttu_ee/_layouts/15/guestaccess.aspx?docid=0503860647d77434d8dae0ac960affa63&authkey=ARg6jjw1kABuNZWf7ofnDmc Thesis topics at the Department of Software Science]

@@ 21. rida: / 21. rida: @@
 # Is the problem suitable for a MSc thesis? (Kas ülesanne on sobiv magistritöö raames lahendamiseks?)
-==November 10: Written related work section==
+==November 17: Written related work section==
 The related work and background description should be at least 4 pages and should contain at least 15 references. The references need to be reliable and useful from the point of view of your thesis.
@@ 27. rida: / 27. rida: @@
 It is recommended that you add the 1 page problem statement to the document so that it will be possible to understand if the background and related work provided is relevant for the problem to be solved.
-* Peer review of the related work, i.e. everybody will be required to read 2 related work submissions and give detailed feedback. Deadline November 24.
+* Peer review of the related work, i.e. everybody will be required to read 2 related work submissions and give detailed feedback. Deadline November December 1.
 ==November/December: Submission of the draft of the thesis==

@@ 15. rida: / 15. rida: @@
 # Is it stated how the goals are going to be achieved? (Kas on kirjeldatud, kuidas plaanitakse eesmärke saavutada?)
 # Is it clear how the results will be validated? Is it valid from the engineering point of view? (Kuidas plaanitakse kontrollida, kas saavutatud tulemus on adekvaatne? Kas see võrdlus on planeeritud insenerlikult?)
 # How current/relevant/novel the topic is? (Kui aktuaalne/uudne teema on?)
 # Is the planned solution realistic? (Kas planeeritav lahendus on realistlik?)

←Vanem redaktsioon		Redaktsioon: 8. september 2017, kell 09:25
52. rida:		52. rida:
	* Sept 8: Introduction		* Sept 8: Introduction
	* Sept 15: Discussion of write literature review. Review of the referencing guide provided by the university: [http://www.ttu.ee/public/i/infotehnoloogia-teaduskond/Tudengile/IT_teaduskond_Allikate_kasutamise_juhend.pdf Allikate kasutamise juhend], [http://isites.harvard.edu/icb/icb.do?keyword=k70847&tabgroupid=icb.tabgroup106849 Using sources].		* Sept 15: Discussion of write literature review. Review of the referencing guide provided by the university: [http://www.ttu.ee/public/i/infotehnoloogia-teaduskond/Tudengile/IT_teaduskond_Allikate_kasutamise_juhend.pdf Allikate kasutamise juhend], [http://isites.harvard.edu/icb/icb.do?keyword=k70847&tabgroupid=icb.tabgroup106849 Using sources].
		+
		+	=Thesis topics=
		+
		+	[https://livettu-my.sharepoint.com/personal/juhan_ernits_ttu_ee/_layouts/15/guestaccess.aspx?docid=0503860647d77434d8dae0ac960affa63&authkey=ARg6jjw1kABuNZWf7ofnDmc Thesis topics at the Department of Software Science]

@@ 1. rida: / 1. rida: @@
 =Deadlines=
-==Oct 6 Feb 21: One page problem statement==
+==Oct 6: One page problem statement==
 * Peer review of the problem statement, i.e. everybody will be required to read 2 problem statements by fellow students and give detailed feedback. Deadline October 20. To be submitted to ained.ttu.ee, to the course ITX8302.