Coupling and Modularity

This chapter is from the book

Balancing Coupling in Software Design: Universal Design Principles for Architecting Modular Software Systems

Learn More Buy

This chapter is from the book

This chapter is from the book 

Balancing Coupling in Software Design: Universal Design Principles for Architecting Modular Software Systems

Learn More Buy

Quiz

1. What are the basic properties of a module?

1. API, database, and business logic

2. Source code

3. Function and logic

4. Function, logic, and context

2. What makes an effective module?

1. Runtime performance

2. Maximizing the complexity it encapsulates

3. Maximizing the complexity it encapsulates while supporting the system’s flexibility needs

4. Correct implementation of the business logic

3. Which property of a module is the most explicit?

1. Function

2. Logic

3. Context

4. Answers B and C are correct.

4. Which of the following software design elements can be considered modules?

1. Services

2. Namespaces

3. Classes

4. All of the answers are correct.

5. What makes an effective abstraction?

1. Omitting as much information as possible

2. Retaining as much detail as possible

3. Creating a language that allows discussing about functionalities of components, without having to know how they are implemented

4. Describing as many objects as possible