Study CAPM User Stories, Use Cases, and Visual Models: key concepts, common traps, and exam decision cues.
This chapter focuses on how requirements are expressed once the analyst has started discovering what matters. CAPM usually tests whether you can choose the right format for the communication problem instead of forcing every need into the same style of documentation.
The exam usually does not reward a generic belief that one requirement format is always best. It rewards whether you can decide what kind of expression will clarify the requirement fastest and most accurately: a lightweight story, a richer behavior model, or a visual artifact that makes hidden assumptions visible.
Use these sections in order. Start with user stories and how they support lightweight adaptive conversation, then move into use cases and process flows for richer behavioral logic, and finish with prototypes, wireframes, and visual modeling when stakeholders need something concrete to react to.