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

Equipment

If nothing else is said, I will assume that you use your own computers, but it is possible for me to bring a computer that is (somewhat) similar to the lab computers.

Sessions:

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.

2024 schedule

We will have most presentations in Kärnan, located almost above entrance 25, upper floor, first door on the right. Some of the presentations are in Transformen, ISY. It is located right above entrance 27 in the B building, upper floor.

All sessions start 15 minutes past (10.15, 13.15 etc).

15 may 10-12 in Kärnan

15 may 13-15 in Kärnan

17 may 10-12 in Kärnan

17 may 13-15 in Kärnan


NEW: 21st and 22nd

21 may 8-10 in Transformen

21 may 10-12 in Transformen

22 may 10-12 in Kärnan

22 may 13-15 in Transformen


23 may 10-12 in Kärnan

23 may 13-15 in Kärnan

24 may 10-12 in Kärnan

24 may 13-15 in Kärnan

The following were cancelled since they are too late.

28 may 10-12 in Kärnan

28 may 13-15 in Transformen

29 may 10-12 in Kärnan

29 may 13-15 in Kärnan

Sign up here:

Booking system

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 computer based presentation

• 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.

Reports

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