Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Requirements  Use Case Scenarios: Exception or another Alternate Flow on an Alternate Flow.
Previous Previous
 
Next Next
New Post 5/12/2015 2:44 AM
Unresolved
User is offline Thomas W.
1 posts
No Ranking


Use Case Scenarios: Exception or another Alternate Flow on an Alternate Flow. 

I'm currently struggling with how to handle an alternate (or exception) flow on an alternate flow in Use Cases.

I've met several business-specific examples in which I needed an alternate flow in an other alternate flow,
or an exception in an alternate flow. We use Enterprise Architect, in which it isn't possible to define an alternate flow within an alternate flow, or an exception flow in an alternate flow. 

I tried an other tool I stumbled upon while searching google (caseComplete) but it had the same problem. That's why I don't know if this is a correct way of working, and I'm searching for another way to correctly define this kind of nested alternate flows.

I tried to make the next example a bit more generic to spare you the business-details, but you can assume that there are more situations in which I'd need an alternate flow within another alternate flow.

7. system shows list of default options.
8. user selects default option.
9. system adds default option to order.
10. system places order.

 

8a. Alternate: option not in list.


8a.1 user enters option not in list.
8a.2 system asks to add option.
8a.3 user confirms addition of new option.
(back to 10)

8a.3a Alternate: user doesn't want to add option. 

8a.3a.1 user reject option addition.
8a.3a.2 system adds not-default option to order.
(back to 10)

 

So two questions:

1)      Is this a correct way of describing Use Case Scenarios?

2)      If this is a correct way of describing this kind of nested alternate flows, how could I solve this in Enterprise Architect?

I could switch the “basic path” and the “alternate path”, so that the alternate flow is a first level alternate flow, but in that case, my basic path wouldn’t be the “basic path” anymore, and I would consider this a dirty solution.

 

7. system shows list of default options.
8. user enters option not in list.

9. system asks to add option
10. user confirms addition of new option.

11. system places order.

 

8a. Alternate: option already exists

8a.1 user selects default option.

8a.2 system adds default option to order.

(back to 11).

 

10a. Alternate: user doesn’t want to add option.

 

10a.1 user rejects option addition.

10a.2. system adds not-default option to order.

(back to 11).

 
New Post 5/15/2015 10:35 AM
User is offline NitWitNick
259 posts
5th Level Poster


Re: Use Case Scenarios: Exception or another Alternate Flow on an Alternate Flow. 
For what it is worth, I don't use Use Cases to develop a system ... I use Visio to create WorkFlow, Activity diagrams and UML diagrams ... showing the end-to-end business process. For many people, they are easier to understand, their mind follows the arrows to a decision point and then more arrows to what the next step is ... from start to finish.

Once everything is figured out ... then I can develop a Use Case if needed.



Here are some things to read:

http://www.modernanalyst.com/Community/Forums/tabid/76/forumid/17/threadid/6980/scope/posts/Default.aspx

http://www.writingusecases.com/wordpress/index.php/archive/tips-for-bas-alternative-flows-of-events/

http://www.lohmy.de/2013/03/06/writing-use-cases-exception-or-alternate-flow/

http://www.agilemodeling.com/essays/umlDiagrams.htm
 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  Use Case Scenarios: Exception or another Alternate Flow on an Alternate Flow.




Latest Articles

Domain Expertise and the Business Analyst: How Vital Is It?
Sep 15, 2019
2 Comments
The question of how essential domain expertise is to a business analyst is a recurring debate in the BA community. One school of thought maintains tha...
Copyright 2006-2019 by Modern Analyst Media LLC