Why is requirements gathering part of the design process? It provides:

• A. An explanation of what the system should 'be' or should 'do'
• B. Documentation of 'needs' to communicate between everyone involved in system development
• C. A set of goals that define objectives for design
• D. All of the above

Answer: (D)

Requirements gathering in the design process sets up a shared understanding of what the system must achieve. It explains what the system should be or do by capturing both functional needs (what features and behaviors are required) and nonfunctional requirements (how well it should perform, security, usability, reliability, etc.). It also documents needs to communicate among everyone involved in system development, ensuring stakeholders, analysts, designers, and developers stay aligned and reducing misinterpretation. Additionally, it defines objectives for design by establishing clear goals that guide decision-making and how success will be measured.

Because it covers what the system should be, communicates needs across the team, and sets design objectives, it provides the most complete basis for the rest of the design process.