| 1 | 8 | ||||||||||||||||||||
| 2 | |||||||||||||||||||||
| 3 | |||||||||||||||||||||
| 4 | 9 | ||||||||||||||||||||
| 5 | |||||||||||||||||||||
| 6 | |||||||||||||||||||||
| 7 | |||||||||||||||||||||
1. The ability for multiple developers to work on different modules or components simultaneously without interfering with each other.
2. The practice of hiding the internal details of a module or component and providing a well-defined interface or API for interacting with it.
3. The ease with which a system can be modified or customized by changing or extending its modules or components.
4. The capability of a system to handle increased workload or size by adding more modules or components.
5. The capability of different modules or components to seamlessly work together and exchange information or functionality.
6. The ability to contain and isolate faults or bugs within a specific module or component, minimizing the impact on the overall system.
7. The ease with which a system can be maintained or repaired by replacing or updating individual modules or components.
8. The ability of modules or components to be reused in different systems or applications, reducing development time and effort.
9. The ability of a system to easily adapt and change by adding, removing, or modifying its components or modules without affecting other parts of the system.