MV Abitur Computer Science exam-day guide
MV Abitur Computer Science · Prepare for the day ahead.
Your checklist
Admission document and photo ID
Bring the invitation/admission notice issued by your school or the exam board plus a valid photo ID. Which ID types are accepted and whether a copy suffices varies by Bundesland and school; confirm with the provider.
Approved calculator
Clarify in advance which calculator model is permitted (graphing calculators are often restricted or must be reset). Bring a model you have used before and check battery or spare batteries.
Approved reference materials
Some states or schools allow a formula collection, dictionary, or the official operator/command reference for the programming language. Confirm exactly which printed materials are allowed and whether annotations are permitted.
Writing and drawing tools
Several pens, pencils, eraser, sharpener, and a ruler. Diagrams (UML, state machines, ER models) are usually part of the written component.
Rough paper and folder
Rough paper is usually supplied, but bring a folder or transparent sleeve so loose sheets stay with your materials. Confirm whether you may bring your own paper.
Watch (non-smart)
Exam rooms do not always have a visible clock. A simple analog or digital watch is usually fine; smartwatches and phones are not.
Water and a small snack
Practical/written components can run several hours. Check the provider's rules on food and drink in the exam room.
Know the programming environment
For the practical part, be familiar with the editor, compiler/interpreter, debugger, and file handling of the environment used at your school. Ask whether you may test the environment beforehand.
Prepared code snippets and templates (mental, not physical)
Practice typical building blocks: class definitions, loops, array/list traversal, file reading, sorting, and simple recursion. Do not bring unauthorized notes; confirm what counts as a permitted aid.
Location and timing confirmed
Confirm building, room, start time, and arrival time with your school. Arrive early enough to settle in; late-arrival rules differ, so confirm with the provider.
Backup plan for technical failure
If the practical part is on a computer, ask in advance what happens if the system fails (spare machine, paper fallback, time compensation). This is school-specific; confirm with the provider.
Phone and smart devices switched off and stored
Phones, smartwatches, and other connected devices are generally not allowed in the exam room. Confirm the storage rule with the provider.
Plan the day
Do a final pass over the official topic list (typically algorithms and data structures, programming, databases, networks, and theoretical foundations such as automata and formal languages, depending on your course). Mark topics you cannot explain in your own words and spend the remaining time only on those. Write one short program end-to-end in the exam environment, including input handling, a data structure, and output, to rehearse the full workflow rather than isolated syntax.
Re-read the operator/command reference and the permitted materials so you know where things are. Practice tracing algorithms by hand (sorting, search, tree traversal, graph algorithms) and drawing UML class diagrams, state machines, and ER diagrams neatly, because hand-drawn diagrams are usually graded on correctness and readability.
Do one timed mock under exam-like conditions: no internet, only permitted aids, fixed duration. Afterwards, review errors by category (misread task, wrong data structure, syntax slip, missing justification) and note the pattern. Sleep on a normal schedule; do not start new topics you cannot consolidate.
Pack the checklist items: admission notice, ID, calculator, permitted reference materials, pens, ruler, watch, water. Confirm room, start time, and arrival time. Prepare clothes and transport. Do a light review of your own error notes and formula/command locations only; stop studying early enough to sleep well.
Eat a normal breakfast, arrive with buffer time, and keep your phone off and stored per the provider's rule. Before the start, set out your materials, check the calculator, and read the cover page of the exam carefully for structure, point distribution, and any choice of tasks.
Read all tasks before writing. Note point values and suggested times, and decide the order. Start with a task you can do confidently to secure points, then move to harder ones. Write down key definitions and structures you will need so you do not lose them under time pressure.
For programming tasks: clarify input/output format, plan the data structures, write the code, then test with small and edge cases (empty input, single element, duplicates). Comment briefly and use meaningful names. For theoretical tasks: state the definition, then apply it step by step and show intermediate states. For diagrams: label everything. If you get stuck, leave a clear marker and move on; return later.
Check that every task has an answer, that code compiles or is syntactically consistent, that diagrams are labeled, and that you answered the actual question asked (not a similar one). Verify name and candidate number on all sheets and hand in everything required.
Rules to check
Bring the admission notice and a valid photo ID; without them you may be refused entry. Accepted ID types and replacement procedures are set by the school or exam board, so confirm with the provider.
Phones, smartwatches, and other connected or storage-capable devices must be switched off and stored outside your working area. Using them during the exam is generally treated as an attempt to cheat; the exact consequence is set by the provider.
Only approved aids may be used. Unauthorized notes, annotated materials, or communication with others can lead to the task being graded zero or the exam being annulled. Confirm the permitted aids list with the provider.
Follow the invigilator's instructions on seating, starting, and stopping. Writing after the stop signal is usually penalized; the specific rule is set by the provider.
Breaks and leaving the room are usually restricted and supervised; you may not take materials with you. Ask the invigilator before leaving and confirm the school's break rule.
If you feel unwell or a computer fails, report it immediately to the invigilator and have it documented; time compensation or a replacement attempt may be possible. The procedure is school-specific, so confirm with the provider.
Answers must be your own work. Cite sources only where the task allows it, and do not present prepared solutions as your own reasoning.
Grading follows the official assessment criteria for the course; partial credit is often given for correct approach and intermediate steps, so show your reasoning and label diagrams rather than writing only final results.