Source: AP Computer Science Principles Course Framework
Tags: creative development, collaboration, pair programming, program development, iterative, incremental, debugging, errors, syntax error, logic error, runtime error, overflow error, API, documentation, comments
Difficulty: Beginner Prerequisites: None. This is a good starting point for the course.
Big Idea 1 covers how software gets made, from the initial idea through to a working program. It accounts for 13% of the AP exam, making it the smallest section, but the terminology here shows up everywhere else. You need to understand the software development process, how programmers collaborate, and the types of errors that can break a program. If you can name each error type and explain what makes it different from the others, you are in good shape for this unit.
Programming is a collaborative, creative process. Programs are built through iterative and incremental development, tested for errors, and documented so others can understand and reuse them. Know the four error types cold: syntax, logic, runtime, and overflow.
Programming
A collaborative and creative process that brings ideas to life through the development of software.
Computing innovation
A computer program that takes in data, transforms it, and outputs data. In simple terms, any application or system that uses a program to do something useful with information.
Program
A collection of instructions that a computing device executes. Think of it as a recipe the computer follows step by step.
Code segment
A smaller collection of statements that are part of a larger program. In simple terms, a chunk of code that does one particular job within the whole.
User interface (UI)
The inputs and outputs that allow a user to interact with a piece of software. Buttons, text fields, screens, anything you click or see.
Pair programming
Two programmers developing software side by side at one computer on the same algorithm. One writes code (the "driver"), the other reviews each line (the "navigator").
Iterative development process
Programmers develop working prototypes and go back through the stages of their development method, refining as they go. Think of it as building in loops rather than a straight line.
Incremental development process
Programmers break the program into smaller pieces and make sure each piece works before adding it to the whole. In simple terms, build one feature at a time, test it, then move on.
Program documentation
A description of how something in your program works. Comments are the most common form, written directly in the code.
Comments
Lines written into a program (e.g. // this button navigates to the next screen) that explain what the code does. They do not execute; they exist for humans reading the code.
Library
A collection of pre-written functions that can be used across different programs.
Application Program Interface (API)
The documentation for a library that describes how each function works, what parameters it takes, and what (if anything) it returns.
Syntax error
An error that occurs when the spelling or punctuation rules of the programming language are broken. A missing semicolon, an unclosed parenthesis, a misspelled variable name. The program will not run at all.
Logic error
A mistake in a program's underlying logic that causes unexpected behaviour. The program runs but produces the wrong result. Using IF instead of IF/ELSE chains is a classic example.
Runtime error
An error that occurs while the program is running. The program starts, but crashes during execution. Dividing by zero (DISPLAY(5/0)) is a common trigger.
Overflow error
An error that occurs when a computer tries to handle a number outside its defined range of values. The result is too large (or too small) for the system to store.
Debugging
The process of finding and fixing errors in a program.
Camel case
A naming convention where multi-word names are joined with each new word capitalised, e.g. stopButton. Used to give variables and elements meaningful, readable names.
Programming benefits from collaboration at the planning, testing, and designing stages
Benefits include exchanging ideas, gaining multiple perspectives, addressing misunderstandings, developing thinking skills, and reducing bias
Pair programming is a specific collaboration method: two programmers, one machine, one algorithm
Iterative development: build a prototype, test it, revisit earlier stages, refine, repeat
Incremental development: break the program into small pieces, verify each one works, then combine
Both approaches reduce the chance of large, hard-to-find bugs
Documentation explains how parts of a program work
Comments in code (e.g. // navigates to next screen) are the most common form
A library's API tells you how each function works, its parameters, and its return values
Good documentation helps collaboration and makes code reusable
A program event is an action like a button click, mouse movement, or keyboard input that triggers behaviour
Event-driven programs respond to events triggered by user actions or system events
Sequential programs execute instructions in order, one after another
Variables and elements should have meaningful names
Camel case (stopButton) is a common convention
Variables are case-sensitive: a and A are different variables
Students often confuse logic errors with syntax errors. A syntax error stops the program from running entirely. A logic error lets the program run but gives the wrong output.
Students sometimes think runtime errors are the same as logic errors. A runtime error crashes the program mid-execution (e.g. dividing by zero), while a logic error produces incorrect results without crashing.
Students often think overflow errors only happen with very large numbers. They occur whenever a value falls outside the defined range, which depends on how many bits the system uses to store the number.
Students sometimes believe comments affect how the program runs. They do not. Comments are ignored by the computer and exist solely for human readers.
⚠️ You will be asked to identify the type of error from a code snippet. Know all four types and be able to distinguish them.
⚠️ Expect questions about the benefits of collaboration and pair programming.
⚠️ Iterative vs. incremental development: know the difference and recognise examples of each.
⚠️ The AP pseudocode on the exam is case-sensitive. DISPLAY(A) when the variable is a is a syntax error.
True or False: A syntax error allows the program to start running before crashing.
Fill in the blank: The process of finding and fixing errors is called __________.
True or False: In pair programming, both programmers write code simultaneously on separate machines.
Fill in the blank: A __________ error occurs when a program runs but produces incorrect output due to flawed logic.
True or False: Comments in code are executed by the computer along with the rest of the program.
Answers: 1. False (it prevents the program from running at all). 2. Debugging. 3. False (they work side by side at one computer). 4. Logic. 5. False (comments are ignored during execution).
Q: A student writes a program that assigns a value to variable score, then uses DISPLAY(Score) to output it. The program crashes. What type of error is this, and why?
A: This is a syntax error. Variables are case-sensitive, so score and Score are treated as different variables. Score was never defined, so the program fails.
Q: A grading program uses separate IF statements (not IF/ELSE) to assign letter grades. A student with a score of 95 receives "A", "B", and "C" as output. What type of error is this?
A: This is a logic error. Because each IF statement is evaluated independently, 95 satisfies all three conditions (> 90, > 80, > 70). The fix is to use IF/ELSE IF/ELSE so that only the first matching condition executes.
Q: What is the difference between iterative and incremental development?
A: Iterative development builds a working prototype and revisits earlier stages to refine it in repeated cycles. Incremental development breaks the program into smaller pieces, tests each one individually, and adds them to the whole one at a time.
Q: A programmer writes DISPLAY(10/0). The program starts but then crashes. What type of error is this?
A: This is a runtime error. The code is syntactically correct, but dividing by zero is undefined, which causes the program to crash during execution.
Q: Why is program documentation important, and what is its most common form?
A: Documentation helps programmers understand how code works and supports collaboration. The most common form is comments, which are written directly in the code and explain what specific sections do.
Error types reappear throughout Big Idea 3 (Algorithms and Programming) when you trace through code and debug it.
The concept of abstraction introduced here (hiding complexity, focusing on what matters) is central to Big Idea 2 (Data) and Big Idea 3.
Collaboration principles connect to Big Idea 5 (Impact of Computing), where crowdsourcing and open-source development build on the same ideas at a larger scale.
programming, software development, collaboration, pair programming, iterative development, incremental development, debugging, syntax error, logic error, runtime error, overflow error, program documentation, comments, code comments, library, API, application program interface, user interface, UI, event-driven programming, sequential programming, camel case, naming conventions, AP CSP, AP Computer Science Principles, Big Idea 1