Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
There’s something that’s been bothering me while attempting to do a use case diagram.
Both users and administrators can manage articles, both can manage categories, both can carry out crud operations on all of those BUT the administrator has control on every single item whereas a user is limited to a subset of these items.
Should/can a distinction be made in a use case diagram so this is clear?
From the sounds of thing the use cases are the same.
The devil could be contained in the detail of the activity and the scenarios associated with these use cases. These could define the role specific operations, or change in operations of the system in reaction to this role.
You could define them as separate use cases (but this doesn’t sound right as you say, it’s the same action for both, just with different limits to the action) or, make sure that authentication and the current user role is clearly defined as a predecessor to the above use cases. If you definitely want this information displayed in that diagram in particular.
This has some pretty good use case diagrams with users in different roles