A programming team is using the Waterfall design approach to create an application. Which deliverable would be produced during the design phase?

In the Waterfall model, the design phase is dedicated to creating a detailed technical blueprint of the system. This includes high-level architectural decisions, such as the choice of a programming paradigm (e.g., Object-Oriented, Procedural, Functional). This decision fundamentally shapes the software's structure, data models, and interfaces. The design phase produces a Software Design Document (SDD) that specifies how the system will be constructed to meet the requirements, and the paradigm is a foundational component of this specification.

B. A list of additional features to be added during revision: This is part of the Maintenance/Evolution phase, which occurs after the initial product is delivered.

C. A report of customer satisfaction: This is a post-deployment activity, typically gathered during the operational or maintenance phase.

D. A written description of the goals for the project: This is a primary deliverable of the Requirements Analysis phase, which precedes the Design phase.

1. Royce, W. W. (1970). Managing the Development of Large Software Systems. Proceedings of IEEE WESCON, 26(August), 1-9. (This foundational paper outlines the sequential phases, where architectural design follows requirements analysis).

2. Pressman, R. S., & Maxim, B. R. (2020). Software Engineering: A Practitioner's Approach (9th ed.). McGraw-Hill. (Chapter 4, "Process Models," describes the design phase of the Waterfall model as encompassing architectural and component-level design).

3. Sommerville, I. (2015). Software Engineering (10th ed.). Pearson. (Chapter 2, "Software Processes," details the Waterfall model, placing architectural design squarely within the "Software Design" phase, following requirements specification).