| 1 | 11 | 17 | |||||||||||||||||||||||
| 2 | 15 | 16 | |||||||||||||||||||||||
| 3 | |||||||||||||||||||||||||
| 14 | |||||||||||||||||||||||||
| 12 | 4 | ||||||||||||||||||||||||
| 5 | |||||||||||||||||||||||||
| 6 | |||||||||||||||||||||||||
| 7 | |||||||||||||||||||||||||
| 8 | 13 | ||||||||||||||||||||||||
| 9 | |||||||||||||||||||||||||
| 10 | |||||||||||||||||||||||||
1. The technique of simplifying intricate data by offering a high-level interface.
2. A program module that performs a specific task within a larger program.
3. A command in a program that activates a subprogram allowing it to run and perform its tasks.
4. How easily the code can be understood by humans.
5. A subprogram that is callable within a program and executes a specific task, but does not return a value.
6. The bundling of data and methods that operate on that data within a single unit.
7. The reduction of complexity by hiding implementation details.
8. The ease with which modifications can be made to a codebase.
9. The ability to present the same interface for different underlying data types.
10. The ability to execute tasks with optimal resource usage.
11. A simplified interface is provided to hide the complexity of lower-level components.
12. The principle of breaking down a program into smaller, manageable sections.
13. A mechanism to create a new class using properties and behaviors of an existing class.
14. The ability to use existing code in multiple programs or contexts.
15. A data type that specifies only the functionality and not the specific way it is implemented.
16. A subroutine that executes specific tasks within a program and provides a returned value when called.
17. A command used in a subprogram to show the specific value that will be given back to the main program