| 1 | 12 | ||||||||||||||||||||||||
| 2 | |||||||||||||||||||||||||
| 14 | |||||||||||||||||||||||||
| 3 | 17 | ||||||||||||||||||||||||
| 4 | 11 | ||||||||||||||||||||||||
| 5 | |||||||||||||||||||||||||
| 13 | |||||||||||||||||||||||||
| 15 | 16 | ||||||||||||||||||||||||
| 6 | |||||||||||||||||||||||||
| 7 | |||||||||||||||||||||||||
| 8 | |||||||||||||||||||||||||
| 9 | |||||||||||||||||||||||||
| 10 | |||||||||||||||||||||||||
1. Dividing a program into separate modules or parts, each of which is responsible for a specific piece of functionality.
2. Breaking a system into smaller, loosely-coupled components that can be independently developed and maintained.
3. A data type that specifies only the functionality and not the specific way it is implemented.
4. How easily the code can be understood by humans.
5. A simplified interface is provided to hide the complexity of lower-level components.
6. The arrangement of elements or components into a structure that mirrors their relative significance or connections.
7. Simplifying complex concepts or systems by focusing on essential features while ignoring unnecessary details.
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. The process of dividing a complex problem or system into smaller, more manageable subproblems or components.
11. The technique of simplifying intricate data by offering a high-level interface.
12. The ability to use existing code in multiple programs or contexts.
13. The ability to present the same interface for different underlying data types.
14. The distribution of power, authority, and decision-making to lower-level entities or individuals.
15. A command in a program that activates a subprogram allowing it to run and perform its tasks.
16. Starting with a high-level overview and breaking the problem down into more detailed sub-tasks
17. A command used in a subprogram to show the specific value that will be given back to the main program