CAPM Practice: Determine how to gather requirements

Natural language requirements are easy to write and read but notoriously ambiguous. Words like 'fast,' 'user-friendly,' 'occasionally,' and 'appropriate' mean different things to different people. BAs supplement prose with formal models, examples, and acceptance criteria to reduce ambiguity.

**Why not A:** Using nature metaphors to make technical requirements understandable describes a communication technique, not natural language specification. Natural language specification means writing requirements in plain prose, which is the most common and accessible form of requirements documentation regardless of metaphor usage.

**Why not B:** Specifying requirements in multiple natural languages for global teams describes localization or translation, not the concept of natural language specification. The term refers to using ordinary prose rather than formal notation, not to multilingual documentation practices.

**Why not C:** Requirements specified without any formatting or structure describes poorly organized documentation, not natural language specification. Natural language requirements can and should be well-structured with numbering, headings, and consistent formatting. The distinction is between prose and formal notation, not between structured and unstructured writing.