Skip to content

Project work

A key element of the exercises is the semester-long project work.

Students are divided into groups of 2-4 and work on the same project throughout the semester, giving them time to thoroughly familiarize themselves with the problem to be solved. At the end of the semester, the submitted project work forms the basis for grading.

Both the practical signature and the course grade depend on the project work.

The requirements for obtaining a practical signature are as follows

  • Weekly progress in the group's GitHub repository.
  • The group's GitHub repository contains all documentation to be produced by the end of the semester.

The above is supplemented by the known requirement regarding absences: students may miss a maximum of three practical sessions.

Team members receive their course grades for the oral defense of the documentation submitted as part of the project work.

A project is considered complete if it contains all of the documentation elements listed below.

Documentation elements are only considered submitted if they are available on the main branch of the group's GitHub repository.

From the case study description, students derive specific requirements, based on which they fill in the relevant sections of the IEEE SRS template.

A list of requirements that define the architecture of the application to be developed.

Each requirement must be accompanied by a justification explaining why it is considered an ASR.

Listing the quality attributes that determine the architecture of the application to be developed. In other words, compiling the architectural characteristics.

Each characteristic must be accompanied by an explanation of why it is considered an architectural characteristic.