CAPM Practice: Determine how to gather requirements

Swim lane diagrams show processes as parallel lanes, one per actor or system. They make handoffs and responsibilities explicit, revealing requirements for each participant and surfacing integration points and data exchange requirements.

**Why not A:** A diagram showing how data flows between different software systems describes a data flow diagram or system integration diagram, not a swim lane diagram. Swim lane diagrams focus on process flows divided by actor or role, showing who does what and where handoffs occur.

**Why not B:** A scheduling chart showing project phases divided by responsible department describes a responsibility assignment or project schedule view, not a swim lane diagram. Swim lane diagrams model business process flows with parallel lanes for different participants, not project scheduling timelines.

**Why not C:** A chart about dividing swimming laps during team-building activities is a literal interpretation with no connection to the BA technique. The "swim lane" metaphor refers to parallel lanes in a process diagram, each representing a different actor or system involved in the business process.