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

Ashish Adike
Ashish Adike
As a Business Analyst, very often we get into a situation where the Project requires multiple IT Products to be evaluated before implementation and might seek Business Analyst’s recommendation for the same. With the ever-growing range of Products in the market and the marketing promotions associated with some of the products, it’s very ...
0 Responses
m_anst
m_anst
What Does Success Look Like? I challenge Business Analysts to view requestors’ requirements as an opportunity to define success. Too often, teams fall into a trap focused on requestors’ prescriptive requirements that are meant to serve as roadmaps for developers and testers. When you limit your view of requirements to this prescripti...
0 Responses
Mariya Kotsupalova
Mariya Kotsupalova
They say the best criteria of Business Analyst’s success are a happy customer (business) and a happy engineering team. But what does it mean? How can we break down happiness and measure it? These are precisely the questions my 8 BAs team and I tried to answer this year. The result was a surprisingly efficient pair of surveys we developed and ...
0 Responses






Copyright 2006-2020 by Modern Analyst Media LLC