Based on what we have been doing, select a problem to dig deeper into. The projects are performed, demonstrated and reported indiviually.

Considering the high number of participants this year, the projects can be made in groups of 1 to 3 people. 2 is recommended. This means that the projects is no longer the only source for grading, since there must be some kind of individual examination. I had this scrap this plan for legal reasons.

Oral presentations!

You should produce a video presentation of your project. I do not plan to use it for anything but examination. I might want to show selected clips of particularly nice projects in a future course. Let me know if you do not want that. The movie is best handed in by a link to a server or git repository.

The video should be 10-15 minutes and include explanations of the most interesting parts of the project, and a short demo.

Report and source code

You also need to hand in a written report and the source code. The report should be in PDF format and your LiU ID should be part of the title. Thus, no “report.pdf” or “tnm084.pdf” please! You don’t want to have your report lost in cyberspace any more than I do. Source code can be handed in by providing a git link, or mailed as attachment. (An upload system might be opened for your hand-ins but this is not 100% certain at this time.)

Hand-in and presentations should be handed in before HT2 ends, which means the day VT1 starts. If you are done before you will get the grade registered for HT2, otherwise it will be in VT1. There is a small score penalty for going over the deadline but you will still be graded.

Report contents

About 5-10 pages, describing what you did, how it was done and why you solved it the way you did. I am not counting pages, I am counting contents. Use figures, it is a graphics course and screenshots are easy to make. Typical structure:

1. Introduction. Describe the problem, basically the specification you started from. What features were mandatory and optional?

2. Background information. Any information about the kind of problem you solved that is needed to follow the rest of the report.

3. About your implementation. Tools used, program structure.

4. Interesting problems. Did you run into any particular problems during the work?

5. Conclusions. How did it come out? How could it have been done better? What did you learn?

6. References.

© Ingemar Ragnemalm 2021