Use case for multiple login option

Question

I have a use case where user may log in via normal login, as well as social login such as Twitter, Google, Facebook. I draw the use case as below but not sure if it is correct.<

Answer 1

In general I tend to agree with Thomas Kilian to be careful with use cases for loggin in as they generally do not pass the boss test.

Will my boss be happy if I do [--insert use case--] 100 times?

But use cases are used in many different ways, and for many different systems. If your system is authentication service then I guess Log In might be an important use case.

Anyhow, the extend relations are pretty much wrong. There is also a heated debate in the community on what extends really means, and how to use it. I usually advice not to use extend at all. But if you want to keep them then you probably need to do it the other way around.

The extending use case inserts some specific functionality to the extended use case at a specific point in the execution of the extended use case (the extension point). The extended use case has no knowledge of the extending use case(s).

Extends is probably not what you need here.

I would probably not go into that much detail, and stick to the single Log in use case (if any). You could make alternate scenario's for facebook, twitter, google, etc...

But if you really need this much detail in your use case model then I would use generalization

As you can see there is one abstract use case Log in. The three other concrete use cases inherit from this use case.

In analyses there are no right or wrong answers. There are only better or worse answers, and it all depends heavily on the purpose of your model.