Project presentations

Project presentations with demo sessions at the end of the course

Instructions for the presentation and report, see below

On this page, I list booked demo sessions. If you want to sign up for a session, send an E-mail to me. Include the following information:

• Project title

• Session (date&time)

• Participants

(• Whether you use your own computer or wish to use one of mine (requires a test beforehand) Irrelevant for 2021)


We will use Zoom, so you use your own computer. If you need a high performance computer, you can probably use Olympen, but you need a webcam, and I don’t know if that is doable. If needed, I will investigate.


A good demo session should have 3-4 groups, possibly 5, minimum 2. If we have only one group for a session, we will cancel it and move the group to another session.

2021 spring schedule:

This year’s sessions will take place online, using Zoom. Some kind of web camera is needed. Let me know if that is a problem.

Sign up here:

Booking system

All sessions start 15 minutes past (10.15, 13.15 etc). Same Zoom link as for the rest of the course.

12 may at 15:15

13 may at 10:15

13 may at 13:15

14 may at 10:15

14 may at 13:15

17 may at 10:15

17 may at 13:15

18 may at 10:15 NEW

18 may at 13:15 NEW

There should be at least two groups in each session. If you end up single, I will need to rearrange somehow.

Mandatory participation

You must be present on one session - the one including your own presentation! If it is not possible for all persons in your group to be present at the same session, your group will make two presentations, with different people!

Project demonstrations

Your demonstration consists of two parts:

• about 10 minutes presentations of the work using whiteboard and/or slides/transparencies

• about 5 minutes demonstration of the working program

Make us understand what you did. Focus on interesting points. Don't forget to be somewhat entertaining. Be aware of who you are talking to (your course mates). Make the time worthwhile for the audience!

Inform me beforehand of any special hardware and software needs! I will do my best to provide what you need, but inform me in time. Also, it is wise to test your program beforehand on the computer that you will use.


The report should be submitted within one week after the presentation. It should be in PDF format, with the LiU Id of participants in the filename.

About 3-5 pages (no less than two pages of text), 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?

Source-code must be supplied, preferrably in electronic form. Links to git repository is OK as long as I have access.

This page is maintained by Ingemar Ragnemalm