CAPM Practice: Demonstrate an understanding of business analysis (BA) roles and responsibilities

Different modeling notations suit different needs: BPMN for business processes, UML use cases for system behavior, ERDs for data structure, wire-frames for UI. BAs familiar with multiple notations select the most appropriate tool for each communication need — matching the model to the audience and purpose.

**Why not A:** A system for numbering requirements is a traceability or identification scheme, not a modeling notation. Modeling notation refers to standardized visual languages with defined symbols and rules for representing processes, data structures, and system interactions, which is fundamentally different from a numbering convention.

**Why not C:** Modeling notations are valuable for both business and technical requirements. BPMN process models, for example, are specifically designed to represent business processes and are heavily used with business stakeholders. Restricting notation to technical requirements ignores a significant portion of the BA's modeling toolkit.

**Why not D:** This answer confuses modeling notation with number formatting conventions across locales, which is an entirely unrelated concept. Modeling notation in the BA context refers to diagramming standards like UML, BPMN, and ERD that provide structured ways to visually communicate requirements and system designs.