CAPM Practice: Determine how to gather requirements

Requirements categorization ensures comprehensive coverage — systematic review of each category confirms the BA has addressed all requirement types. It also enables stakeholder communication (business users see functional requirements; architects see non-functional requirements) and traceability by category.

**Why not A:** Requirements categorization serves a much broader purpose than regulatory compliance alone. While compliance requirements are one category, the technique is used to organize all types of requirements—functional, non-functional, business, stakeholder, and transition—to improve traceability, prioritization, and overall requirements management.

**Why not B:** Categorizing requirements by the stakeholder who requested them is not a standard or effective categorization approach. This method would create overlapping and inconsistent groupings, since multiple stakeholders may request similar requirements. Proper categorization uses meaningful dimensions such as type, priority, or business domain.

**Why not D:** Organizing requirements alphabetically provides no analytical or management value. Alphabetical ordering is a simple sorting mechanism that does not help teams understand relationships between requirements, prioritize work, or ensure complete coverage across functional and non-functional categories.