The aim of the subject is to provide on hand experience in developing a complex software from requirements to final tested product applying an incremental, iterative approach in teams of 5, using UML, C++ or Java. Each week the incremental results are documented, the documentation is submitted and corrected. At some points also runnable software is created.

The task is to solve the problem in 3 major phases.
- The goal of the skeleton is to show the soundness of the analysis model.- The goal of the prototype is to create the final product without the GUI. It fulfills all requirements except the graphical representation.- The graphical version adds the graphical user interface to the prototype. The schedule of the project is as follows:
1. Teams set up, original problem announced.
Skeleton phase
2. Requirements, project, functionality
3. Analysis model, version 1, based on Object oriented principles and using UML.
4. Analysis model, version 2, correcting the errors and other problems of the previous version.
5. Design of the skeleton. The analysis model is transformed into a full design of the skeleton: all business classes with all publicc method but no business logic. Business logic decesions are asked of the user. The method calls are printed to the screen.
6. Implementing the skeleton. Software source code is to be submitted. At laboratory testing is conducted.
7. Spring break
Prototype phase.
8. Concept of the prototype. Real use-cases, input-output interface design, test cases defined.
9-10. Detailed design. All classes are designed fully, except the graphical interface. Tests are designed and described in the language specified in the previous task.
11. Implementing the prototype. Based on the detailed design. Also, tests are conducted and the protocols are to be submitted.
Graphical phase.
12 Specifying the GUI, using UML, based on MVC. Detailed as far, as the connection to earlier classes are specified.
13-14 Implementing the graphical version.