| 1 | 15 | 17 | |||||||||||||||||||||||
| 2 | |||||||||||||||||||||||||
| 12 | 3 | ||||||||||||||||||||||||
| 4 | |||||||||||||||||||||||||
| 14 | |||||||||||||||||||||||||
| 5 | |||||||||||||||||||||||||
| 16 | |||||||||||||||||||||||||
| 6 | |||||||||||||||||||||||||
| 7 | |||||||||||||||||||||||||
| 13 | 8 | ||||||||||||||||||||||||
| 9 | |||||||||||||||||||||||||
| 10 | |||||||||||||||||||||||||
| 11 |
1. Starting with a high-level overview and breaking the problem down into more detailed sub-tasks
2. The arrangement of elements or components into a structure that mirrors their relative significance or connections.
3. The ability to execute tasks with optimal resource usage.
4. The process of dividing a complex problem or system into smaller, more manageable subproblems or components.
5. A simplified interface is provided to hide the complexity of lower-level components.
6. The ability to use existing code in multiple programs or contexts.
7. A data type that specifies only the functionality and not the specific way it is implemented.
8. The ease with which modifications can be made to a codebase.
9. starting with small details and gradually building up to a complete understanding.
10. Breaking a problem into smaller, more manageable parts, solving them individually, and then combining the solutions.
11. A command used in a subprogram to show the specific value that will be given back to the main program
12. Breaking a system into smaller, loosely-coupled components that can be independently developed and maintained.
13. A subprogram that is callable within a program and executes a specific task, but does not return a value.
14. The technique of simplifying intricate data by offering a high-level interface.
15. A mechanism to create a new class using properties and behaviors of an existing class.
16. A modular, reusable, and self-contained part of a larger system.
17. A technique that conceals the inner workings of a procedure and reveals only the essential information.