Modular Design

MODULAR DESIGN

Q1 DEFINE MODULAR DESIGN

Modular design is a way of creating something that breaks it into smaller, more attainable parts. This makes testing and setting smaller goals easier because you can break your large project into smaller chunks

Q2 What is Cohesion?

Public Final String Cohesion = "the measurement of how well elements of a module are designed to work together to reach a common goal."

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

Lower coupling means the mnodules are more independent from the other modules in the system

Q4 What are the three main reasons that modular design is important?

switch(getReasons) { case 1:you can keep to a budget, its easier to divide up work. break;case 2:System will be more maintainable, easier to understand system as a wholebreak;case 3:System will be reliable, you will understand the whole system and its flawsbreak;default:// do nothing}

Q5 How will you know if your design is modular

You will know if your design is modular because you are able to test the independent modules to ensure they work, before combining it into the full project

Q6 What do you understand by layered design?

Layered design divides the project into multiple layers, each with a specific role and responsibility

Q7 GIve two examples of layered design in real-life complex software.

a web-based online banking system and an e-commerce platform; both typically utilize a three-tier system of client side, business side, and then database access side

Q8 What are a few outstanding benefits of using layered design?

Managing complexity, portability, maintainability, reusability, and creating a blueprint for constructing the system are all outstanding benefits of using layered design.