1) The layout is confusing with lines crossing.  I try to avoid crossing lines, if I can.

2) What are the use cases with the separator lines doing?  You should only have a single use case in an ellipse.

Bob

1)  I will try to fix the line crossing issue.
2)  Use case with seperate line are Actually i got it from one tutorial, its called Extend.

Extends:
In some instances you want to describe a variation on behaviour in a more controlled form.  In such instances you can define extension points in the extended use case.  In the example below, search by name is said to extend search at the name extension point.  The extends link is more controlled than the generalization link in that functionality can only be added at the extension points

http://www.visualcase.com/tutorials/use-case-diagram.htm

Thanks

I understand the Extends usage, but that doesn't describe having two entries in a single use case with a line separating them.  It describes have separate use cases with <extends>, which you have included in the diagram.

Bob

So bob you saying that all I need to do is to remove the extra use case text from the use case with line seperator?

Actually the functional flow chart given in my diagram is designed by my senior and i had designed the use case based on those information can you please highlight me any mistakes you see in my use cases?

Thanks

so i guess in my diagram i just didnt put the extend correctly

actually I am a bit confused about extend and include

what i have understand is that
extend is when u need the current use case to perform some task in between the time of execution and that task becomes a extend use case

include use case i m not sure what is it

can you explain please
thanks

I tried to explain what extends means in the previous comment.  Are you saying that you don't understand the explanation?

Bob

yes

Did you look at the example on the web page that I referenced?

Bob