The "123" in your methodology isn't about using every tool on every project. It’s about . A seasoned Business Analyst knows that a software migration requires different tools (like Data Mapping and API Analysis) than a departmental restructure (which might require Organizational Modelling and RACI Matrices).
Using Use Case Diagrams, Activity Diagrams, and State Diagrams to describe system behavior.
Group sessions to generate creative solutions. The "123" in your methodology isn't about using
Not all requirements are created equal. You need a way to sort the "must-haves" from the "nice-to-haves."
The gold standard for mapping out business workflows. Using Use Case Diagrams, Activity Diagrams, and State
While "123" represents the vast breadth of the profession, successful analysis usually boils down to mastering specific categories of tools. 1. Strategic Analysis Techniques (The "Big Picture")
Business Analysis Techniques: 123 Essential Tools for Success You need a way to sort the "must-haves"
Reviewing existing system documentation, business plans, and policy manuals.
Targeted interviews with specific user groups to gauge reactions.