| 1 | 12 | 14 | |||||||||||||||||||||||
| 2 | 15 | ||||||||||||||||||||||||
| 3 | |||||||||||||||||||||||||
| 4 | |||||||||||||||||||||||||
| 13 | |||||||||||||||||||||||||
| 5 | 17 | ||||||||||||||||||||||||
| 16 | |||||||||||||||||||||||||
| 6 | |||||||||||||||||||||||||
| 11 | 7 | ||||||||||||||||||||||||
| 8 | |||||||||||||||||||||||||
| 9 | |||||||||||||||||||||||||
| 10 | |||||||||||||||||||||||||
1. A technique that conceals the inner workings of a procedure and reveals only the essential information.
2. The distribution of power, authority, and decision-making to lower-level entities or individuals.
3. The ability to present the same interface for different underlying data types.
4. starting with small details and gradually building up to a complete understanding.
5. The ease with which modifications can be made to a codebase.
6. Simplifying complex concepts or systems by focusing on essential features while ignoring unnecessary details.
7. A data type that specifies only the functionality and not the specific way it is implemented.
8. A simplified interface is provided to hide the complexity of lower-level components.
9. The process of dividing a complex problem or system into smaller, more manageable subproblems or components.
10. A mechanism to create a new class using properties and behaviors of an existing class.
11. A subprogram that is callable within a program and executes a specific task, but does not return a value.
12. The ability to use existing code in multiple programs or contexts.
13. A command used in a subprogram to show the specific value that will be given back to the main program
14. How easily the code can be understood by humans.
15. The bundling of data and methods that operate on that data within a single unit.
16. A program module that performs a specific task within a larger program.
17. The ability to execute tasks with optimal resource usage.