Summary

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

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.cds
	1	+XWiki.tig

Content

...	...	@@ -1,4 +1,4 @@
1		-This page is the collected wisdom and advice after supervising about 100 theses, from short study reports to dissertations. We recommend to study it **before** you start with your thesis work. Some topics are discussed on these separate pages:
	1	+This page is the collected wisdom and advice after supervising about 100 theses, from short study reports to dissertations. We recommend to study it __before__ you start with your thesis work. Some topics are discussed on these separate pages:
2	2
3	3
4	4
...	...	@@ -13,62 +13,62 @@
13	13	//Note: Most of this page is in German. Future additions should be done in English. At some point, some good soul might translate the German "legacy documentation" to English as well.//**
14	14	**
15	15
16		-= Interaction With Your Adviser(s) =
	16	+= Interaction With Your Advisor(s) =
17	17
18		-A good interaction with your adviser(s) is key to success. Unless you happen to have substantial work experience and to be already an expert in your field, your adviser is ahead of you in terms of experience and expertise. Take advantage of this to improve your own work.
	18	+A good interaction with your advisor(s) is key to success. Unless you happen to have substantial work experience and to be already an expert in your field, your advisor is ahead of you in terms of experience and expertise. Take advantage of this to improve your own work.
19	19
20		-Advisers are humans. They like to help you with your thesis topic; they don't like to have to "drive" it, or to get the feeling that their advice (including the hints on this page) is ignored. You, and not your adviser, should be the one who is pushing your work, asking questions, initiating discussions, and handing over thesis/chapter drafts without having to be explicitly asked for it. In short, your adviser should be convinced that your work is on track.
	20	+Advisors are humans. They like to help you with your thesis topic; they don't like to have to "drive" it, or to get the feeling that their advice (including the hints on this page) is ignored. You, and not your advisor, should be the one who is pushing your work, asking questions, intiiating discussions, and handing over thesis/chapter drafts without having to be explicitly asked for it. In short, your advisor should be convinced that your work is on track.
21	21
22		-Even in the age of modern communication devices, the basis of a good communication with your adviser is regular physical presence. Most of the time, we are in the fortunate position that we can provide you with a full-time desk, typically in the lab (1114/1115). Use this desk for doing your thesis work, and not your PC at home. A key communication instrument in the RTSYS group is the 9:30am tea, which you should participate in as well. One exception are theses that are done in collaboration with industry and where the industry partner provides the work space. In that case, you should keep your adviser here on track with regular progress reports. Usually, an E-mail every 2 to 4 weeks suffices for that.
	22	+Even in the age of modern communication devices, the basis of a good communication with your advisor is regular physical presence. Most of the time, we are in the fortunate position that we can provide you with a full-time desk, typically in the lab (1114/1115). Use this desk for doing your thesis work, and not your PC at home. A key communication instrument in the RTSYS group is the 9:30am tea, which you should participate in as well. One exception are theses that are done in collaboration with industry and where the industry partner provides the work space. In that case, you should keep your advisor here on track with regular progress reports. Usually, a short E-mail every 4-6 weeks suffices for that.
23	23
24		-Usually, your thesis is a full-time job, also meaning **full-time presence at your desk**. In case you also have other regular work to do, discuss this with your adviser at the beginning of your thesis work.
	24	+Usually, your thesis is a full-time job, also meaning **full-time presence at your desk**. In case you also have other regular work to do, discuss this with your advisor at the beginning of your thesis work.
25	25
26	26	= Timing is (Almost) Everything =
27	27
28		-Chances are your adviser has already supervised one or more theses. Take advantage of his or her experience! Send him 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 achieve an excellent result. 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.
	28	+Sie sollten insbesondere bei der Anfertigung der schriftlichen Ausfertigung auf die Erfahrungen des Betreuers zugreifen. Sie sollten dem Betreuer also Entwürfe Ihrer Arbeit zukommen lassen, bevor Sie die zu benotende Endversion einreichen. Ihre Entwürfe sollten dabei aus Ihrer Sicht möglichst reif sein, müssen aber noch keineswegs vollständig sein. Eine bewährte Sequenz von abzuliefernden Dokumenten ist:
29	29
30	30	|=(((
31		-What
	31	+Aktion
32	32	)))|=(((
33		-Master's Thesis
	33	+Masterarbeit/Diplomarbeit
34	34	)))|=(((
35		-Bachelor's Thesis
	35	+Bachelorarbeit/Studienarbeit
36	36	)))|=(((
37		-Motivation
	37	+Idee
38	38	)))
39	39	|(((
40		-Outline
	40	+Gliederung
41	41	)))|(((
42		-3 months before final submission
	42	+3 Monate vor Abgabe
43	43	)))|(((
44		-6 weeks
	44	+6 Wochen vor Abgabe
45	45	)))|(((
46		-Once you are halfway through your thesis, you should have a basic idea of which topics you want to cover in your thesis. This must be discussed with your adviser.
	46	+Zur Halbzeit sollte man schon einen Plan haben, welche Themen in der Arbeit grundsätzlich diskutiert werden sollen. Dies muss rechtzeitig mit dem Betreuer besprochen werden.
47	47	)))
48	48	|(((
49		-1–2 chapters
	49	+1-2 Probekapitel
50	50	)))|(((
51		-4 weeks
	51	+4 Wochen vor Abgabe
52	52	)))|(((
53		-3 weeks
	53	+3 Wochen vor Abgabe
54	54	)))|(((
55		-The first drafts you submit are used to make you aware of basic problems of your writing style. Getting this feedback as early as possible in your writing process means that you won't have to change the whole thesis after you submit your final draft.
	55	+Probekapitel sollen grundsätzliche stilistische Probleme zeigen und verhindern, dass bei der Endkorrektur alles grundsätzlich anders gemacht werden muss.
56	56	)))
57	57	|(((
58		-Complete thesis
	58	+Komplette Arbeit
59	59	)))|(((
60		-2 weeks
	60	+2 Wochen vor Abgabe
61	61	)))|(((
62		-10 days
	62	+10 Tage vor Abgabe
63	63	)))|(((
64		-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.
	64	+Die Abgabe der kompletten Arbeit **vor** der offiziellen Abgabe dient unter anderem dazu, dass stilistische/orthographische Korrekturen noch in die Arbeit einfließen können, bevor diese offiziell abgegeben/veröffentlicht ist. Das dient nicht nur der Verbesserung der Arbeit, sondern ist auch für den Betreuer befriedigender.
65	65	)))
66	66
67		-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.
	67	+Für Arbeiten, welche in Zusammenarbeit mit einem Industrieunternehmen angefertigt werden, gilt diese Sequenz ebenso; Sie sollten hier jedoch Entwürfe, welche Sie dem universitären Betreuer zukommen lassen, vorher entsprechend von Ihrem Betreuer aus dem Unternehmen durchsehen lassen.
68	68
69	69	= Keeping Notes =
70	70
71		-A common experience: while you do your investigative/implementation work, everything is clear — until you try to write things up, weeks or months later. Thus we highly recommend to take notes along the way, eg, as part of a chapter draft of your thesis.
	71	+A common experience: while you do your investigative/implementation work, everything is clear - until you try to write things up, weeks or months later. Thus we highly recommend to take notes along the way, eg, as part of a chapter draft of your thesis.
72	72
73	73	= Implementations =
74	74
...	...	@@ -80,9 +80,9 @@
80	80
81	81	Grundsätzlich gilt: Die Software ist „sauber“ zu schreiben und zu dokumentieren, unter Beachtung eines evtl. vorhandenen Projekthandbuchs. Die Qualität und Leserlichkeit Ihrer Software sowie der Dokumentation geht in die Bewertung Ihrer Arbeit mit ein.
82	82
83		-== Reviews and Ratings[[url:http://trac.rtsys.informatik.uni-kiel.de/trac/rtsys/wiki/Hinweise_Arbeiten#ReviewsundRatings||style="text-decoration: none;" title="Link to this section" shape="rect" class="anchor"]] ==
	83	+== Reviews und Ratings[[url:http://trac.rtsys.informatik.uni-kiel.de/trac/rtsys/wiki/Hinweise_Arbeiten#ReviewsundRatings||style="text-decoration: none;" title="Link to this section" shape="rect" class="anchor"]] ==
84	84
85		-More often than not, you will write code as part of your thesis. 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.
	85	+Ist die Implementierung Teil des KIELER Projekts, so müssen zur Erhaltung des Qualitätsstandards Design und Code Reviews durchgeführt werden. Wie dies praktisch abläuft und wie die sich daraus ergebenden Ratings aussehen wird auf der KIELER Projektseite erläutert.
86	86
87	87	= What Grade Do I Get For All This? =
88	88
...	...	@@ -110,7 +110,7 @@
110	110	)))|(((
111	111	Lösung von Teilproblemen
112	112	)))|(((
113		-Vollständige Lösung; gutes Vertrauen in die Lösung
	113	+Vollständige Lösung; gutes Vertauen in die Lösung
114	114	)))|(((
115	115	Vollständige, gute Lösung und Behandlung zusätzlicher Fragestellungen
116	116	)))|(((
...	...	@@ -290,8 +290,8 @@
290	290
291	291	= Further Links =
292	292
293		-* Eine sehr zu empfehlende, einführende Veranstaltung zur Präsentation und Erstellung wissenschaftlicher Arbeiten („Dokumentieren und Präsentieren“) bietet regelmäßig (ca. alle zwei Jahre) Prof. Luttenberger am Lehrstuhl für [[Kommunikationssysteme>>url:http://www.comsys.informatik.uni-kiel.de/||style="text-decoration: none;" shape="rect" class="ext-link"]] an.
294		-* „Einige typographische Grundregeln und ihre Umsetzung in LaTeX“ von [[Werner Struckmann>>url:http://www.cs.tu-bs.de/ips/struck/index.html||style="text-decoration: none;" shape="rect" class="ext-link"]] (TU Braunschweig), [[PDF>>url:http://www.ips.tu-braunschweig.de/struckmann/unitext/typographie.pdf||shape="rect"]]
295		-* „Anmerkungen zur Rechtschreibung“ von [[Werner Struckmann>>url:http://www.cs.tu-bs.de/ips/struck/index.html||style="text-decoration: none;" shape="rect" class="ext-link"]] (TU Braunschweig), [[PDF>>url:http://www.ips.tu-braunschweig.de/struckmann/unitext/rechtschreibung.pdf||shape="rect"]]
296		-* Falls Sie die Arbeit auf englisch verfassen: eine Reihe guter Ratschläge und weiterer Querverweise (wie z.B. den klassischen Strunk & White) finden sich auf [[Henning Schulzrinnes>>url:http://www.cs.columbia.edu/~~hgs/||style="text-decoration: none;" shape="rect" class="ext-link"]] Seite „[[Writing Technical Articles>>url:http://www.cs.columbia.edu/~~hgs/etc/writing-style.html||shape="rect" class="icon"]]“.
297		-* [[Wie schreibe ich eine gute Diplomarbeit?>>url:http://www.informatik.uni-oldenburg.de/studium/azwa/wie.html||shape="rect" class="icon"]] - Eine Anleitung der Uni-Oldenburg, z.T. spezifisch für Oldenburg; auch dort gibt es noch weiterführende Links.
	293	+* Eine sehr zu empfehlende, einführende Veranstaltung zur Präsentation und Erstellung wissenschaftlicher Arbeiten („Dokumentieren und Präsentieren“) bietet regelmäßig (ca. alle zwei Jahre) Prof. Luttenberger am Lehrstuhl für [[(% class="icon" %) (%%)Kommunikationssysteme>>url:http://www.comsys.informatik.uni-kiel.de/||style="text-decoration: none;" shape="rect" class="ext-link"]] an.
	294	+* „Einige typographische Grundregeln und ihre Umsetzung in LaTeX“ von [[(% class="icon" %) (%%)Werner Struckmann>>url:http://www.cs.tu-bs.de/ips/struck/index.html||style="text-decoration: none;" shape="rect" class="ext-link"]] (TU Braunschweig), [[(% class="icon" %) (%%)PDF>>url:http://www.cs.tu-bs.de/ips/struck/unitext/typographie.pdf||style="text-decoration: none;" shape="rect" class="ext-link"]]
	295	+* „Anmerkungen zur Rechtschreibung“ von [[(% class="icon" %) (%%)Werner Struckmann>>url:http://www.cs.tu-bs.de/ips/struck/index.html||style="text-decoration: none;" shape="rect" class="ext-link"]] (TU Braunschweig), [[(% class="icon" %) (%%)PDF>>url:http://www.ips.cs.tu-bs.de/struck/unitext/rechtschreibung.pdf||style="text-decoration: none;" shape="rect" class="ext-link"]]
	296	+* Falls Sie die Arbeit auf englisch verfassen: eine Reihe guter Ratschläge und weiterer Querverweise (wie z.B. den klassischen Strunk & White) finden sich auf [[(% class="icon" %) (%%)Henning Schulzrinnes>>url:http://www.cs.columbia.edu/~~hgs/||style="text-decoration: none;" shape="rect" class="ext-link"]] Seite „[[(% class="icon" %) (%%)Writing Technical Articles>>url:http://www.cs.columbia.edu/~~hgs/etc/writing-style.html||style="text-decoration: none;" shape="rect" class="ext-link"]]“.
	297	+* [[(% class="icon" %) (%%)Wie schreibe ich eine gute Diplomarbeit?>>url:http://www.informatik.uni-oldenburg.de/studium/azwa/wie.html||style="text-decoration: none;" shape="rect" class="ext-link"]] - Eine Anleitung der Uni-Oldenburg, z.T. spezifisch für Oldenburg; auch dort gibt es noch weiterführende Links.

Confluence.Code.ConfluencePageClass[0]

Id

...	...	@@ -1,1 +1,1 @@
1		-9471776
	1	+8650971

URL

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