Use Case Paths (Flow of Events) to Capture, Organize, and Communicate Functional Features


Learn how stakeholders can capture, organize, and communicate Functional Business Requirements or Functional Features , “Lean / Agile Business Analysis: Writing BUSINESS Use Cases” (https://bit.ly/2Fmr4pw). See you in lesson 1! #UseCases #FunctionalFeatures #Business Analysis

Learn how stakeholders can capture, organize, and communicate Functional Business Requirements or Functional Features for a digital solution.
Paths are the meat of the Use Case. Use Cases represent interactions between Actors and Applications that deliver value to the initiator. The sequence of those interactions are defined using paths.

There are three different types of paths: Main (aka Standard, Basic), Alternate, and Exception. By distinguishing three distinct path types, your Lean Use Case gains tremendous power in support of effective communication and collaborative development of the solution.

Separating the Standard (Main, Basic, Happy) Path from Alternate and Exception Paths keeps the Use Case simple and straightforward which is aligned with Lean Principles. Keeping Alternate and Exception Paths separate from the Standard Path facilitates modifications to the Use Case as future needs are uncovered.

Although there are no fixed rules for documenting a Use Case, the techniques in this video are best practices to make sure your Use Cases are as good as they can be and will fit into a lean and agile software development environment.

Browse our online courses and books (https://businessanalysisexperts.com/) to get your Business Analyst career to the next level.

You May Also Like