Should different actors in a Use Case Diagram share the same Login Use Case?

Question

I currently have a Use Case Diagram that is similar to the above one:

In my final application I will probably share the same Login form for both Employees and Employers. Should I reflect that in this Use Case Diagram, having both Actors using the same Login Use Case? If so, how can I then represent what each one of them can do after doing the Login?

Answer 1

Why don't you make both Employer and Employee specialise from an abstract User, and make that User actor use the Login use case?

Then Employer and Employee would use their specific use cases only.

Answer 2

@CesarGon's is a good solution. Another alternative - not necessarily better, just different - is to have both Employee & Employer Use Cases <<include>> the login UC.

Which you use depends on style & preference. The Abstract User approach can look cleaner and is more declarative (you should specify login as a pre-condition on other UCs). The <<includes>> approach perhaps fits an imperative/process modelling mindset better since each UC will explicitly show the call to login as the first step.