| 1 | 14 | ||||||||||||||||||||||||
| 12 | 2 | ||||||||||||||||||||||||
| 3 | |||||||||||||||||||||||||
| 4 | |||||||||||||||||||||||||
| 16 | 17 | ||||||||||||||||||||||||
| 5 | |||||||||||||||||||||||||
| 6 | 15 | ||||||||||||||||||||||||
| 7 | 13 | ||||||||||||||||||||||||
| 8 | |||||||||||||||||||||||||
| 9 | |||||||||||||||||||||||||
| 10 | |||||||||||||||||||||||||
| 11 |
1. The technique of simplifying intricate data by offering a high-level interface.
2. A data type that specifies only the functionality and not the specific way it is implemented.
3. A technique that conceals the inner workings of a procedure and reveals only the essential information.
4. The ease with which modifications can be made to a codebase.
5. The process of dividing a complex problem or system into smaller, more manageable subproblems or components.
6. A subroutine that executes specific tasks within a program and provides a returned value when called.
7. The arrangement of elements or components into a structure that mirrors their relative significance or connections.
8. A command in a program that activates a subprogram allowing it to run and perform its tasks.
9. A command used in a subprogram to show the specific value that will be given back to the main program
10. Breaking a system into smaller, loosely-coupled components that can be independently developed and maintained.
11. The ability to present the same interface for different underlying data types.
12. Breaking a problem into smaller, more manageable parts, solving them individually, and then combining the solutions.
13. The ability to use existing code in multiple programs or contexts.
14. A program module that performs a specific task within a larger program.
15. A modular, reusable, and self-contained part of a larger system.
16. A simplified interface is provided to hide the complexity of lower-level components.
17. The distribution of power, authority, and decision-making to lower-level entities or individuals.