Administrator: Add English DGB 2 translation

2026-09-11T17:35:51Z

Add English DGB 2 translation

Neue Seite

{{DISPLAYTITLE:DGB 2: Programming, Testing and Debugging}}
← [[DGB 2. Klasse/en|Digital Literacy – Year 2]]

Programming means describing a solution precisely enough for a computer system to execute it. In Year 2, the focus is on small, understandable programs: planning sequences, combining instructions, using variables, input, output and conditions, testing systematically and fixing errors deliberately.

== Curriculum reference ==

{| class="wikitable"
! Area !! Classification
|-
| '''Competence area''' || Production
|-
| '''Perspectives''' || Technical and interaction perspectives (T, I)
|-
| '''Focus''' || Creating, testing and debugging simple programs
|-
| '''Competence''' || Develop simple programs in a suitable learning environment, plan test cases, locate errors and improve programs step by step.
|}

== Learning objectives ==

Students can:

* use the basic functions of a programming or learning environment;
* distinguish a program from its source code or block sequence;
* create and run simple sequences of instructions;
* receive input and produce output;
* use variables to store changing values;
* use simple conditions for decisions;
* recognise repetition in simple tasks and use loops where appropriate;
* distinguish syntax errors, runtime problems and logical errors in simple examples;
* test programs step by step rather than only at the end;
* develop normal, boundary and error test cases;
* explain debugging as systematic error finding;
* make controlled changes and test again after each change;
* plan, implement, document and improve a small program.

== Learning content ==

=== Programming environment and program ===

A programming environment provides tools for writing or assembling, running and testing programs. In block-based environments, instructions are combined as blocks; in text-based languages, instructions are written. The specific environment may change, but algorithmic thinking, data and testing remain central.

=== Sequences and clear processes ===

A program follows instructions in a defined order. Changing the order can change the result. Before coding, a short sequence in everyday language or a flowchart can help clarify the intended process.

=== Variables ===

Variables store values a program needs, such as a name, score or counter. A value can be assigned, read and changed. Clear variable names make a program easier to understand and debug.

=== Conditions and repetition ===

A condition lets a program choose between actions, for example: if the answer is correct, add a point. Repetition avoids writing the same instruction many times. Students should first understand the rule before choosing a technical block or language construct.

=== Testing ===

Testing asks whether the program behaves as intended for selected inputs. Good tests include ordinary cases, boundary cases and, where appropriate, incorrect or unexpected input. Testing small parts early makes faults easier to locate.

=== Debugging ===

Debugging is systematic problem solving: reproduce the problem, locate the relevant part, form a hypothesis, change one thing, test again and document the result. Random changes make it harder to understand why a program works.

=== Types of errors ===

A syntax error means the written code does not follow the language rules. A runtime problem occurs during execution. A logical error means the program runs but produces the wrong result. Block environments reduce some syntax errors, but logical errors still occur.

=== Documenting and improving ===

Useful documentation includes the task, important variables, test cases and changes made. Feedback and testing can then be used to improve clarity, correctness and usability.

== Classroom activities ==

=== Explore a programming environment ===

Find the controls for editing, running, stopping, resetting and viewing output.

'''Expected outcome:''' Confident use of basic tools.

=== Create a first simple program ===

Build a short sequence that takes an input and produces a visible output.

'''Expected outcome:''' A working basic program.

=== Test step by step ===

Add or change one part at a time and run the program after each meaningful step.

'''Expected outcome:''' A documented incremental test process.

=== Debug a faulty program ===

Use prepared examples with one or more errors and record the hypothesis, change and result.

'''Expected outcome:''' A systematic debugging log.

=== Program input and output ===

Create a program that asks for information and produces a suitable response.

'''Expected outcome:''' Correct input–process–output behaviour.

=== Use variables deliberately ===

Store and change at least two values and explain when each value changes.

'''Expected outcome:''' Correct variable use.

=== Develop your own test cases ===

Write normal, boundary and error cases before running a program.

'''Expected outcome:''' A small test table.

=== Peer-review programs ===

Exchange programs and use a checklist to test behaviour and readability.

'''Expected outcome:''' Constructive feedback.

=== Plan, build and improve a mini-project ===

Develop a quiz, calculator, simple game or other small project and improve it after testing.

'''Expected outcome:''' A documented mini-project.

=== Summarise the debugging process ===

Write a five-step routine you can use when a program does not work.

'''Expected outcome:''' A reusable troubleshooting method.

== Self-check ==

* I can create a simple program.
* I can use input, output and variables.
* I can use simple conditions and repetitions where appropriate.
* I can plan useful test cases.
* I can distinguish basic types of errors.
* I can debug by changing and testing systematically.
* I can document and improve a small program.

== See also ==

* [[DGB 2: Programme und Daten/en|Programs and Data]]
* [[DGB 2: Geistiges Eigentum und Urheberrecht/en|Copyright in Programming Projects]]
* [[DGB 2: Software fuer unterschiedliche Aufgaben/en|Software and Development Tools]]

[[Kategorie:Digitale Grundbildung]]
[[Kategorie:DGB 2]]

DGB 2: Programmieren Testen Debuggen/en - Versionsgeschichte

Administrator: Add English DGB 2 translation