Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Structured Anal...  UML: Use Case diagram for Create Invoice
Previous Previous
 
Next Next
New Post 11/18/2019 8:44 AM
Unresolved
User is offline David Jacobs
1 posts
No Ranking


UML: Use Case diagram for Create Invoice 

Hello all
I've just joined Modern Analyst and would like to ask for some advice.
I want to draw a use case diagram for Create Invoice (this is an example I am working on for my own edification).
I have two use case ovals, Create Invoice (Header) and Create Invoice Line.
This may not be the best way to approach it but it seems to me to be a two-way extend relationship.
The user can create an invoice header and optionally create lines (or add lines later).
And the user can create invoice lines, sometimes having to create a header first where one does not exist.
In UML would this be best as Create Invoice without the detail or drawn as how?
I believe a two-way extend is not a recommended construct for use case diagrams.
Many thanks in advance for any thoughts.
David Jacobs, business analyst

 

 

 
New Post 12/11/2019 11:42 PM
User is offline Stewart F
110 posts
7th Level Poster


Re: UML: Use Case diagram for Create Invoice 

Hi David, 

To answer your question directly - I don't thin it really matters which way you create your diagram. 

You are quite right that there needs to be a step to create an Invoice 'shell' or 'header' as you call it. So I agree with that approach, especially based the fact that everything else that is created needs to go somewhere. 

So common sense would say it should be a two-way extend. However, you are also right that usually UML steers you away from having such a approach. The only thing I can suggest is to keep it at one - 'create the invoice shell' and then build on top of that. 

Failing that, rules are to be broken !!

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Structured Anal...  UML: Use Case diagram for Create Invoice

Community Blog - Latest Posts

There are big differences between data exploration versus data presentation. And you need to be aware of these differences as you're creating data stories and data presentations. Let’s start by defining our terms: Data exploration means the deep-dive analysis of data in search of new insights. Data presentation means...
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, ...

 






 

Copyright 2006-2022 by Modern Analyst Media LLC