Why Oberstufeninformatik Exists

Oberstufeninformatik is a small independent publication about computer science in the upper years of secondary school. It is written for teachers who plan lessons, for students preparing for coursework and exams, and for self-taught learners who want a clear path through the same material.

Three subjects, one classroom

Articles fall into three areas that tend to meet in the same course: teaching methods, Java and databases. A lesson on object-oriented design is easier when the example is a small library database, and a database unit lands better when students have already written code that stores something.

• Computer Science Teaching looks at lesson sequences, project work, assessment ideas, common misconceptions and ways to keep mixed-ability groups moving.
• Java Programming covers classes and objects, inheritance, interfaces, collections, recursion, file handling and the errors beginners meet again and again.
• Databases explains relational modelling, normalisation, SQL queries, joins, keys and how to connect a small program to stored data.

How the material is prepared

The goal is explanation you can use in the next lesson or study session. Code examples are meant to be small enough to read in full, and they are compiled and run before they are published. Statements about the language, SQL behaviour or database design are checked against official documentation, standard textbooks and the specifications of the tools mentioned.

Curricula differ between regions and change over time, so articles point out where a topic may be treated differently in your course instead of claiming one syllabus fits everyone. Pages are revisited when a Java release, a tool or a teaching approach makes older advice outdated.

Who reads it

Some readers are experienced teachers looking for a fresh exercise, others are new to the subject and teaching it for the first time. Students use the site to revisit a concept after class. Nothing here assumes a specially equipped computer room or paid software.

Spotted an error?

If a code sample fails, a query returns something other than described or an explanation is misleading, write to [email protected]. A confirmed fix is applied directly to the affected article, so the next reader sees the right version.