Summary

• Page properties (3 modified, 0 added, 0 removed)
• Objects (1 modified, 0 added, 0 removed)
  • Confluence.Code.ConfluencePageClass[0]

Details

Page properties

Parent

...	...	@@ -1,1 +1,0 @@
1		-RTSYS.Rtsys Group Wiki.Writing Guides.WebHome

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.rtadmin
	1	+XWiki.rvh

Content

...	...	@@ -37,17 +37,13 @@
37	37
38	38	= Timing is (Almost) Everything =
39	39
40		-Technically, the only hard deadline that you have regarding your thesis submission is the one concerning the submission to the examination office (//Prüfungsamt//), which is at the end of the semester for Bachelor thesis and six months after registering the thesis for master thesis. However, at RTSYS (as with most other groups) we offer to look at your thesis before the official submission. This not only helps to improve your thesis, it also is more satisfying for the advisor to look at a thesis in detail if it's not just to determine a grade but also to help improve the result.
	40	+Chances are your adviser has already supervised one or more theses. Take advantage of their experience! Send them drafts of the chapters of your thesis before submitting the final thesis. Of course, the drafts should be as good as possible from your point of view. Your adviser can only improve your drafts so much. If your draft is of low quality, (s)he can help you push it to an okay-ish level; but if the draft is already of high-quality to start with, (s)he can help you elevate it to pure awesomeness. Note that your drafts need not be complete yet: you can always hand in missing bits and pieces later on. Here's a schedule that has proven to work well regarding when to hand in what.
41	41
42		-Thus, in your own interest, we advise //strongly// to send drafts of the chapters of your thesis to your advisor(s) before submitting the final thesis. Of course, the drafts should be as good as possible from your point of view. Your adviser can only improve your drafts so much. If your draft is of low quality, they can help you push it to an okay-ish level; but if the draft is already of high-quality to start with, they can help you elevate it to pure awesomeness. Note that your drafts need not be complete yet: you can always hand in missing bits and pieces later on.
43		-
44		-The process is usually that 1) you send a draft to the doctoral student(s) directly advising you, 2) you get feedback from them, 3) you implement that feedback, 4) you send the revised draft to the Prof. Yes, this pipeline takes time, and often there are holidays and travel plans to take into account as well, in particular for deadlines at the end of the summer semester. Here's a schedule that has proven to work well regarding when to hand in what to your direct advisors. Of course, sticking to that schedule is YOUR responsibility, you should not rely on your advisors to remind you of it.
45		-
46	46	(% class="wrapped" %)
47	47	|=(((
48	48	What
49	49	)))|=(((
50		-When (AT THE LATEST)
	46	+When
51	51	)))|=(((
52	52	Motivation
53	53	)))
...	...	@@ -70,7 +70,7 @@
70	70	)))|(((
71	71	2 weeks
72	72	)))|(((
73		-Submitting a draft of your complete thesis **before** the final submission gives your adviser enough time to find problems and gives you enough time to incorporate corrections into your final thesis.
	69	+Submitting a draft of your complete thesis **before** the final submission gives your adviser enough time to find problems and gives you enough time to incorporate corrections into your final thesis. This doesn't only improve the quality of your thesis, but also satisfies your adviser.
74	74	)))
75	75
76	76	Theses done in collaboration with industry partners follow the same schedule. The drafts you submit to your adviser at the university, however, should previously be run past your industry adviser.
...	...	@@ -91,7 +91,7 @@
91	91
92	92	== Reviews and Ratings ==
93	93
94		-To make sure that code is of a certain quality, it must be run through design and code reviews. The way this works is explained [[on this page>>doc:Kieler.Processes.Review Process.WebHome]]. The reviews are not only intended to improve the quality of your code, but also to give feedback to you as a programmer to help you improve.
	90	+To make sure that code is of a certain quality, it must be run through design and code reviews. The way this works is explained [[on this page>>doc:KIELER.Review Process]]. The reviews are not only intended to improve the quality of your code, but also to give feedback to you as a programmer to help you improve.
95	95
96	96	= What Grade Do I Get For All This? =
97	97
...	...	@@ -301,7 +301,7 @@
301	301
302	302	= RtSys Stammtisch =
303	303
304		-Every student who is going to write a thesis and hence is considered an integral part of our group is more than welcome to join our [[doc:Rtsys.RtSys Stammtisch.WebHome]]. We will meet monthly in different restaurants in Kiel to have dinner and a good time together. Please ask your advisor or other students to invite you
	300	+Every student who is going to write a thesis and hence is considered an integral part of our group is more than welcome to join our [[doc:RtSys Stammtisch]]. We will meet monthly in different restaurants in Kiel to have dinner and a good time together. Please ask your advisor or other students to invite you
305	305
306	306	= Further Links =
307	307

Confluence.Code.ConfluencePageClass[0]

Id

...	...	@@ -1,1 +1,1 @@
1		-6160527
	1	+106364952

URL

...	...	@@ -1,1 +1,1 @@
1		-https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/RTSYS/pages/6160527/Writing and Grading Theses
	1	+https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/RTSYS/pages/106364952/Writing and Grading Theses