Match List I (software design principles) with List II (Definition)
| List I | List II |
|---|---|
| (A) Cohesion | (I) Degree to which one module relies on another module. |
| (B) Coupling | (II) Dividing a software system into distinct modules. |
| (C) Abstraction | (III) Degree to which elements of a module belong together. |
| (D) Modularity | (IV) Simplifying complex reality by modelling classes appropriate to the problem. |
Pick an option to check yourself, or open the answer below.
Show answer & explanation
Correct answer: C. (A)-(III), (B)-(I), (C)-(IV), (D)-(II)
Explanation
Cohesion is how strongly a module's elements belong together (III). Coupling is how much one module relies on another (I). Abstraction simplifies complex reality by modelling appropriate classes (IV). Modularity divides the system into distinct modules (II).More Software Engineering questions
- Given a project with an estimated effort of 1500 person-hours and a team of 5 people, how many days will it take to complete the project if…
- In software configuration management, what is the primary purpose of version control?
- Match List I (Testing Type) with List II (Description)List I List II (A) Unit testing (I) Testing individual components of the software. (B…
- Given a project that uses the COCOMO model with an estimated effort of 2000 person-months and a productivity rate of 5 person-months per KL…
- A test suite consists of:
- A Level-0 DFD is also called a: