Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Requirements  Use Case - Direction of the Include and Extend arrows
Previous Previous
 
Next Next
New Post 1/12/2012 3:12 PM
User is offline Engle
30 posts
9th Level Poster


Use Case - Direction of the Include and Extend arrows 

 Would like to understand the direction of the arrows for Include and Extend UC in a UC diagram

1. Seems to me that when a Base UC INCLUDEs a UC, then the connector arrow s/b TOWARDs the Base UC. 

The included UC is being brought in (included) into the Base UC. 

2. Conversely, when a Base UC EXTENDs to another UC, then the connector arrow s/b AWAY FROM the Base UC

The Base UC is extending or expanding to another UC

 

So, why are the arrows pointing in the opposite direction from what a reasonable reader would expect  ?

Thoughts or explanations ?

Thanks, 

 

 
New Post 1/12/2012 5:48 PM
User is offline Kimbo
453 posts
5th Level Poster


Re: Use Case - Direction of the Include and Extend arrows 

Hi  Engle,

Now you could say that base UC includes other use case, so it reads left to right. And other use case is extending the one it points to - the base UC. But really it doesn't matter that much does it? Just follow the convention. As long as everyone does it the same way there's no issue

Kimbo

 
New Post 1/12/2012 6:22 PM
User is offline Engle
30 posts
9th Level Poster


Re: Use Case - Direction of the Include and Extend arrows 

 Kimbo wrote

Hi  Engle,

Now you could say that base UC includes other use case, so it reads left to right. And other use case is extending the one it points to - the base UC. But really it doesn't matter that much does it? Just follow the convention. As long as everyone does it the same way there's no issue

Kimbo

Hi Kimbo, just thought I'd throw my thinking out there, not necessarily because I'd like to challenge the status quo, but in an attempt to clarify what I believe is a confusing issue between the ' include ' and ' extend ' features. 

In the English lexicon, when you include something, you bring it into your space, your domain - as in I'm including you in my team. <---

When you extend something, you reach out - as in I'm extending my hand out to you or extending our business to foreign markets  --->

Those teeny-weeny little arrows pointing in the wrong direction are IMO a contributing cause of the confusion and I'd imagine the creators of the UC, perhaps did not put as much thinking into this as they should have. 

Cheers !

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  Use Case - Direction of the Include and Extend arrows

Community Blog - Latest Posts

Is Agile a reason to avoid documentation? I bet this question shows up again and again while working with product requirements. On one side, we have got long specifications, complicated diagrams, mystical technical design, too many prototypes and pretty obvious for engineers user guides (do we really need so much?). On the other side, can we actual...
The cloud-native application development has helped enterprises all around the globe reduce time-to-market, enhance performance, and develop agility and flexibility. Several enterprises are achieving these results by migrating their systems or traditional monolithic applications to the cloud. But to gain from the real benefits of cloud technology, ...
So you’ve found the perfect time and place to study and you’re ready to finally get some work done. You’ve pulled out your laptop, your textbook, and your notes, and four different highlighters. After five minutes of reading your textbook, you start zoning out and thinking about puppies. Then, you go on Tumblr and look at cut...

 



Upcoming Live Webinars




 

Copyright 2006-2021 by Modern Analyst Media LLC