Develop, test, document, and explain programs while preparing for the official Create task and exam.
5 lessons10 estimated blocksAP topics 1.1–1.4 and integrated Big Idea 315 original exam questions
Unit overview
Use these lessons like the Algebra II and Physics pages: read the notes, learn the vocabulary, follow a worked example, attempt the quick checks before revealing solutions, and make a prediction before running the investigation.
10 blocks85-minute blocks, approximately 15–16 in the 16-week map
5 lessonsNotes, examples, vocabulary and quick checks
15 questionsFilterable exam-style bank
Success criteria
Define program purpose and intended users.
Develop tests for program features and boundaries.
Identify official submission components.
Explain algorithm behavior and how procedures manage complexity.
Apply exam-style pseudocode and concepts across units.
Course model: CodeHS for targeted coding, this page for conceptual understanding, and AP Classroom for official aligned assessment. This is an original supplementary resource, not an official College Board publication.
Lesson map
Lesson numbering on this page is site-specific. CodeHS uses a different lesson numbering system.
Each lesson ends with two quick checks. Open each answer only after attempting the problem.
Lesson 8.1 · AP 1.1–1.3 · 1–2 blocks
Purpose, users and design cycles
CodeHS: 18.1 Intro to Design Thinking; 18.2 Prototype
Learning targets
Define program purpose and intended users.
Use an iterative design cycle informed by feedback.
Core notes
A program has an intended purpose, a function, inputs, and outputs. Plan with a problem statement and success criteria, build a small prototype, collect evidence from users, and revise. Iteration is not simply repeating work; it is improving the design in response to tests and observations.
Vocabulary
purpose reason a program exists
function what a program does
prototype early version for testing
iteration repeated refinement
Worked example
A flashcard app aims to help students study. Its function displays questions and tracks responses. User testing reveals whether controls are understandable.
Try it · Check your understanding
1. How do purpose and function differ?Show solution
Purpose is the goal; function describes its behavior.
2. What makes user feedback actionable?Show solution
Specific observations tied to a requirement or usability problem.
CodeHS: 18.3 Test; 18.4 Project Prep and Development
Learning targets
Develop tests for program features and boundaries.
Document expected and observed outcomes.
Core notes
A test should specify the input, expected outcome, actual outcome, and interpretation. Test typical, boundary, and invalid inputs where appropriate. Debugging includes reproducing the problem and isolating the incorrect logic. Documentation helps others understand a system without reading every implementation detail.
Vocabulary
test plan systematic checks
expected output correct predicted result
actual output observed result
debugging locate and fix faults
Worked example
For a grade tracker accepting 0–100, test 0, 100, a typical value, and any invalid values the interface might accept.
Try it · Check your understanding
1. Why document expected results before execution?Show solution
It prevents changing expectations after seeing the output.
2. Is a successful ordinary test enough?Show solution
No; boundary and alternative path tests are still needed.
Lesson 8.3 · AP 1.1–1.4, 3.2, 3.9–3.13 · 1–2 blocks
Create requirements and independent planning
CodeHS: 16.1 Create Performance Task: Overview; 16.2 Guidelines; 16.3 Categories and Questions; 16.4 Planning and Pacing
Learning targets
Identify official submission components.
Distinguish allowed preparation from restricted official task assistance.
Core notes
The official Create task requires program code, a video demonstration, and a Personalized Project Reference. Your work must meet the current College Board directions and rules. Analyze sample programs and practice the required features before beginning official task time; once it begins, follow all restrictions on collaboration, feedback and AI tools.
Vocabulary
Create task official programming performance task
PPR Personalized Project Reference
submission final uploaded component
independent work work subject to task rules
Worked example
A program with a list, a student-developed procedure, and an algorithm combining sequencing, selection and iteration can be analyzed for whether each feature meets the official criteria.
Try it · Check your understanding
1. Can an ordinary code comment replace the required video?Show solution
No; official submissions include distinct components.
2. Where should students verify exact task rules?Show solution
Current College Board Create task instructions in AP Classroom/Digital Portfolio.
Explain algorithm behavior and how procedures manage complexity.
Write precise testing and error explanations.
Core notes
AP written responses require specific evidence from a program and Personalized Project Reference. Avoid generic statements such as “it helps my code”; name variables, parameters, control flow, inputs, and expected outcomes. Practice independently with non-submission sample programs before the official task.
Vocabulary
program behavior what it does for inputs
algorithm explanation ordered description of steps
data abstraction collection hides repeated individual variables
procedural abstraction named procedure manages detail
Worked example
A procedure checks entries in a score list using a loop; a clear explanation identifies the list, loop behavior, and the returned or displayed result.
Try it · Check your understanding
1. Why mention a concrete input in a response?Show solution
It grounds the explanation in observable program behavior.
2. What does a strong testing explanation include?Show solution
Inputs, expected results and what a result would demonstrate.
Apply exam-style pseudocode and concepts across units.
Identify misconceptions and target remediation.
Core notes
Exam preparation should include mixed practice: data representation, control structures, algorithms, networks, impacts, and Create explanations. Review wrong answers by misconception, not just score. The official pseudocode reference sheet is permitted as specified by the exam. Use AP Classroom for official item banks.
Vocabulary
retrieval practice recall without notes
distractor plausible wrong choice
misconception persistent incorrect model
remediation targeted correction
Worked example
If a student confuses 1-based AP list indexing with 0-based Python indexing, targeted list-state practice is more useful than repeating an unrelated Python project.
Try it · Check your understanding
1. Why mix topics on practice exams?Show solution
It requires choosing strategies without a unit label as a cue.
2. What should follow an incorrect answer?Show solution
Identify the reasoning error, then retry a parallel problem.
Core video selection: The matching CodeHS lesson video and AP Daily topic video for each lesson. Direct AP Daily videos are accessed inside the school's AP Classroom enrollment and may not have public URLs.
Lesson 8.1: Purpose, users and design cycles. Watch the matched CodeHS lesson video and the corresponding AP Daily topic video for 1.1–1.3; pause to answer the notes prompt before the interactive lab. AP Daily requires student login.
Lesson 8.2: Test cases, debugging, and documentation. Watch the matched CodeHS lesson video and the corresponding AP Daily topic video for 1.3–1.4; pause to answer the notes prompt before the interactive lab. AP Daily requires student login.
Lesson 8.4: Written responses and evidence-based explanation. Watch the matched CodeHS lesson video and the corresponding AP Daily topic video for 1.4, 3.2, 3.9–3.13; pause to answer the notes prompt before the interactive lab. AP Daily requires student login.
Lesson 8.5: Mixed review and exam habits. Watch the matched CodeHS lesson video and the corresponding AP Daily topic video for All Big Ideas; pause to answer the notes prompt before the interactive lab. AP Daily requires student login.
Video selections are topic- and platform-matched. Teachers should check account availability and assign individual CodeHS/AP Daily clips from their course dashboards.
Interactive inquiry · Program evidence & written-response trainer
Make a prediction, manipulate the model, record observations, and explain whether your original thinking was correct.
Student lab record: Before you start, write your prediction and reasoning. Afterward, record at least two trials and an evidence-based conclusion. This model is illustrative and its limitations should be noted.
Program evidence builder · Practice only
Use the fictional program below to prepare written-response explanations. Do not enter or upload official Create-task source code or your submitted Personalized Project Reference into this tool.
PROCEDURE countHigh(scores, threshold) {
count ← 0
FOR EACH item IN scores {
IF (item > threshold) {
count ← count + 1
}
}
RETURN(count)
}
DISPLAY(countHigh([3, 9, 6, 10], 7))
Official Create task: use current College Board directions; the minimum nine in-class hours are protected task time, and assistance rules differ from ordinary practice.
Investigation record
Lab responses stay in this page; they are not uploaded or stored on a server.
AP-style practice & self-check
Original multiple-choice questions focus on reasoning, not just coding. Filter by lesson and difficulty. Show explanations in practice mode or hide them in exam mode.
Mastery target: 80% on mixed original questions, plus a clear written explanation on one unfamiliar scenario. Treat the bank as practice, not a secure test.
Teacher lesson specifications & implementation
Teacher-facing scope, exact learning goals, CodeHS alignments, and assessment requirements. This section can be hidden or separated before student publishing.
Pacing and lesson allocation
10 × 85-minute blocks. Shorten or extend CodeHS programming time based on prior experience and how many blocks actually meet; all lessons are supplemental to the main CodeHS course.
Default block: 10 min retrieval · 20 min notes/video · 20 min inquiry · 25 min selected CodeHS/independent practice · 10 min quick assessment.
Lesson
AP
CodeHS
Measurable targets
Assessment specifications
8.1 Purpose, users and design cycles
1.1–1.3
18.1 Intro to Design Thinking; 18.2 Prototype
Define program purpose and intended users.; Use an iterative design cycle informed by feedback.
40 points: 20 original AP-style multiple-choice questions (1 point each), four short-answer reasoning prompts (3 points each), and one 8-point novel investigation/analysis. Mix current-unit and prior-unit topics. Use AP Classroom separately for official question practice.
Assessment and feedback strategy
Independent predictions precede each simulation.
Students justify one wrong multiple-choice distractor in writing.
Teacher verifies model limitations, not just numeric answers.
Repeat key pseudocode and binary ideas in later units.