Last modified by Niklas Rentz on 2023/10/10 10:45
<
From version < 24.1 >
edited by cds
on 2014/09/05 00:07
To version < 31.1 >
edited by Reinhard von Hanxleden
on 2017/05/15 11:11
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.cds
1 +XWiki.rvh
Content
... ... @@ -15,7 +15,7 @@
15 15  
16 16  = Interaction With Your Adviser(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 adviser(s) is key to success. Unless you happen to have substantial work experience and to already be 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.
19 19  
20 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.
21 21  
... ... @@ -23,10 +23,23 @@
23 23  
24 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.
25 25  
26 += Thesis Proposal =
27 +
28 +The first thing to do after you familiarized yourself with the topic and problem of your thesis is to write a short proposal (~~2-4 pages). The proposal should be prepared as early as possible (within the first or second week) and should show your adviser that you understood the problem and have a rough idea how to solve it. It may be structured as follows.
29 +
30 +* Problem description
31 +* Planned Solutions/Goals
32 +** Hard requirements that have to be fulfilled by the end of your thesis
33 +** Soft requirements that can be solved if time permits
34 +* Schedule outlining your proceeding (this includes writing the thesis, see next section)
35 +
36 +You should send your thesis proposal to your advisor and (if he is not already your advisor) the professor. After you finished the proposal, you should give a short (informal) talk of about 15 minutes during our daily tea meeting presenting your topic to all members of our group.
37 +
26 26  = Timing is (Almost) Everything =
27 27  
28 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 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.
29 29  
42 +(% class="wrapped" %)
30 30  |=(((
31 31  What
32 32  )))|=(((
... ... @@ -80,9 +80,9 @@
80 80  
81 81  The bottom line: write clean and proper code that adheres to our coding guidelines and document it. The quality and the readability of your code and of your documentation will influence your grade.
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"]] ==
96 +== Reviews and Ratings ==
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.
98 +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.
86 86  
87 87  = What Grade Do I Get For All This? =
88 88  
... ... @@ -90,16 +90,17 @@
90 90  
91 91  Zur Beurteilung einer Diplomarbeit wird generell ein schriftliches Gutachten erstellt, welches die jeweilige Arbeit individuell würdigt (incl. Note) und an das Prüfungsamt weitergeleitet wird. Es hängt dabei von der jeweiligen Aufgabenstellung ab, welche Leistungen im Einzelfall erwartet werden; so sind z.B. die Anforderungen hinsichtlich der konkreten Umsetzung bei einer stark anwendungsbezogenen Arbeit anders als bei einer eher theoretischen Arbeit. Gewisse Anforderungen und Erwartungen hinsichtlich der Qualität der Arbeit und der Vorgehensweise des Studierenden sind jedoch allgemein gültig, und z.T. auch bereits in der jeweiligen Prüfungsordnung konkret genannt. So sieht z.B. §19(1) der Diplomprüfungsordnung vor: „Die Diplomarbeit [...] soll zeigen, dass die Kandidatin oder der Kandidat in der Lage ist, innerhalb einer vorgegebenen Frist ein Problem aus dem Fach Informatik selbständig nach wissenschaftlichen Methoden zu bearbeiten.“ Hier sind also bereits drei Kriterien genannt (Fristeinhaltung, Selbständigkeit, Wissenschaftlichkeit). Ein etwas detaillierterer Kriterien-/Bewertungskatalog ist in den beiden folgenden Tabellen angegeben. Diese sind zunächst für Diplomarbeiten ausgelegt, finden aber - mit entsprechenden Abwandlungen - auch für Studien-, Bachelor- und Masterarbeiten Anwendung.
92 92  
106 +(% class="wrapped" %)
93 93  |(((
94 94  **Merkmal**
95 95  )))|(((
96 -
110 +\\
97 97  )))|(((
98 -
112 +\\
99 99  )))|(((
100 -
114 +\\
101 101  )))|(((
102 -
116 +\\
103 103  )))|(((
104 104  **Punkte**
105 105  )))
... ... @@ -114,7 +114,7 @@
114 114  )))|(((
115 115  Vollständige, gute Lösung und Behandlung zusätzlicher Fragestellungen
116 116  )))|(((
117 -
131 +\\
118 118  )))
119 119  |(((
120 120  Punkte
... ... @@ -226,13 +226,13 @@
226 226  max. 16
227 227  )))
228 228  |(((
229 -
243 +\\
230 230  )))|(((
231 -
245 +\\
232 232  )))|(((
233 -
247 +\\
234 234  )))|(((
235 -
249 +\\
236 236  )))|(((
237 237  **Summe**
238 238  )))|(((
... ... @@ -241,6 +241,7 @@
241 241  
242 242  Die Umrechnung einer Punktzahl in eine Zensur ergibt sich unter Anwendung dieses Katalogs aus der folgenden Tabelle.
243 243  
258 +(% class="wrapped" %)
244 244  |(((
245 245  Note
246 246  )))|(((
... ... @@ -288,6 +288,10 @@
288 288  24
289 289  )))
290 290  
306 += RtSys Stammtisch =
307 +
308 +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
309 +
291 291  = Further Links =
292 292  
293 293  * Prof. Luttenberger at the [[Communication Systems Group>>url:http://www.comsys.informatik.uni-kiel.de/||shape="rect"]] regularly offers a very good course on writing and presenting scientific work.
Confluence.Code.ConfluencePageClass[0]
Id
... ... @@ -1,1 +1,1 @@
1 -9471805
1 +37814327
URL
... ... @@ -1,1 +1,1 @@
1 -https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/RTSYS/pages/9471805/Writing and Grading Theses
1 +https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/RTSYS/pages/37814327/Writing and Grading Theses

Navigation

Quick Links

KIELER on GitHub
RTSYS Homepage