Arrangement

Cover Page

This must clearly show your topic and your name. Additionally, your supervisor, the responsible professor, and the processing time must be indicated.

Task

Original or copy of the task hand-signed by the professor (your can retrieve the original from our secretary, Ms Jarschel in room APB 3110).

declaration of independent authorship

Here you declare in writing and by original signature that you have independently created your thesis, and that you did not use any references and means other than indicated. (Do not forget to sign both copies of your thesis!)

Table of Contents

The table of contents is supposed to provide a rough overview of your thesis, so please do not list all subsections down to the 5th or 6th level.

If you have further lists (list of figures, list of tables, ...), you should place them in the appendix.

Introduction

The reader is supposed to find a  brief introduction into the research area as well as the motivation for the task at hand. Your introduction should contain a brief summary of the thesis’ contents so that the reader knows what to expect.

Fundamentals and State of the Art

Here you are supposed to lay out the basics required to understand the thesis. You should assume that a computer scientist is able to understand common concepts of computer science independent of their research field. However, assume they are not firm in the area of your topic, so try to explain on this level. You should reference related work, but do not copy contents of reference books or tutorials.

A very important part of your thesis is the assessment of ‘state of the art’ as well as ‘related work’. Here you descibe approaches similar to your topic from enterprise as well as science. Your own concept must clearly be distinguished from these.

(Own) Concept

The main part of your thesis comprises of your own concept. Describe your approach as well as your conceptual layout here. As mentioned above, different existing approaches should be compared and assessed. Design decision based on that should be reasoned here. Therefore, you should keep this chapter updated during your entire processing time. Make sure to describe your concept on an abstract level, independent of underlain implementation details

Proof of Concept / Implementation

Describe the most important aspects of your implementation that were required in order to proof the feasibility of your concept. Help the reader by providing information on software and platforms used. This chapter is not supposed to be a developer or user documentation (documentations are - if required - part of the appendix).

Validattion / Evaluation / Assessment

Often, students tend to forget this chapter, or hastely write it within the last few days of the processing time. However, this chapter is an integral part of scientific writing: you evaluate your own concept and objectively assess the achieved results. Do not simply puke out a few performance parameters; explain what they mean and which conclusions can be drawn!

Summary and Future Work

Finally, summarise your thesis. Point out your main contributions and major improvements to existing concepts. Clearly point out which parts of the task could be fulfilled and which could not. Discuss how open aspects can be addressed in the future; ideally, provide some clues on what could be investigated. If you had ideas that did not make the final cut, do not hesitate to illuminate here; this provides evidence that you investigated beyond the boundaries of your task.

References

You must list all sources of your related work in bibliographic completeness. Each source should be referenced at least once within your thesis. Sources (like specifications and articles) that were only accessible through the WWW should be included in the references. The date of last successful access must be indicated for WWW sources. If the source found in the WWW is part of a journal or conference proceedings, these should be used as source.

Your list of references should follow a standard layout, preferable on from BibTEX. (c.f. BibTeX online tutorial)

Appendix

Do not place into your prose any figures (like UML or class diagrams), tabellen or listings (code examples) that cover more than 3/4 of a page. Place them here an reference then correspondigly in your prose. Furthermore, your list of figures, list of tables, and list of abbreviations go here. If you are into detailed work, place your glossary here.