CAPM Practice: Determine how to gather requirements

On large projects with hundreds of requirements, a requirements catalog (typically in a requirements management tool) provides the organizational infrastructure: each requirement has unique ID, attributes, status, links to source stakeholders, design elements, and test cases. This enables systematic management at scale.

**Why not A:** A "marketing catalog of available products" is a sales or product management tool, not a business analysis artifact. A requirements catalog is a structured repository that organizes and manages all requirements for a project or initiative, enabling traceability and status tracking throughout the project lifecycle.

**Why not B:** A "catalog of elicitation techniques" would be a reference tool or methodology guide, not a requirements catalog. While business analysts use various elicitation techniques, the requirements catalog is where the resulting requirements are documented, organized, and maintained—not where the techniques themselves are cataloged.

**Why not C:** "A collection of past projects' requirements" describes a historical repository or lessons learned archive, not an active requirements catalog. A requirements catalog is a living document for the current initiative that tracks each requirement's attributes, status, priority, and relationships, not a historical reference from previous projects.