The project is to be done in teams (team-building instructions) and is worth 2 higher-education credits (ECTS credits). The main objective of the project is to exercise further the theoretical knowledge gained in the lectures, but on a problem that you propose and that gets our approval.
We are not just interested in a sufficiently complete and efficient approach, but also in explanations and experimental evaluation, hence a report is also required for the project and the quality of the report determines the project score.
Eight optional (but highly recommended) help sessions (some shared with Assignment 3) and a mandatory grading session are scheduled for the project.
PhD students do either just the assignments (solo), or just the project (solo; possibly in connection with their PhD research; but they are highly encouraged to do the assignments nevertheless), or both: contact the head teacher.
A project proposal of three problems, listed by decreasing preference, each answering two questions (what? which third-party instance data?) must be submitted at Studium (as a single file in .pdf format; all other formats will be rejected; state the team number and the names of the team members): the head teacher may interactively (via Studium) negotiate revisions with you during the subsequent seven days until our notification (if approved, then pass, else fail). The problems can be your own or drawn from the following websites (in the latter case, it suffices to name the problem when listing it):
Let us know if you think some problem ought to be taken off this list, for instance because an approach with MiniZinc or OPL can be found on the internet.
An approved project proposal entitles to continuation (deadlines and schedule in the table below):
Initial report: If your initial report is submitted on time at Studium, follows the imposed structure of the project report (LaTeX source, including a demo report), is at most 15 pages long (excluding Feedback to the Teachers, Error Report, and References), complies with the instructions at the slides numbered 78 and 79 of Topic 1, and all goes fine at the mandatory grading session, then you pass and are entitled to a final report, else you fail and are not entitled to a final report. Either way, you get feedback.
Note that the project report has additional structure compared to assignment reports, namely Approach and Correctness.
Final report: You must use the obtained feedback in order to prepare your final report: it will get a score \(p \in 0..10\), under the same conditions as the initial report, and it must be rewritten where relevant and not just expanded incrementally.
Re-examination will be conducted during the general re-examination period from 16 to 28 August 2027: contact the head teacher by email minimum 2 weeks in advance, so that the questions can be set on time.
| Deliverable or Event | Deadline or Date |
|---|---|
| Proposal | Wed 18 Nov at 13:00 |
| Approval (pass / fail) | Wed 25 Nov at 13:00 |
| Kickoff & Help A | Fri 27 Nov |
| Help B (also for Assignment 3) | Thu 03 Dec (after Solution Session 2) |
| Help C (also for Assignment 3) | Mon 07 Dec |
| Help D (also for Assignment 3) | Thu 10 Dec |
| Help E | Wed 16 Dec |
| Help F | Thu 17 Dec (after Solution Session 3) |
| Initial Report (pass / fail) | Fri 18 Dec at 13:00 |
| Grading Session (mandatory) | Mon 21 Dec |
| Help G | Mon 11 Jan |
| Help H | Wed 13 Jan |
| Final Report (score \(p \in 0..10\)) | Fri 15 Jan at 13:00 |
The project proposal, initial report, and final report must be submitted via Studium. Submission deadlines are hard. Exceptions must be negotiated in due time during work hours with the head teacher, upon reporting a convincing case of force majeure. Grading will only start after a deadline, so you can submit multiple times until then.
The considerations on ethics, including the generative AI policy, of the assignment reports also apply to the project reports.
We reserve the right to give different project scores to the teammates of a team.
Each higher-education credit (ECTS credit) translates under Swedish university law into an expected 26.67 hours of work for the average student. The project is worth 2 credits: discounting about half of the 21 hours spent in period 1 on the lectures (the other half being similarly discounted on the 3 assignment credits), the project should reflect 49.5 hours of work by the average student, for each teammate. This does not clash with other courses you are taking, as university studies are legally defined to take 400 hours of work per study period (normally 10 weeks), and the standard 15 credits targeted in a study period are calibrated to reach that total.
The project grade is determined by a published scale, depending on your project score \(p \in 0..10\).
The overall grade is determined by a published scale, depending on the modelling assignment scores and the project score \(p\).
These rules are effective as of Mon 2 Nov 2026. The head teacher reserves the right to modify them at any moment, should special circumstances call for this.