Lecture 1: Quiz

Why do we need software design?

• To speed up coding without planning

• To describe the structure of software at a higher level of abstraction to reduce complexity

• To standardize tools across the team so development proceeds uniformly

• To increase software production costs

What does PHAME stand for in the context of Software Design?

• Patterns, Hierarchy, Aggregation, Modularity, Encapsulation

• Protocols, Heuristics, Abstraction, Modularity, Extensibility

• Principles of Hierarchy, Abstraction, Modularization, and Encapsulation

• Process, Handling, Association, Modeling, Encapsulation

What key difference distinguishes a software component from a module?

• Components cannot be composed by third parties; modules can.

• Modules have contractually specified interfaces; components do not.

• Components can be deployed independently, modules cannot.

• Modules have explicit context dependencies; components do not.

Which challenge is emphasized in top-down design.

• Reworking existing designs

• Deciding when to stop decomposition and avoiding duplicated design.

• Identifying basic design elements

• Components lack well-defined interfaces.

Which pairing is the recommended rule of thumb for maintainable design?

• High coupling & high cohesion

• Low coupling & low cohesion

• Low coupling & high cohesion

• High coupling & low cohesion

What is the problem with high coupling in software design?

• Makes the system easier to maintain

• Requires fewer code changes

• Lowers Intra-module binding

• Decreases maintainability

Which type of coupling should you avoid at all costs?

• Loose coupling

• Cyclic coupling

• Parallel coupling

• Cascading coupling

What is the aim of Separation of Concerns (SoC)?

• Mix aspects to reduce complexity and reuse code.

• Focus each unit on a single responsibility to avoid mixing aspects.

• Hide public interfaces and expose implementation details.

• Prefer technology-driven design over domain concepts.

How do abstraction and encapsulation relate?

• Abstraction hides implementation; encapsulation defines behavior.

• Abstraction defines observable behavior; encapsulation hides details.

• Both mean making attributes public via getters/setters.

• Both refer to inheritance hierarchies.

Which principle warns against adding functionality before it is required?

• DRY

• KISS

• YAGNI

• SOLID