Big idea. A condition is a yes-or-no question about the data, and every decision in a program is built from such questions.
Outcomes served. O3 (use logic and conditions to control which steps a method takes).
Plan your six hours
| Part | Minutes |
|---|---|
| Opener and orientation (this page) | 15 |
| M3.L1 Conditions and true or false | 55 |
| M3.L2 AND, OR and NOT | 50 |
| M3.L3 If and else chains | 50 |
| M3.L4 Testing the boundaries | 50 |
| Practice set | 35 |
| Lab: Specify and test a rule | 50 |
| Mastery checkpoint | 30 |
| Discussion prompt and recap | 25 |
| Total | 360 (6 hours) |
Assumed. Modules 1 and 2: stating a problem, tracing steps by hand and counting in binary. No new mathematics is needed.
Where this topic appears in practice. Every form that validates an entry, every ticket price and every spam filter uses conditions. If you can state a rule exactly and test it at its boundaries, you can check that software follows it. See the encyclopedia entry on the algorithm.
Privacy. Your answers stay with you. This course does not store, collect or send anything you write or tick.