Software Design Quiz

Q: What is the ideal state for a software system? A: Low Coupling, High Cohesion — modules

are independent but internally focused. - High Coupling, High Cohesion - Low Coupling, Low Cohesion - Low Coupling, High Cohesion - High Coupling, Low Cohesion

Q: What does Cohesion measure? A: Intra-dependency within a module — how focused its

internal responsibilities are. - Inter-dependency between modules - Intra-dependency within a module - Number of lines of code - Number of developers

Q: Which design approach starts with the overall system and breaks it down? A: Top-Down —

begin with the system as a whole, then decompose into smaller modules. - Bottom-Up - Top-Down

• Object-Oriented - Agile

Q: Which coupling type is considered the worst? A: Content coupling — one module directly

modifies the internal data of another. - Data coupling - Stamp coupling - Content coupling - Control coupling

Q: Which architectural style separates an application into Model, View, and Controller? A:

MVC — used by most web frameworks to separate data, UI, and input handling. - Layered - MVC - Microservices - Event-driven

Q: The Singleton pattern belongs to which category? A: Creational patterns — controls

object creation by ensuring only one instance exists. - Creational - Structural - Behavioral - Architectural

Q: Which usability heuristic says users should be able to undo their actions? A: User

control and freedom — users often perform actions by mistake; they need an “emergency exit.” - Consistency and standards - User control and freedom - Error prevention - Recognition rather than recall