Creative Development
Creative Development: Name the objects and notation before applying a rule.
Turn the remaining weeks into a repeatable cycle of retrieval, repair, mixing, and timed rehearsal.
Move through the content map twice: first for understanding and repair, then for mixed retrieval and timing.
Creative Development: Name the objects and notation before applying a rule.
Data: Connect the symbolic form to a graph, diagram, table, or example.
Algorithms and Programming: Compare two methods and record when each one is valid.
Computer Systems and Networks: Finish with an unfamiliar problem and an independent check.
Impact of Computing: Name the objects and notation before applying a rule.
Repeat this pattern with the highest-risk content area still on your list.
Rebuild definitions, diagrams, and relationships from memory.
Study the smallest missing connection and solve a changed example.
Place the repaired idea beside neighboring content areas.
Use the actual time, calculator, and reference constraints.
| Section | Time | Questions | Pacing note |
|---|---|---|---|
| End-of-course multiple choice | 2 hours | 70 questions | About 1.7 minutes each. Code-tracing items are slower, so bank time on the vocabulary and impact items. |
| Create Performance Task | Through-course | Program plus written responses | Done during the year, not on exam day. Start it early enough to record the video and write the responses without rushing. |
| Verb | What earns credit |
|---|---|
| Identify | Name the line, the variable, or the procedure. One phrase. |
| Describe | Say what it does from the outside - What goes in and what comes out. |
| Explain how | Walk through the logic step by step, referring to your own code by name. |
| Justify why | Say what problem this choice solved - Why the list, why the procedure, why the parameter. |
| Trace the algorithm | Write a table of variable values after each pass. Guessing from the shape of the code is where most errors happen. |
| Section | Rule | Detail |
|---|---|---|
| End-of-course multiple choice | No calculator | Binary, compression ratios, and speedup are all small mental arithmetic. |
| Provided during the exam | Exam Reference Sheet | The pseudocode language is given to you. It is not Python or JavaScript, and reading it as if it were is a common way to lose easy points. |
| Create Performance Task | Not applicable | Built during the course on a computer, submitted before exam day, and scored separately. |
Week 1 is “Diagnose and start the Create task” and you finish it with one thing you keep: An error log plus a chosen Create-task idea with a list and a procedure already sketched. Week 8 is “Full timed rehearsal”. Start at the week that matches the time you have left, not at week one.
End-of-course multiple choice - About 1.7 minutes each. Code-tracing items are slower, so bank time on the vocabulary and impact items. Create Performance Task - Done during the year, not on exam day. Start it early enough to record the video and write the responses without rushing.
Name the line, the variable, or the procedure. One phrase. Answering a different verb can be mathematically correct and still score zero.
The task also needs a list (or other collection) used to manage complexity. Storing one value in a list does not count - The program has to be genuinely harder without it.