Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Requirements  Use Case feedback
Previous Previous
 
Next Next
New Post 7/23/2012 7:53 AM
User is offline M.Islam
18 posts
9th Level Poster


Re: Use Case feedback 

 Yes..i would really appreciate your feedback.

 
New Post 7/24/2012 1:57 AM
User is offline Kimbo
454 posts
5th Level Poster


Re: Use Case feedback 

Check out this forum discussion for an explanation of extend:

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

I use <include> basically to avoid defining the same flow in more than one use case. Idea is to pull it out into a separate use case that you include in all the places its needed. An example might be a Find Customer use case that is used in use cases Enter Sales Order and Sales Order Report and Change Sales Order.

Now having said that, I do still use Include in pretty much all projects. But I haven't used extension points very much for years. I don't think they add very much and they can really clutter up your use case diagrams. Up to you of course.

Kimbo

 
New Post 7/24/2012 9:19 AM
User is offline M.Islam
18 posts
9th Level Poster


Re: Use Case feedback 

 I wanted to know Use case "include" and "extend" are they same as Use Case "dependency". Several places I have seen that they have indicated Use Case "depedency" can be 2 types which is "include" and "extend". Some other places Use Case "dependency" , "include" and "extend" they are all different and being utilized in the same use case. I am confused if "include"and "extend" are part of use case "dependency" or it is totally different? thanks for your response and feedback.

 
New Post 7/25/2012 1:56 AM
User is offline Kimbo
454 posts
5th Level Poster


Re: Use Case feedback 

 "dependency" is not part of UML use case diagrams. Just include and extend. 

 
New Post 7/25/2012 7:17 AM
User is offline M.Islam
18 posts
9th Level Poster


Re: Use Case feedback 

 ok some places on the internet I have seen they have showed all 3 the Use Case diagram. In our work environment we prefer writing detail use case in narrative. what about when you are writing in detail narrative use case? Use Case dependency is a part of narrative description then or do I need do describe it then? Second question how do you show a Use Case diagram when there is two system interacting with several Business users. Usually in system boundary you write one system name? how would you approach it? would you draw few diagrams to represent each different system? Thanks again for your valuable feedback.

 

 

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  Use Case feedback

Community Blog - Latest Posts

Today I had the pleasure of chatting to Jignesh Jamnadas, Chief Operations Officer at Mosaic, about his Blueprints for Success. As a Senior Finance and Operations Executive, Jigs (as he is known to many) has a holistic understanding of all facets of business and a flair for managing both people and processes. Having worked with Jigs, I was struc...
I recently had the pleasure of chatting with Wolfgang Goebl, a visionary in the field of business architecture and enterprise design. His unique approach, which he refers to as "architectural thinking," and his work with the EDGY framework, offer valuable insights into the future of organizational structure and design. This tool covers th...
Our next speaker in our Blueprints for Success series is none other than Roger Burlton, a prominent leader in business architecture. As founder of Process Renewal Group, Roger has spent over three decades helping businesses worldwide translate strategy into execution. “Intention is everything.” – Roger Burlton Known for his ...

 






 

Copyright 2006-2024 by Modern Analyst Media LLC