I have the following scenario:
When a customer registers he needs to enter his details, choose a subscription period and take a subscription - so TakeSubscription is included in Register.
However, a customer is allowed to take a subscription without registering, in which case he will be asked to register as part of taking the subscription, so Register becomes an extension point of TakeSubscription.
Can I have both <<include>> and <<extend>> between the same two use cases like in the attached diagram or is it wrong? Is so, how should I model it so that the model is valid?
Pinned topic Extend and Include between the use cases?
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-11-14T20:06:05Z at 2012-11-14T20:06:05Z by SystemAdmin
Re: Extend and Include between the use cases?2012-11-14T07:27:41ZThis is the accepted answer. This is the accepted answer.It seems to me, you just have to be a registered subscriber in the first place so just make your take subscription the base use case and extend the registration as shown in my diagram. There is a diagram I did along with a basic flow of events. I think having a use case perform in this manner although is feasible may not be robust. By that I mean, the separation of concern is a little muddy when you do this which makes this design to dependent. Take a look at what i did and let me know what you think.
Re: Extend and Include between the use cases?2012-11-14T20:06:05ZThis is the accepted answer. This is the accepted answer.
- SystemAdmin 110000D4XK