Saarland Abitur Information Systems
More study resources
Cheat sheet
Keep the key ideas within reach.
ExploreKey terms
Get comfortable with the vocabulary.
ExploreStudy plan
Give each week a clear focus.
ExploreCommon mistakes
Understand the traps and how to avoid them.
ExploreCase studies
Put your knowledge to work in context.
ExploreExam-day guide
Prepare for the day ahead.
ExploreAbout this exam
The Saarland Abitur in Informatik is the written subject examination taken by Gymnasium students in Saarland who choose computer science as a Leistungs- or Grundkurs for the Abitur. It is a school-leaving qualification, not a professional certification: it signals that a candidate can model systems, reason about algorithms, and analyse technical problems in writing under examination conditions. It is intended for pupils who have followed the Saarland curriculum through the Oberstufe and who want a university-entrance qualification with a strong informatics component.
The written paper is task-based rather than multiple choice. Prompts are multi-part and typically move from analysis of a given situation through modelling and implementation to evaluation. Content draws on software development and programming, relational databases and SQL, networks and client-server protocols, formal languages and automata, and the societal and ethical dimensions of information systems such as data protection and security. Because the tasks are cumulative, partial credit depends on showing your reasoning at each step.
Preparation should be active: write code by hand, draw and defend data models, trace automata on paper, and practise explaining design decisions in precise German. Work through the official curriculum and past central tasks, and time yourself on full prompts. The responsible authority publishes the current regulations, task formats and any binding notices; consult those sources rather than relying on second-hand summaries, and confirm details with your school's Fachlehrer.
What you'll study
About Saarland Abitur Information Systems preparation
What does the written Informatik Abitur actually look like?
It is a written examination built from central task sets, usually with several multi-part prompts. Expect to analyse a described scenario, produce models or code on paper, and justify decisions in continuous prose. There is no multiple-choice section. The responsible ministry and your school publish the binding structure and permitted aids for the current year.
How difficult is it compared with class tests?
The individual concepts are familiar from lessons; the difficulty lies in combining them under time pressure and in writing precise justifications. Tasks often chain: an error in your model carries into later parts. Practising complete, timed prompts is more useful than drilling isolated exercises, because it trains the sequencing and self-checking the paper rewards.
Can I retake the examination?
Retake and repeat rules for the Abitur are set in the Saarland examination regulations and administered by the school and the responsible authority, so they vary by individual case. Ask your Oberstufenleitung early, in writing, about your specific situation. Do not rely on forum reports; the official regulation text and your school's written confirmation are what count.
How long is the paper and how many points is it worth?
The official body publishes the current duration, weighting and scoring for each subject and course type, and these can change between years. Check the ministry's site and the current Prüfungsordnung, and confirm the details for your course with your Fachlehrer. No third-party summary should be treated as binding on timing or weighting.
In what order should I revise the topics?
Start with modelling and programming, since they underpin database and network tasks. Then move to relational modelling and SQL, practising joins and integrity constraints by hand. Add networks and protocols, then automata and formal languages, which need regular short practice. Leave ethical and legal topics for spaced review, and finish with full timed papers.
Which mistakes cost the most marks?
Common losses come from skipping the analysis step, giving code without explanation, drawing incomplete entity-relationship models with missing cardinalities or keys, and writing SQL that ignores constraints. In automata tasks, students forget to define states and transitions precisely. Read each sub-task's operator verb carefully: begründen, bewerten and implementieren demand different answers.
Do I need to write real, runnable code on paper?
Expect to write syntactically correct program fragments by hand, in the language or notation your course uses. Correctness, structure and readability all matter, and comments or short explanations of intent usually earn credit. Practise on paper without an IDE so that you notice missing declarations, indentation and edge cases before the exam.
How much weight do societal and ethical topics carry?
They appear as evaluation components attached to technical tasks, for example assessing a database design against data-protection principles or discussing security trade-offs in a client-server system. Answers should cite concrete legal or technical grounds rather than general opinions. The exact share of marks is published by the responsible authority.
Where do I find the authoritative rules and task examples?
Use the Saarland ministry's education server and the official regulation texts for the current Abitur cohort, plus the central task examples your school distributes. These are the only reliable sources for format, aids and assessment criteria. This page is independent study material and is not affiliated with the ministry or any school board.