Search code examples
umlprojectproject-managementuse-caseuse-case-diagram

Need help creating a Use Case Diagram

I have to create a Use Case Diagram for a project management software. What I need to take into account is which are the actors working with the software and which are the important activities.

That's how I made it:

enter image description here

Is it correct, did I choose the actors and activities properly and is there anything else that needs to be improved?

Solution

  • Some remarks :

    • the arrow of your extend is very probably on the wrong side, currently set a priority is extended by set assignments. The notation is extended UC <--<<extend>>-- extending UC, and it is extend rather than extends
    • project manager and project member cannot login, they already login to be a manager or a member, furthermore the login does not have enough added value to be an (interesting) use case, better to remove it
    • receive a message is not an UC or is wrongly named, a project member decides to read a message but the reception of the message is done by the mailbox subsystem without stimulus from the member. An other problem is its inclusion by the UC add project members, that one can include send message but not receive message nor read message in case you rename it
    • globally you have several UC using plural, like send messages, attach files etc, so it seems not possible to send one message etc, better to name them not using plural or may be placing s between parenthesis ?
    • except the problematic receive a message the included UCs are included by only one UC and never directly activated by an actor, for me these UCs are useless then and their behavior directly placed in the including UC. An UC is not just a name in an ellipsis, an UC must have an associated description
    • very probably a project manager can read message and can process project information, in that case project manager inherits project member
    • being on the right project member seems to be a secondary actor, this is a very common notation even not part of the standard, better to place it on the left, out of the fact very probably project manager inherits project member