Big idea. Hiding detail behind a clear name and a clear interface is what lets people build large programs from small parts they can trust.
Outcomes served. O6 (design a solution from functions and suitable data structures).
Plan your six hours
| Part | Minutes |
|---|---|
| Opener and orientation (this page) | 15 |
| M6.L1 Abstraction and decomposition | 55 |
| M6.L2 Functions | 50 |
| M6.L3 Lists and dictionaries | 50 |
| M6.L4 Modular design and testing | 50 |
| Practice set | 35 |
| Lab: Design a fines function | 50 |
| Mastery checkpoint | 30 |
| Discussion prompt and recap | 25 |
| Total | 360 (6 hours) |
Assumed. Modules 1 to 5: stating methods, conditions, searching and sorting and counting cost. You will reuse conditions and step tracing.
Where this topic appears in practice. Every app, spreadsheet formula or form is built from named parts that call each other. Being able to read the parts, their inputs and their outputs lets you judge a design and spot where an error must be. See the encyclopedia entry on the programming language.
Privacy. Your answers stay with you. This course does not store, collect or send anything you write or tick.