Study guide: Plan 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.
Ideas to explain in your own words
- A requirement describes needed behavior; an acceptance criterion defines observable evidence that it is met. Criteria should include realistic input, expected result and conditions. A vague claim such as easy to use cannot be checked without a task and method. Use fictional users and data for tests.
- Version history records intentional revisions and their relationships. When two edits share a base, a later editor should inspect both changes before combining them. Keeping history helps trace behavior and support rollback. Replacing newer work with an old snapshot can remove corrections even if the old build still runs.
- A test report should identify the environment, inputs, actions and observed results. Built-application tests, previews and live tests are different evidence. Synthetic accounts protect real work while enabling reproducible scenarios. Clearly record unavailable checks instead of promoting another test’s result to broader coverage.
- A rollback returns application behavior to a known prior state. It should not replace production learner data with old fixtures. Changes to stored-data meaning may require compatibility or a safe migration plan. A release checkpoint is useful only when its application and data assumptions are documented.
Useful vocabulary
- acceptance criterion
- An observable condition showing required behavior.
- revision
- An identified state in version history.
- rollback
- Returning behavior to a known prior compatible state.
Watch your reasoning
- A count of feature names is not an acceptance test.
- A higher-looking label is not proof that all intended changes were preserved.
- A static page response does not prove a button’s interactive behavior.
- Restoring an old database dump can erase newer learner work.
A worked review example
User needs to complete the form without a mouse. Which criterion addresses the need? The supported answer is Keyboard task completes. Translate the stated need into a specific observable task result. A count of feature names is not an acceptance test. A requirement describes needed behavior; an acceptance criterion defines observable evidence that it is met. Known prior application reads current record format safely. Which rollback plan is described? The supported answer is Compatible application rollback. Check application/data compatibility and preserve current records when reverting behavior. Restoring an old database dump can erase newer learner work. A rollback returns application behavior to a known prior state.
Make a practice plan
- Make a four-row summary, one row for each lesson, with its computing idea and one worked decision.
- Explain one tempting mistake using the actual supplied example.
- Complete the new unit review before consulting its explanations.
- Try the transfer task on paper and compare your evidence against the model response.