What are the main activities of Requirements Development (RD)?

What are the main activities of Requirements Development (RD)?

• A. Elicitation and analysis of requirements only.
• B. Validation and allocation of requirements to system components only.
• C. Elicitation, analysis, validation, and allocation of requirements to system components.
• D. Requirements development focuses on scheduling and budgeting.

Answer: (C)

The main activities of Requirements Development are elicitation, analysis, validation, and allocation of requirements to system components. Elicitation involves gathering needs and constraints from customers, users, and other stakeholders, ensuring you capture what the system must achieve. Analysis then refines these needs, resolves conflicts, removes ambiguity, and establishes priorities and feasibility. Validation checks with stakeholders to confirm that the documented requirements truly reflect their needs and can be verified or tested. Allocation maps each requirement to specific system components or subsystems, creating a traceable link from what’s required to how it will be implemented. Including all four activities is essential because each fills a different gap: without elicitation, important needs may be missed; without analysis, requirements can be inconsistent or impractical; without validation, you risk designing to the wrong goals; without allocation, you can’t trace requirements to design, implementation, or tests. Scheduling and budgeting, while important, belong to project planning rather than Requirements Development.

The main activities of Requirements Development are elicitation, analysis, validation, and allocation of requirements to system components.

Elicitation involves gathering needs and constraints from customers, users, and other stakeholders, ensuring you capture what the system must achieve. Analysis then refines these needs, resolves conflicts, removes ambiguity, and establishes priorities and feasibility. Validation checks with stakeholders to confirm that the documented requirements truly reflect their needs and can be verified or tested. Allocation maps each requirement to specific system components or subsystems, creating a traceable link from what’s required to how it will be implemented.

Including all four activities is essential because each fills a different gap: without elicitation, important needs may be missed; without analysis, requirements can be inconsistent or impractical; without validation, you risk designing to the wrong goals; without allocation, you can’t trace requirements to design, implementation, or tests. Scheduling and budgeting, while important, belong to project planning rather than Requirements Development.