I am drawing a diagram of use-case using ArgoUML, I have a scenario in which user can update status but after sign in to the application , in that sense i need to extends update status after sign in or make it a new separate usecase or generalize it.
Thank you
Login
is not a use case simply because it does not bring any value to the actor. It is a constraint. Just draw the association from user
to update status
(use verb substantive, not a concatenated identifier). You can put the login
association inside the use case.
Ask yourself for a use case: what value does it add to the user? The login
does not add any value. My value on SO for example is that I can ask question or that I can earn points be answering questions. So they are use cases "ask question" and "answer question".