Yes..i would really appreciate your 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
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.
"dependency" is not part of UML use case diagrams. Just include and extend.
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.
brought to you by enabling practitioners & organizations to achieve their goals using: