Reports
The three preliminary examinations
You write three reports over the semester, each analysing a small business problem with the tools covered up to that point. They are the Prüfungsvorleistung for this module: all three must pass before you can sit the exam.
| Topic | Issued | Due | Submitted via | Assignment link | |
|---|---|---|---|---|---|
| Report 1 | Pricing the Barcelona hotel market | Session 3, 28.09. | Sun 18 October, 23:59 | Moodle | — |
| Report 2 | announced in session 6 | Session 6, 02.11. | Sun 8 November, 23:59 | Classroom 50 | Accept Report 2 |
| Report 3 | announced in session 10 | Session 10, 30.11. | Sun 6 December, 23:59 | Classroom 50 | Accept Report 3 |
The assignment links work from the session in which a report is issued. Before that, Classroom 50 says This assignment is locked.
This page carries the deadlines and the rules. The task sheets are handed out on the day a report is issued:
- Report 1: task sheet and data in the Moodle course.
- Reports 2 and 3: the assignment link in the table above. The repository it creates for you holds everything — task sheet and hints (
TASK.mdandTASK.pdf,HINTS.mdandHINTS.pdf), the data, and a starter document.
If you cannot see Report 1 in Moodle after session 3, say so in the forum.
Reports 2 and 3 go through Classroom 50: you accept a link, clone the repository it creates for you, and push. The Classroom 50 manual has every step, and the last commit you push before the deadline is the one that counts.
The rules, for all three
- Written individually. Discussing an approach with a classmate is fine; handing in the same document is not.
- Graded pass/fail only. There is no mark, and a report that passes comfortably counts exactly as much as one that scrapes through.
- Submitted as a rendered document plus everything needed to re-run it. Your analysis has to reproduce on my machine — that is the point of session 3, and it is checked.
- One revision in total across the three reports — not one per report.
If a report does not pass, you may revise and resubmit it. Across the whole semester you have one revision. Use it on Report 1 and Reports 2 and 3 have to pass first time. The revised version is due one week after you receive the feedback on the report that did not pass.
That is deliberate. A revision exists to rescue a report that went wrong, not to serve as a first draft.
Moodle is the fallback for every report, including the two that normally go through GitHub. If something technical goes wrong, submit through Moodle and tell me. A tooling problem will never cost you a submission.
What passes
The same two things, every time:
- It reproduces. I can re-run your analysis and get your document back.
- It answers the question honestly — with code that does what you say it does, and interpretation sentences that claim no more than the data supports.
Each task sheet spells this out in detail, including an explicit list of what fails. Nothing on it will be a surprise if you have done the in-session exercises.
Using AI
Allowed and encouraged, under the two rules from Getting Started: you are responsible for every line you submit, and you declare how you used it. Each report ends with a short note on that. Session 7 is devoted to doing it well.