Background for the header
To the home page of the University of Antwerp



Concept | Guidance

LORE / Teaching / PP3BAC

The concept

The idea of the project proposals below is that students complete a complex software system during a two semester period. At the end of the second semester, the students have to present the results of their projects, typically by means of a short report and a little presentation.

A detailed elaboration of the expectations about projects are discussed can be found in Dutch.

There are three types of projects we are happy to supervise. The first collects everything that has to do with object-oriented reengineering, the main research topic for LORE. The second involves various tools to support teaching and research, while the third are projects in industry.

We have organized the information on PP3BAC projects supervised by LORE members in three sections:



LORE guides students throughout the year at two levels: (i) the individual level; and (ii) the group level.

At the individual level, students are assigned a project guide. The task of this project guide is to coach the student. At large, this coaching role consists of "stimulating and guiding the development of an effective attitude of the student with respet to the problems and situations related to the project, conform to a durable growth in personality, such that the ability to handle equivalent situations in the future, without coaching, improves". More specifically, the project guide is the student's first line of support.

At the group level, we invite students to organize regular project meetings. The goal of these meetings is to (i) prepare for the final project defense at the end of the year; (ii) practice and improve communication skills; and (iii) learn from others. How often these meetings are held is determined by the students themselves.

I'd, the purpose is to get to know each other, and to get aware of other students addressing similar challenges. As of the second meeting, some kind of presentation is preferred as the main means to structure your communication. The setting which is simulated in these presentations is the following: imagine that you are working at a company, and all of a sudden your boss pops in to ask about your current status. Aspects that we typically like to see addressed in these presentations are:

  • Context: Briefly discuss the context in which you are running your project.
  • Problem at hand: Clarify the problem at the base of the project, and indicate its intrinsic difficulties.
  • Project management: Demonstrate how you have organized the work, and how you are controlling it (instead of the work controlling you!)
    • Scope: What are the boundaries of your project? What is not included in the project?
    • Planning: What deliverables were promised, and when are they due? Is the planning realistic? Is the planning used? Did the planning need to be readressed/renegotiated?
    • Status: What is the status of the deliverables? Are you on schedule? If not, what is the calculated delay for the deliverables?
    • Next step: What is the very next activity which you will perform?
    • Risks: Which risks were envisioned, and which have been mitigated? What is the priority of the risks that still need to be migitated? E.g., which external dependencies might have an affect on your outcome? Which alternatives have you prepared in case this risk instantiates?
  • Software engineering:
    • Tests: How can you verify that you satisfy the requirements? Which testing strategy have you selected, and what are the arguments for this selection? How confident are you that your solution satisfies the requirements?
    • Analysis: How have you captured the requirements? How did you validate that these are the right requirements?
    • Quality assurance: What are the non-functional requirements? E.g., how do you differentiate between a good and a bad solution?
Valid HTML 4.01! Valid CSS!

 Lab On REengineering - Antwerpen, last modified 17:10:33 06 April 2009