Question

multiple choice questions
answer the following multiple choice questions about the reading.

1. in the context of software development, which of the following best describes the purpose of decomposition?

a. creating a single, unified interface for all software components.
b. combining multiple programs into a single, larger application.
c. breaking down a complex problem into smaller, more manageable parts.
d. hiding the complex details of how something works from the user.

1. which of the following is the most accurate analogy for abstraction in software development, based on the passage?

a. sorting lego bricks by size and color before building a castle.
b. dividing a library management program into modules for checkouts, accounts, and searching.
c. using a pre - built function to calculate a square root without knowing the specific algorithm.
d. writing a single, 1000 - line program instead of two 500 - line programs.

1. why are both decomposition and abstraction important in software development?

a. to increase the overall size and scope of software projects.
b. to manage complexity, improve understanding, and facilitate teamwork.
c. to eliminate the need for testing and debugging.
d. to make code more difficult to read and modify, ensuring job security.

Explanation:

Question 1

To solve this, we analyze each option:

• Option A: Decomposition is not about creating a unified interface; it's about breaking down, so A is wrong.
• Option B: Decomposition is not combining programs; it's breaking down, so B is wrong.
• Option C: Decomposition in software development means breaking a complex problem into smaller, manageable parts. This matches the definition.
• Option D: Hiding details is abstraction, not decomposition.

Analyze each option for abstraction (hiding complex details, using high - level concepts):

• Option A: Sorting Lego bricks is about organization, not abstraction.
• Option B: Dividing a program into modules is decomposition, not abstraction.
• Option C: Using a pre - built function without knowing the algorithm is abstraction (hiding the complex algorithm details).
• Option D: Writing a longer program instead of two shorter ones is not related to abstraction.

Analyze each option for the importance of decomposition and abstraction:

• Option A: Decomposition and abstraction are not for increasing project size/scope.
• Option B: Decomposition (breaking into parts) and abstraction (hiding details) help manage complexity, improve understanding, and make teamwork easier (different team members can work on different parts).
• Option C: They don't eliminate testing/debugging.
• Option D: They make code easier to read/modify, not more difficult.

Answer:

C. Breaking down a complex problem into smaller, more manageable parts.

Question 2