Software Engineering - Projects

Project Schedule and Admin


The Task

How the projects are graded

Ada stuff (to be filled with more and more)





  • 2007-06-18 Project grades assigned! You should get your individual credits soon, and the total course grade (in case you have written the exam and finished the labs) is calculated as described in the course overview.
  • 2007-05-25 Final deadline for all documents is June 1st 9:15! Make sure all docs are checked in by then. After that we will look at them in order to grade the projects.
  • 2007-05-25 Remember that June 1st is mandatory for everyone! If you for some reason cannot attend June 1st, contact Rikard beforehand to arrange a way to compensate for this.
  • 2007-05-23 Detailed schedule for the final presentation available! See below.
  • 2007-05-23 Do you want to earn 5 more credits during summer? You have the opportunity to continue with developing/finishing the robots after the SE course ends in the form of a summer course. Ask Lars for more info.
  • 2007-03-23 Change in schedule? Due to a student request, group 1 and 2 have swapped place in the steering group meetings. The schedule below is correct.
  • 2007-03-21 SVN or CVS? Sorry for any confusion, you are to use SVN, nothing else.
  • 2007-03-21 Weekly meetings? Weekly meetings / presentations is called "Project followup" in the schedule (first occasion April 2nd).
  • 2007-03-13 Project groups defined, see last slides in Project Schedule and Admin. Report as soon as possible if there is any error!
  • 2007-03-13 Here you will find news about the projects. Monitor this page regularly!








 Sensor Fusion

 Command Center

 Strategy Goalie

 Strategy Attacker







 Lars Asplund

 Lars Asplund

 Lars Asplund

 Lars Asplund

Steering Group





Project Manager

 Vasilis Odontidis

 Mikael Åsberg

 Kristian Karlberg

 Kivanc Doganay

Result (40 points)





Documentation (10)





Project work (10)





Product - Software (10)





Presentations (10)










Steering Group Meetings

Schedule for steering group meetings are as follows:

Group 2   13:00 – 13:30

Group 1   13:30 – 14:00

Group 3   14:00 – 14:30

Group 4   14:30 – 15:00

Look at the schedule for exact dates (not always Mondays!), and rooms.

Final Presentation

The whole presentation on June 1st is mandatory for everyone. There are two parts, first 9:15-12:00 in T2-056, and then 14:00-15:00 in the robotics lab.

First, we have presentations in room T2-056 from 9:15-12:00. Each group have ca 30 minutes to present:

1) The project results – you should present things like:

  - Activities and worked hours summarized.

  - Timeliness. Which milestones were met, which were missed? Why? Which deliverables did you deliver, how timely were they? Why?

  - Describe the overall features of the system. How many (and which) requirements are fulfilled? Do you fulfil the use cases you have promised?

  - Some graphs would be nice, e.g. a Gantt chart illustrating activities, milestones etc.

2) What did you learn from the project – you should present things like:

  - How much of the initial plan held – how did you manage changes along the way?

  - Did you spend less time than you wanted on any particular activity (e.g. testing)?

  - Did you divide and synchronize the work in a proper way? What are your experiences?

  - What is your experience from working in a group? What were the problems (please do not be too detailed or personal)?

  - What turned out as you expected? What will you improve the next time?

3) Requirements and Design. Present the fundamental ideas in your solution, e.g.:

- What were the fundamental requirements? (You should not go through each requirement in detail, but stay at a high level; showing some use case diagrams may be a good idea.)

- Are there any requirements of particular interest, e.g. non-functional requirements, very strict requirements, very difficult requirements?

- What are high-level design (architectural) decisions? How is the program structured? How do you use the available technology?

- How do you ensure real-time behaviour?

Then, we have a break during which you should prepare the afternoon part (and also maybe have lunch ;-) We meet in the robotics lab 14:00-15:00 where each group have ca 15 minutes for their…

4) Result demonstration. This means showing the robot, describing all features in a pedagogical and convincing way. Of course, you should rehearse beforehand what you will show, to avoid embarrassing situations (the “demo ghost”). You should probably spend some time planning and practicing the demo!




Rikard Land, last update: 2006-04-11