Team and Overview
In this course you carry out a medium-sized software development project in a team, consistently applying an agile development process. The course is divided into two phases: 1.) Bootcamp, and 2.) Group Phase.
During the Bootcamp, you will be working on an individual assignment. In this assignment you will develop a web application with Spring Boot and Vue.js. In the Group Phase you will work in teams of 4-6 students on a software project of your choice where you will be supported by a tutor and will present your progress in regular Management Reviews.
- Course number
- 194.148 — Projekt (PR), 4.0 semester hours, 6.0 ECTS, Presence, continuous assessment
- Course lead
- Jürgen Cito
- Lecturers
- Stefan Biffl, Kristof Meixner, Peter Frühwirt, Wolfgang Krebs, Dietmar Winkler
- Assistants
- Markus Böck, Jakob Valentin Hoffmann, Michael Schröder, Nathanael Nussbaumer
- Course email
- se-pr@se.tuwien.ac.at
- Preliminary discussion
- Thu 01.10.2026, 15:00 - 16:00, Informatikhörsaal - ARCH-INF
- Course catalog
- Official course listing in TISS (194.148, WS 2026/27)
- TUWEL
- TUWEL course — announcements, materials and submissions
- Institute
- E194 — Institute of Information Systems Engineering
Registration
Important! Registration for this course runs through TISS, from 20.09.2026 16:00 until 05.10.2026 23:55 (strict deadline!).
All students registered in TISS until the deadline will have access to the course in
TUWEL.
Deregistration is possible until 07.10.2026 23:55.
Prerequisites
Mandatory prerequisite is the completion of the introductory and orientation phase (STEOP). We kindly ask for your understanding that we cannot make exceptions here (exchange students excluded).
Furthermore we expect:
- Object-oriented analysis, design and programming
- Basics of the Unified Modeling Language (UML)
- Basic knowledge of algorithms and data structures
- Basic knowledge of database systems
- Using a practical programming language and tools (e.g. Java or C++)
- Applying an integrated development environment and source code management
Timetable
The following table lists all important dates for the course (preliminary discussion, entry test, tutor meetings, Management Review, deadlines).
If a deadline is listed on a certain date, assume it is due at 23:55 that day unless specified otherwise.
Lecture dates
| Date | Content | Location |
|---|---|---|
| Thu 01.10.2026 15:00 - 16:00 |
Kickoff | Informatikhörsaal - ARCH-INF |
| Mon 05.10.2026 See TISS |
Software Quality and Evolution + Software Design and Architecture (recorded) online lecture | Zoom (Link in TUWEL) |
| Tue 06.10.2026 See TISS |
Crash Course: Spring Boot (recorded) online lecture | Zoom (Link in TUWEL) |
| Wed 07.10.2026 See TISS |
Crash Course: Vue.js + Responsible AI Use (recorded) online lecture | Zoom (Link in TUWEL) |
| Fri 09.10.2026 14:00 - 17:00 |
Bootcamp-Tutorial | HS 17 Friedrich Hartmann - ARCH |
| Tue 03.11.2026 14:00 - 16:00 |
Group Phase Tutorial | EI 7 Hörsaal - ETIT |
Bootcamp Examination slots
| Date | Content | Location |
|---|---|---|
| Thu 29.10.2026 08:00 - 20:00 |
SEPR Live Coding and Interview | InfLab Frogger |
| Thu 29.10.2026 08:00 - 20:00 |
SEPR Live Coding and Interview | InfLab Q*bert |
| Fri 30.10.2026 08:00 - 20:00 |
SEPR Live Coding and Interview | InfLab Frogger |
| Fri 30.10.2026 08:00 - 20:00 |
SEPR Live Coding and Interview | InfLab Q*bert |
| Sat 31.10.2026 08:00 - 18:00 |
SEPR Live Coding and Interview | InfLab Frogger |
| Sat 31.10.2026 08:00 - 18:00 |
SEPR Live Coding and Interview | InfLab Q*bert |
Further milestones
| Date | Content | Notes |
|---|---|---|
| 05.10.2026 23:55 | Registration deadline in TISS | |
| Fri 09.10.2026 23:55 |
TUWEL Entry test | Must be passed positively |
| Fri 23.10.2026 23:55 |
Submission individual assignment | Final grading in submission interview |
| 03.11.2026 - 06.11.2026 | Group formation | Start of Group Phase |
| 13.11.2026 08:00 |
Deadline project proposal | |
| 13.11.2026 | Online proposal presentations | |
| 16.11.2026 - 20.11.2026 | Management Review 1 | Will be scheduled with your assistant |
| 14.12.2026 - 18.12.2026 | Management Review 2 | Will be scheduled with your assistant |
| 24.01.2027 | Upload video | Mandatory ~5-minute presentation of your project |
| 25.01.2027 - 28.01.2027 | Management Review 3 | Will be scheduled with your assistant |
Course Structure
The course consists of two phases that together amount to 400 points. Both phases must be completed positively for a positive completion of the course.
Bootcamp (total: 100pts)
You work independently during the Bootcamp. The main objective of the Bootcamp is to teach you solid software engineering practices and to prepare you for the Group Phase.
The Bootcamp consists of:
- Entry Test (5pts)
- Individual Assignment (50pts)
- Live Coding (45pts)
- Submission Interview
Entry Test
The entry test will be a TUWEL online test that can be repeated as often as you like until the deadline on 9 October 2026 at 23:55. Students who have not passed the test by then will be removed from the course. The test will cover software quality and evolution, and software design and architecture.
Individual Assignment
During the individual assignment, you will implement a web application using Spring Boot and Vue.js. The assignment will be released on TUWEL on 6 October 2026.
The assignment will be graded by a combination of automated tests, which will set your base grade, and a submission interview, where a tutor will look at your solution and ask you questions about it. The submission interview can alter your grade in either direction, and it is possible to get a negative grade even if you have passed the automated tests. The submission interview will take place directly after the live coding.
During the assignment you will have the chance to ask questions and get help from the teaching staff in the TUWEL forum and during tutor hours. Further, we will provide you with intermediate feedback on your progress. The timing will be announced on TUWEL. The intermediate feedback will consist of a test report generated by the same automated tests that will be used for final grading. The intermediate feedback will not be graded, but will give you an impression on your progress and how to improve your solution.
It is recommended to start the assignment early and to work on it continuously, as the assignment should not be underestimated and will likely require a significant amount of time to complete. Further, starting early ensures that you will get feedback more often.
Live Coding and Submission Interview
Make sure to register in TUWEL for a live coding and interview slot!
To register for the live coding and submission interview, you will need to have at least 50% on the automated tests of the individual assignment. If you have not reached this threshold, you will not be able to register for a slot and will not be able to complete the Bootcamp positively.
During your slot, you will start with a live coding exercise in class. The exercise will consist of a small feature that extends a sample solution of the project from the individual assignment provided by us. You will have 45 minutes to complete the exercise.
After the live coding exercise, you will have a submission interview with a tutor. The tutor will look at your live coding and individual assignment solution and ask you questions about both. The interview will take about 30 minutes and will be used to determine your final grade for the Bootcamp.
The main focus of the interview will be to assess your understanding and ownership of the project. As in real software projects, you are responsible for your solution and should be able to explain your design choices, implementation details and the concepts behind your solution. The tutor will further use the interview to assess your solutions adherence to the technical guidelines and best practices taught in the course.
Group Phase (total: 300pts, per group member)
Your team develops a software project using agile practices, supervised by a tutor, and presents progress in three Management Review. You will work on a project of either your choice or a suggested topic which will be anounced in TUWEL.
Group finding
After the live coding and submission interview, everyone who completed the Bootcamp positively will have 3 days to submit group preferences in TUWEL. You can use the group finding forum in TUWEL to find teammates and discuss project ideas. PLEASE NOTE: these are preferences. We will try to accommodate them, but cannot guarantee that everyone will get their preferred teammates or project.
Project finding
After final group assignment, you will submit a project proposal on TUWEL by 13 November 2026 at 08:00. This proposal can be based on our suggested topic or a project of your choice. The proposal should contain a short description of the project (including its goals) and the features you will implement, described as user stories. You will present the proposal online on 13 November and receive feedback from the teaching staff.
Technologies
During the Group Phase, you must use Java with Spring Boot for the backend and Vue.js for the frontend, as in the Bootcamp.
Development
Overall the development phase will last about 10 weeks which will be split into 4 sprints. During this time, you will have weekly meetings with your tutor. The development phase starts after the first Management Review and ends with the final Management Review.
Group Phase Grading
While this is a group project, grading will happen for each individual student and continuously throughout the Group Phase. Your grade consists of the following components:
- Sprint Reviews (4x 40pts)
- Technical Review (1x 40pts)
- Overall Project Success (100pts)
Sprint Reviews are made by your tutor. For each sprint your tutor will look at 1-2 merge requests per student and provide a grading recommendation based on the quality of your code, your adherence to the user story and technical guidelines as well as best practices taught in the course.
The Technical Review will be conducted by a different tutor than your own. In the week before Management Review 2 another tutor will look at one merge request for each student and provide a grading recommendation based on the same criteria as the sprint reviews.
The Overall Project Success will be assessed by your assistant during the final Management Review. The assessment will be based on the quality of your final product, the mandatory video presentation, the completeness of your project and the overall success of your team.
Overall Grading
The grading consists of 25 % from the Bootcamp and 75 % from the Group Phase.
Both phases must be completed positively (≥ 50%) for a positive completion of the course.
The examination mode is continuous assessment (prüfungsimmanent).
Grading scale
All partial and final performances are graded on the same scale from 0 to 100 percent:
- S1: 88%-100%
- G2: 75%-87.99%
- B3: 63%-74.99%
- G4: 50%-62.99%
- N5: 0%-49.99%
- S1: 352-400pts
- G2: 300-351.99pts
- B3: 252-299.99pts
- G4: 200-251.99pts
- N5: 0-199.99pts
Academic Honesty
We expect all students to do their own work. Where work is done in teams, every team member is expected to contribute substantially and to be able to explain and defend any part of the submission, including parts primarily written by others.
Any kind of plagiarism, including submitting code or text authored by someone else without attribution, sharing solutions between teams, or presenting work from a previous edition of the course as your own, will result in expulsion from the course with a grade N5 (Nicht Genügend).
AI Usage Policy
You may use AI tools in this course. You remain responsible for every artifact you submit, including code, tests and models. You must understand your work, be able to explain your decisions and take clear ownership of the result, whether or not AI helped produce it.
Submit a written reflection on your AI use for each unit of grading: one for the Bootcamp and one for each sprint in the Group Phase. State whether you used AI, what you used it for, and how you checked and incorporated its output. If you did not use AI, say so in your reflection.
Reflection Prompts
For your 200-word reflection, you may consider the following prompts to guide your writing:
- How did you evaluate the AI's output?
- Did you need to correct or refine its suggestions? Why?
- Did any responses surprise you? Why?
- Did the AI speed up tasks you could have done yourself? Which?
- Did the AI provide information or explanations you did not previously have? What?