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.uru
	1	+XWiki.cmot

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
...	...	@@ -33,7 +33,7 @@
33	33	** Soft requirements that can be solved if time permits
34	34	* Schedule outlining your proceeding (this includes writing the thesis, see next section)
35	35
36		-After you finished the proposal, you should give a short (informal) talk during our daily tea meeting presenting your topic to all members of our group.
	36	+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	37
38	38	= Timing is (Almost) Everything =
39	39
...	...	@@ -92,7 +92,7 @@
92	92
93	93	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.
94	94
95		-== 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"]] ==
	95	+== Reviews and Ratings ==
96	96
97	97	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	98
...	...	@@ -300,6 +300,10 @@
300	300	24
301	301	)))
302	302
	303	+= RtSys Stammtisch =
	304	+
	305	+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
	306	+
303	303	= Further Links =
304	304
305	305	* 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		-10751501
	1	+28672020

URL

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