Comprehensive and Detailed Explanation From Exact Extract:
The Waterfall methodology follows a linear sequence: requirements analysis, design, implementation, testing, and maintenance. According to foundational programming principles (e.g., Certiport Scripting and Programming Foundations Study Guide), the design phase involves creating detailed technical specifications, including outlining functions to be written.
Waterfall Phases Overview:
Analysis: Defines requirements (e.g., “the system must track books, loans, and returns”).
Design: Creates technical plans, including system architecture and function specifications (e.g., addBook(), checkOutBook()).
Implementation: Writes the code for the specified functions.
Testing: Verifies the system meets requirements.
Option A: "Testing." This is incorrect. Testing verifies the implemented functions, not their planning.
Option B: "Analysis." This is incorrect. Analysis identifies high-level requirements (e.g., system features), not specific functions.
Option C: "Design." This is correct. In the design phase, the programmer outlines the functions needed (e.g., function names, parameters, and purposes) to support the inventory system, creating a blueprint for implementation.
Option D: "Implementation." This is incorrect. Implementation involves coding the functions, which occurs after they are outlined in the design phase.
Certiport Scripting and Programming Foundations Study Guide (Section on Waterfall Methodology).
Pressman, R.S., Software Engineering: A Practitioner’s Approach, 8th Edition (Chapter 2: Waterfall Model).
Sommerville, I., Software Engineering, 10th Edition (Chapter 2: Waterfall Design).
