CODEWITHSUNDEEP
web-applicationsumluse-case
JoeRaid
JoeRaid

Reputation: 107

UML-Modeling Different User Classes (Actors) in Use Case Diagrams

I'm building a web application with CRUD/social-network-like functionalities. The problem is that users won't be getting the same privileges when it comes to accessing certain pages nor in terms of services and this apparently should not figure in a use case diagram as an actor needs to be treated independently from the system. A commenter suggested using constraints to check if a user has privilege or not but the problem is that most of time the application won't even do a check, rather will load a different version of the page or will simply not display a command for a certain function. This is my initial take on the problem : 1, 2, 3, 4.

Upvotes: 0

Views: 174

Answers (1)

qwerty_so
qwerty_so

Reputation: 36313

Using Generalization is a way to approach this. You can further add constraints as shown in my example here.

Please note that Login is no use case. A use case is about added value, not about functions. If y login is required you attach a constraint to where it applies (can be an actor or a specific use case; if all except one needs login you can add a general requirement and make a "negative" constraint like { no login required }). As always I recommend to read Bittner/Spence about synthesizing use cases.

Upvotes: 1

Related Questions