Project Phases

Project work is done in phases and iterations. Each phase/iteration has to be presented to the teacher during consultation and has to be approved before continuing with the next phases/iterations. If a phase/iteration is not done to a satisfactory level, the team will be instructed to improve their work and present once again for approval.

Phase 1

Iterations

• P1-I1. Inception of the project idea (BusinessCase, ProjectVision)
• P1-I2. Functionalities of the system (UseCaseList, UseCaseScenarios)

Phase 2

• P2-I1. Architecture (ArchitectureInititial, ТechnologyChoice, SourceVersionControlOrganization)
• P2-I2. Implementing a system prototype (UseCasePrototypeImplementation)

Starting from this phase, a project source code repository has to be created as assigned by the teacher and it has to be regularly maintained and updated.

Milestone M1: Public presentation (where all course students are invited) of a first prototype with some initial functionalities of the project (PrototypePublicPresentation)

Phase 3

• P3-I1. Revised architecture (ArchitectureRevised, SourceVersionControlOrganizationRevised, UseCaseRealizations)
• P3-I2. Implementing all proposed functionalities (UseCaseImplementations)

Milestone M2: Public presentation (where all course students are invited) of the entire project as envisioned by the team (PreFinalPublicPresentation)

Phase 4 (Optional)

During PreFinalPublicPresentation, for projects that had a successful presentation the teacher announces a list of additional funcionalities and requests for each project, that are to be implemented during P4. It is up to the team members to decide if they will implement this list of additional requirements for a higher course grade, or not.

• P4-I1. Transitions and Finalization (UseCaseImplementationsFinal)

Milestone M3: Presentation of the final version of the project (FinalPublicPresentation)