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
96 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

Gen1us2k
Gen1us2k
Most of the IT projects imply constant cooperation between the team members and customers. Although it might be often overlooked, the role and the importance of the client within the project is very crucial. Thus, it is in your interest to build a strong relationship based on trust. However, gaining trust on a single occasion is not a dealmaker &md...
0 Responses
emorphistechno
emorphistechno
Introduction In today's world, most enterprises work aggressively to achieve a higher level of business growth, which is made possible by leveraging one of the best automation technologies. One such technology is Robotic Process Automation (RPA) that plays a vital role in streamlining the customer experience in the most profitable manner.&nb...
0 Responses
Nick Stowers
Nick Stowers
Introduction   When I was introduced to scrum, the burndown chart was a tool that was highly emphasised however I feel the purpose has changed from it being a tool to predict (to a certain level) timescales for delivery to a tool that measures a team’s productivity…..in other words, the focus is on the number of points clear...
0 Responses






Latest Articles

From an Intermediate to a Strategic Senior Business Analyst
Aug 09, 2020
0 Comments
It is strange how something that is supposed to be simple is actually so complex.  Something that is supposed to be a matter of linear career pro...
Copyright 2006-2020 by Modern Analyst Media LLC