AP® Computer Science Principles Unit 1 flashcardsCreative Development
33 cards · about 8 minutes for the whole deck
Flashcard drill
Space flips the card, arrow keys move, and keys 1 to 4 rate how well you knew it.
- Position
- 1 / 33
- Due
- 33
- Mastered
- 0 / 33
This card: New
Flip the card before you rate it.
Computing innovation
Something new that has a program as a key part of how it works. It can be physical (a self-driving car), software (a photo editor) or an idea (online shopping).
Topic 1.1: Collaboration
Collaboration
Working with other people to build something. Teams with different talents and viewpoints usually make better programs than one person alone.
Topic 1.1: Collaboration
Diverse perspectives
Viewpoints from people with different backgrounds, skills and experiences. They help a team spot problems and bias that one group would miss.
Topic 1.1: Collaboration
Pair programming
Two programmers share one computer: the driver types the code and the navigator reviews each line and thinks ahead. They swap roles often.
Topic 1.1: Collaboration
Online collaboration tools
Shared documents, code repositories and chat that let teammates share ideas and give feedback on each other's work, even when they're apart.
Topic 1.1: Collaboration
Interpersonal skills
Skills for working well with people, like communicating clearly, building consensus, resolving conflicts and negotiating. Strong teams practice them.
Topic 1.1: Collaboration
Program (software)
A set of instructions that does a specific job when a computer runs it.
Topic 1.2: Program Function and Purpose
Code segment
A group of program statements that's part of a larger program.
Topic 1.2: Program Function and Purpose
Program purpose
Why a program exists: the problem it solves or the creative interest it lets people pursue. Knowing it helps you design and test the program.
Topic 1.2: Program Function and Purpose
Program behavior (function)
What a program does while it runs, often explained through what happens when a user interacts with it. It answers "what does it do?" rather than "why?"
Topic 1.2: Program Function and Purpose
Input
Data sent to a program for it to process. It can be typed text, a tap, a sound, a picture, or data from another program.
Topic 1.2: Program Function and Purpose
Output
Data a program sends to a device, like text on a screen, a sound or a vibration. It usually depends on the input or on values the program already has.
Topic 1.2: Program Function and Purpose
Event
An action, like a click, a key press or the program starting, that supplies input and can trigger code to run.
Topic 1.2: Program Function and Purpose
Event-driven programming
A style where code runs when an event triggers it (a button tap, say), instead of running straight through from top to bottom.
Topic 1.2: Program Function and Purpose
Development process
The steps used to build a program: investigating and reflecting, designing, prototyping and testing. It can be planned or exploratory.
Topic 1.3: Program Design and Development
Investigation
Finding out what users need and what limits a program has, through surveys, interviews, user testing and watching people work.
Topic 1.3: Program Design and Development
Program requirements
A description of what a program must do, including how users will interact with it. You need them to choose good test inputs.
Topic 1.3: Program Design and Development
Program specification
The document that sets out a program's requirements. The design phase plans how to meet it.
Topic 1.3: Program Design and Development
Design phase
Planning how a program will work: brainstorming, storyboarding, sketching the user interface, splitting it into parts and planning the testing.
Topic 1.3: Program Design and Development
Prototype
An early, rough version of a program built to try out ideas and get feedback before the full version is made.
Topic 1.3: Program Design and Development
Iterative development
Building a program in cycles, refining and revising it after feedback, testing or reflection. You may go back to earlier phases.
Topic 1.3: Program Design and Development
Incremental development
Building a program one small piece at a time and testing each piece so it works before you connect it to the rest.
Topic 1.3: Program Design and Development
Program documentation
A written description of what a program, procedure or code segment does and how it was built. Write it throughout development, not just at the end.
Topic 1.3: Program Design and Development
Comment
A note written inside a program for people to read. Comments don't change how the program runs.
Topic 1.3: Program Design and Development
Acknowledging code
Crediting code you didn't write yourself, in your documentation, by naming where it came from or who wrote it.
Topic 1.3: Program Design and Development
Logic error
A mistake in the algorithm that makes a program run but behave wrongly, like using > when you meant ≥.
Topic 1.4: Identifying and Correcting Errors
Syntax error
A mistake where the code breaks the language's rules, like a missing bracket, so the program can't run.
Topic 1.4: Identifying and Correcting Errors
Run-time error
An error that happens while the program is running, like using a list index that doesn't exist. Each language defines its own.
Topic 1.4: Identifying and Correcting Errors
Overflow error
An error when a number is too big (or too small) for the fixed number of bits used to store it.
Topic 1.4: Identifying and Correcting Errors
Test case
An input you choose plus the output you expect. If the program's real output doesn't match, you've found an error.
Topic 1.4: Identifying and Correcting Errors
Boundary values
Test inputs at or just past the edges of what's allowed (the smallest and largest values). Errors often hide there.
Topic 1.4: Identifying and Correcting Errors
Hand tracing
Following code step by step on paper, writing down each variable's value, to see what it really does.
Topic 1.4: Identifying and Correcting Errors
Debugger
A tool that lets you pause a program, step through it one line at a time and watch the variables change.
Topic 1.4: Identifying and Correcting Errors