CAPM Practice: Determine how to gather requirements

Document analysis reviews existing artifacts — current system documentation, business policies, sample reports, form templates — to identify implicit requirements embedded in existing processes and understand the current state without relying solely on stakeholder memory.

**Why not B:** Analyzing documents for grammar and formatting errors is an editorial review activity, not document analysis for requirements gathering. Document analysis reviews existing business artifacts to extract requirements about current processes, not to assess writing quality.

**Why not C:** Reviewing competitor product documentation to identify features is competitive analysis or benchmarking, not document analysis. Document analysis focuses on the organization's own existing documents — policies, forms, manuals — to understand current processes and implicit requirements.

**Why not D:** Analyzing stakeholder feedback documents is a form of feedback processing, not the document analysis technique described here. Document analysis specifically reviews pre-existing organizational artifacts (procedure manuals, policies, forms) to extract requirements embedded in current processes.