CAPM Practice: Determine how to gather requirements

Implied requirements are those stakeholders assume are so obvious that they don't mention them (e.g., 'the system must log users out after inactivity'). BAs must proactively identify implied requirements through domain knowledge and careful questioning.

**Why not A:** The distinction is not about written versus spoken format. Both stated and implied requirements can be communicated verbally or in writing. The key difference is whether stakeholders explicitly express the requirement versus assuming it is so obvious it goes without saying.

**Why not B:** The distinction is not based on the source (business vs. technical). Both business and technical stakeholders can have stated and implied requirements. Implied requirements come from assumptions any stakeholder considers obvious, regardless of their role.

**Why not C:** Implied requirements are not optional enhancements. They are often critical expectations that stakeholders assume are self-evident (like security timeouts or data backup). Missing implied requirements can cause significant user dissatisfaction precisely because they are seen as fundamental.