1 | 14 | ||||||||||||||||||||||||
2 | |||||||||||||||||||||||||
3 | |||||||||||||||||||||||||
4 | |||||||||||||||||||||||||
5 | |||||||||||||||||||||||||
6 | 15 | ||||||||||||||||||||||||
12 | |||||||||||||||||||||||||
7 | |||||||||||||||||||||||||
13 | |||||||||||||||||||||||||
8 | |||||||||||||||||||||||||
9 | 16 | ||||||||||||||||||||||||
10 | |||||||||||||||||||||||||
11 | |||||||||||||||||||||||||
1. How easily the code can be understood by humans.
2. The distribution of power, authority, and decision-making to lower-level entities or individuals.
3. A program module that performs a specific task within a larger program.
4. Dividing a program into separate modules or parts, each of which is responsible for a specific piece of functionality.
5. Starting with a high-level overview and breaking the problem down into more detailed sub-tasks
6. The ability to present the same interface for different underlying data types.
7. A command used in a subprogram to show the specific value that will be given back to the main program
8. The ability to execute tasks with optimal resource usage.
9. A data type that specifies only the functionality and not the specific way it is implemented.
10. The process of dividing a complex problem or system into smaller, more manageable subproblems or components.
11. The bundling of data and methods that operate on that data within a single unit.
12. A mechanism to create a new class using properties and behaviors of an existing class.
13. The arrangement of elements or components into a structure that mirrors their relative significance or connections.
14. starting with small details and gradually building up to a complete understanding.
15. Breaking a system into smaller, loosely-coupled components that can be independently developed and maintained.
16. A modular, reusable, and self-contained part of a larger system.