Software Cohesion Basics Quiz for Grade 10

1. What does cohesion measure in software design?

How closely related functions within a module are

How many lines of code a function contains

The speed at which code executes

The number of variables used in a class

Cohesion in software design refers to the degree to which the elements within a module or component are related and work together to fulfill a single purpose. High cohesion is desirable as it enhances maintainability, readability, and reusability, making the module easier to understand and modify.

Explanation

Cohesion in software design refers to the degree to which the elements within a module or component are related and work together to fulfill a single purpose. High cohesion is desirable as it enhances maintainability, readability, and reusability, making the module easier to understand and modify.

2. High cohesion is generally considered good design practice.

True

False

High cohesion refers to how closely related and focused the responsibilities of a single module or component are. It enhances maintainability, readability, and reusability of code. When a module has high cohesion, it performs a single task effectively, making it easier to understand and modify, which is a fundamental principle of good software design.

Explanation

High cohesion refers to how closely related and focused the responsibilities of a single module or component are. It enhances maintainability, readability, and reusability of code. When a module has high cohesion, it performs a single task effectively, making it easier to understand and modify, which is a fundamental principle of good software design.

3. A class that handles both user authentication and database queries demonstrates ____ cohesion.

A class that combines user authentication and database queries exhibits low cohesion because it performs multiple unrelated tasks. High cohesion is achieved when a class focuses on a single responsibility or closely related functions. Mixing these distinct functionalities makes the class harder to maintain and understand, leading to decreased clarity and increased complexity.

Explanation

A class that combines user authentication and database queries exhibits low cohesion because it performs multiple unrelated tasks. High cohesion is achieved when a class focuses on a single responsibility or closely related functions. Mixing these distinct functionalities makes the class harder to maintain and understand, leading to decreased clarity and increased complexity.

Submit

4. What is coupling in software design?

The degree of interdependence between modules

The total number of functions in a program

How fast data moves between classes

The memory used by a single object

Coupling in software design refers to the extent to which different modules or components rely on each other. Lower coupling is desirable as it promotes modularity, making systems easier to maintain and understand. High coupling can lead to challenges in modifying one module without affecting others, thereby increasing complexity and reducing flexibility.

Explanation

Coupling in software design refers to the extent to which different modules or components rely on each other. Lower coupling is desirable as it promotes modularity, making systems easier to maintain and understand. High coupling can lead to challenges in modifying one module without affecting others, thereby increasing complexity and reducing flexibility.

5. Low coupling means modules are independent and easy to test separately.

True

False

Low coupling refers to a design principle where different modules or components of a system have minimal dependencies on each other. This independence allows for easier testing and maintenance, as changes in one module are less likely to affect others. Consequently, low coupling enhances modularity, making systems more robust and adaptable.

Explanation

Low coupling refers to a design principle where different modules or components of a system have minimal dependencies on each other. This independence allows for easier testing and maintenance, as changes in one module are less likely to affect others. Consequently, low coupling enhances modularity, making systems more robust and adaptable.

6. Which scenario shows high cohesion? (Select all that apply)

A UserAccount class that manages login and password validation

A class that handles both graphics rendering and network communication

A Calculator class that only performs math operations

A module mixing file I/O with email sending

High cohesion refers to a design where components within a class or module are closely related in functionality. The UserAccount class focuses solely on user authentication tasks, while the Calculator class is dedicated to mathematical operations. Both exhibit high cohesion by maintaining a single responsibility and ensuring that their methods work towards a unified purpose.

Explanation

High cohesion refers to a design where components within a class or module are closely related in functionality. The UserAccount class focuses solely on user authentication tasks, while the Calculator class is dedicated to mathematical operations. Both exhibit high cohesion by maintaining a single responsibility and ensuring that their methods work towards a unified purpose.

Submit

7. What problem does tight coupling create?

Changes in one module force changes in dependent modules

Code runs faster

Functions become shorter

Variables use less memory

Tight coupling occurs when modules are highly dependent on each other, meaning that a change in one module necessitates modifications in others. This interdependence can lead to increased maintenance complexity and reduced flexibility, making the system harder to adapt or scale over time.

Explanation

Tight coupling occurs when modules are highly dependent on each other, meaning that a change in one module necessitates modifications in others. This interdependence can lead to increased maintenance complexity and reduced flexibility, making the system harder to adapt or scale over time.

8. A well-designed module should have cohesion and coupling.

High cohesion within a module means that its components are closely related and work together effectively, enhancing maintainability and clarity. Low coupling indicates that the module is largely independent from others, reducing the impact of changes and promoting reusability. Together, these traits contribute to a more robust and flexible software design.

Explanation

High cohesion within a module means that its components are closely related and work together effectively, enhancing maintainability and clarity. Low coupling indicates that the module is largely independent from others, reducing the impact of changes and promoting reusability. Together, these traits contribute to a more robust and flexible software design.

Submit

9. Which design principle helps reduce coupling between classes?

Dependency Injection

Adding more global variables

Making all methods public

Combining all code into one file

Dependency Injection is a design principle that promotes loose coupling between classes by allowing an object's dependencies to be provided externally rather than being hard-coded within the class. This approach enhances modularity, making it easier to manage, test, and maintain code, as changes in one class have minimal impact on others.

Explanation

Dependency Injection is a design principle that promotes loose coupling between classes by allowing an object's dependencies to be provided externally rather than being hard-coded within the class. This approach enhances modularity, making it easier to manage, test, and maintain code, as changes in one class have minimal impact on others.

10. Low cohesion makes code harder to understand and maintain.

True

False

Low cohesion occurs when a module or class has unrelated responsibilities, making it difficult to understand its purpose. This scattering of functionality complicates maintenance, as changes in one area may inadvertently affect others. High cohesion, on the other hand, ensures that related tasks are grouped together, enhancing clarity and ease of maintenance.

Explanation

Low cohesion occurs when a module or class has unrelated responsibilities, making it difficult to understand its purpose. This scattering of functionality complicates maintenance, as changes in one area may inadvertently affect others. High cohesion, on the other hand, ensures that related tasks are grouped together, enhancing clarity and ease of maintenance.

11. Which of these demonstrates low coupling? (Select all that apply)

Using interfaces to define contracts between classes

Directly accessing private variables of another class

Passing dependencies as constructor parameters

Creating circular dependencies between modules

Low coupling refers to minimizing dependencies between components. Using interfaces to define contracts allows classes to interact without needing to know each other's implementations, promoting flexibility. Passing dependencies as constructor parameters further decouples components, as it allows for easier substitution and testing, enhancing modularity and maintainability in the code.

Explanation

Low coupling refers to minimizing dependencies between components. Using interfaces to define contracts allows classes to interact without needing to know each other's implementations, promoting flexibility. Passing dependencies as constructor parameters further decouples components, as it allows for easier substitution and testing, enhancing modularity and maintainability in the code.

Submit

12. Cohesion refers to how well functions within a module work toward a ____ purpose.

Cohesion in software engineering describes the degree to which the elements within a module are related and work together to achieve a single, well-defined purpose. High cohesion indicates that the functions within the module are closely aligned, enhancing maintainability and clarity, while low cohesion suggests a lack of focus, complicating the module's purpose.

Explanation

Cohesion in software engineering describes the degree to which the elements within a module are related and work together to achieve a single, well-defined purpose. High cohesion indicates that the functions within the module are closely aligned, enhancing maintainability and clarity, while low cohesion suggests a lack of focus, complicating the module's purpose.

Submit