Checklist for journeyman exam and exam project
From bottom task to approved documented and defended solution
§Understanding the task
- 01Have I read the task description through at least twice and underlined the requirements that must be met?
- 02Have I noted which industry-relevant requirements and standards the solution must comply with?
- 03Have I set a realistic timetable for when each part should be finished?
- 04Do I know what technologies and methods I will use and why they are current and relevant to the task?
§Technical solution
- 01Are the basic requirements of the assignment solved before I spend time on extra fine-tuning?
- 02Is the code semantic, structured and readable by others?
- 03Have I tested the solution — including cases where something can go wrong?
- 04Are safety and accessibility designed in, not added at the last minute?
- 05Does the solution work in the environment it is to be delivered or displayed in?
§Project documentation
- 01Does the documentation describe the task's requirements and my technical choices — and the reasoning for them?
- 02Has testing and quality assurance of the solution been documented?
- 03Can an outsider understand the structure of the solution from the documentation alone?
- 04Has documentation been written continuously and not just compiled at the last minute?
§Oral presentation
- 01Can I account for my system and methodology without reading from a manuscript?
- 02Have I prepared answers to why I chose exactly these technologies and solutions?
- 03Have I thought about what I would do differently with more time?
- 04Have I rehearsed the presentation aloud for at least one other person?
§Final check before delivery
- 01Are all fields in the form completed even if the origin is unknown?
- 02Do I have a working copy in a safe place if something goes wrong on the day itself?
- 03Have I removed test data, temporary code and secrets that don't belong in the final submission?