1 | 16 | ||||||||||||||||||||||||
2 | |||||||||||||||||||||||||
3 | |||||||||||||||||||||||||
4 | |||||||||||||||||||||||||
13 | |||||||||||||||||||||||||
5 | |||||||||||||||||||||||||
6 | 17 | ||||||||||||||||||||||||
14 | 7 | ||||||||||||||||||||||||
8 | |||||||||||||||||||||||||
15 | |||||||||||||||||||||||||
9 | |||||||||||||||||||||||||
10 | |||||||||||||||||||||||||
11 | |||||||||||||||||||||||||
12 | |||||||||||||||||||||||||
1. A technique that conceals the inner workings of a procedure and reveals only the essential information.
2. The ability to execute tasks with optimal resource usage.
3. starting with small details and gradually building up to a complete understanding.
4. Starting with a high-level overview and breaking the problem down into more detailed sub-tasks
5. A mechanism to create a new class using properties and behaviors of an existing class.
6. Simplifying complex concepts or systems by focusing on essential features while ignoring unnecessary details.
7. Breaking a system into smaller, loosely-coupled components that can be independently developed and maintained.
8. The ease with which modifications can be made to a codebase.
9. The ability to use existing code in multiple programs or contexts.
10. How easily the code can be understood by humans.
11. Dividing a program into separate modules or parts, each of which is responsible for a specific piece of functionality.
12. A command used in a subprogram to show the specific value that will be given back to the main program
13. Breaking a problem into smaller, more manageable parts, solving them individually, and then combining the solutions.
14. The arrangement of elements or components into a structure that mirrors their relative significance or connections.
15. A program module that performs a specific task within a larger program.
16. The process of dividing a complex problem or system into smaller, more manageable subproblems or components.
17. A simplified interface is provided to hide the complexity of lower-level components.