This document describes the purpose and content of proposals for master thesis projects in Computing Science. Since it is the content of the document that is important, no specific form is required. This does not imply that the document may be written without care. In fact, whether or not you manage to turn the content into a reasonable form indicates whether you are mature enough for a master thesis project.
As a student, you usually choose your master thesis topic based on some kind of description provided by a company (external projects) or a researcher at the Department of Computing Science (internal projects). These descriptions are usually a good basis for the proposal, but are not sufficient in their own. This is particularly true for external projects, because companies are usually interested in some kind of practical work to be done, whereas your interest should be to show that you deserve the title Master of Science in Computing Science - and this includes much more than "just" making an implementation of a fancy system.
To receive the pass grade, your work on the project, including the thesis itself, the presentation, and the opposition, must
Your master thesis project and its outcome are, thus, the "crowning event" of your education. Naturally, this means that you should full all other degree requirements before embarking on your master thesis project. While there are cases in which small deviations from this general rule are well motivated, no major departures from it will be accepted. For this reason, we want you to hand in a Ladok printout of your completed courses together with the specication of our project.
In order to be acceptable, the proposal must, of course, specify the goals of the project and who is going to work on it (your name, study programme, and personal number). However, it is at least as important that the proposal provides enough information for the programme coordinator to be able to assess whether your own prerequisites, in combination with the requirements imposed by the project, will probably result in a successful thesis. Here, successful means that it demonstrates the abilities listed above. Therefore, you should have an eye on the list when describing the requirements and circumstances of the project and your own background in the field. You can start by answering the following questions, and add further information to the extent you consider useful:
Note that the specication does not need to be a long document. In most cases, 2-3 pages will be sufficient. In most cases, you will already be in contact with a possible supervisor (namely the one who proposed the topic). In this case, it is advisable to formulate the proposal with him/her. The following steps are:
Note that your project plan is not a static document. Most plans will have to be adjusted to some extent during the running time of the project. The goal is not to adhere to a plan that does not work, but to use it as a meaningful document that is revised in a well-motivated and transparent way if necessary. To be able to assess the way in which you follow and update the plan (see the third item in the initial list of demonstrated abilities), we want you to set up a project diary. (In most cases, one that is accessible via the Internet is most appropriate.) This diary should be updated at least once every week and has to be handed in when your thesis is finished, possibly in the form of a web link. It should document