CAPM Practice: Determine how to gather requirements

Interface analysis examines system-to-system, human-to-system, and organization-to-organization interactions to surface interface requirements — data formats, timing constraints, communication protocols — that are often missed when focusing only on core functionality.

**Why not B:** A review of the project manager's communication interfaces describes stakeholder communication management, not interface analysis as a requirements technique. Interface analysis in the BA context specifically examines the boundaries where a system connects to or exchanges data with other systems, users, or hardware devices.

**Why not C:** While API documentation review might be one small input to interface analysis, the technique is much broader. Interface analysis encompasses all interaction points including human-system interfaces, hardware interfaces, system-to-system integrations, and data exchanges, not just third-party API documentation.

**Why not D:** Analyzing GUI design for usability is user experience or usability analysis, which is a distinct activity from interface analysis. Interface analysis focuses on identifying and specifying the requirements at system boundaries and interaction points, whereas usability analysis evaluates how intuitive and effective a specific user interface design is.