Turn a User Need into an Acceptance Criterion
Translate the stated need into a specific observable task result.
About 22 minutes, plus any extended practice
Open lesson 1Plan Inclusive and Reviewable Software
Write acceptance criteria for saving/returning and private-account separation. Describe a synthetic test and a rollback that preserves current records.
Before you begin
- Read a requirement and distinguish test environments.
Choose by skill rather than age alone. Read with an adult when useful, revisit a lesson, or explore another grade.
Follow the lesson sequence
Use Version History to Reconcile Changes
Compare the common base and both intended changes before integrating them.
About 22 minutes, plus any extended practice
Open lesson 2Document a Test as Evidence with Scope
State exactly which environment and behavior were exercised.
About 22 minutes, plus any extended practice
Open lesson 3Plan a Data-Compatible Rollback
Check application/data compatibility and preserve current records when reverting behavior.
About 22 minutes, plus any extended practice
Open lesson 4Review and transfer
After the lessons, try 4 new review cases and a practical task. Each answer has an explanation and a link back to the related lesson.
Open the unit reviewGuest answers are temporary. Keep your own paper or document; this unit does not certify completion or record a school grade.
Topic references
- 2026 CSTA PK–12 Computer Science Standards: topic reference — Human-Centered Design; Inclusive Collaboration
These references informed the topic selection. They do not certify complete standards alignment.