Modual Design

Q1 Define Modular Design

Modular software design is the process of breaking larger chunks of code into smaller sections.

What is Cohesion?

Definition: Cohesion measures how well the elements of a module or class work together to achieve a common goal. It's a way of keeping related things together and unrelated things out Importance: High cohesion is desirable because it leads to more readable, maintainable, and modular code. Example A module that handles all the operations related to user authentication, such as logging in, logging out, and managing passwords, has high cohesion. Contrast with coupling Coupling is a measure of how dependent one module or class is on another module or class

What does it mean for a module to have low coupling?

• What is Coupling?
• How interconnected modules are

• A module with low coupling means it has less connections. This means it is easier to test and reuse code!

What are main reasons modular design is important?

1. It is very flexible, you can easily update your design.
2. It is easier to understand.
3. They are scalable, meaning you can easily expand your design.

How will you know if your design is modular?

• Your design will have clearly separated systems and boundaries
• Utilize packages and interfaces