Kimbo I read all your opinion and views and respect them as well. This is one of the reason i keep coming here and posting. I also wanted to ask one more thing for future refernces. I have found out one of my IT manager have told me as you can use an alternate path or an exception path and make a seperate scenario or a seperate use case. What is the advantage and disadvantage of doing so in a project ?

Kimbo:

You are right:  Alot depends upon ones viewpoint.    But, that said, one would want their use case, or user story, or data flow diagram to be loosely coupled and highly cohesive.  Otherwise, especially for more complex projects, things would get just too complicated.

Tony

 thanks for all the feedback.

I want your feedback about one more concept of use case.

Use case dependencies can be broken down to include and extend?? or use case dependencies is a toally different area than include and extend?? can you explain or maybe give me some examples if they are different (dependencies vs include/extend)??

thank you.