How to Represent Constraints for Role-Based Access Control in a Task Management Use Case Diagram?
I'm working on designing a use case diagram for a task management application, and I'm seeking guidance on representing role-based access control (RBAC) effectively.
I've created a preliminary use case diagram that includes actors such as "Manager" and "Standard User," along with various use cases like "Manage Projects," "Manage Tasks," and so on. However, I'm struggling to depict the relationship where standard users are restricted to projects and tasks assigned by managers.
I've created two use cases 'Manage Assigned Project' and 'Manage Assigned Tasks'. Tasks are dependent on a project. The manager is linked to the assigned project via association.
How to represent this constraint effectively in the use case diagram?
If deemed useful, here are the requirements I need to cover:
- The application should support CRUD operations (Create, Read, Update, Delete) on projects and tasks.
- Tasks can only be created if a project already exists.
- Managers should have access to all features across all projects and tasks.
- Standard users are limited to projects and tasks assigned by managers.
- Standard users can only read and edit tasks.
- Managers should be able to assign tasks and projects to standard users.
The manager and the project manager both aim to manage projects and tasks. It's their shared goal.
It's just that their role and contributions in regard of this goal changes : while the manager has a greater responsibility, and probably has to identify, specify and assign tasks, the standard user contributes to the management of these items, of course limited to the assignements. This pleads to make manager a primary actor of manage project and manage task, and make standard user a supporting actor to the same use-cases.
Whether you follow or not the advice, you could show the contraint in the diagram with a text between curly brackets { only for projects/tasks assigned to the user }. This would however clutter the diagram with too many details. A better alternative is to describe the constraint in the use-case description/ narrative.
- How do I create a unique key that is case sensitive?
- Difference between declarations of trait bounds
- How to truncate a foreign key constrained table?
- How to list all constraints of a table in PostgreSQL?
- Read/write lock on range using EXCLUDE constraint
- what's the problem in defining multiple constraints?
- Postgres: Add constraint if it doesn't already exist
- Setting default value for DATE type column to current date without time part?
- C# - How to instantiate an object with constraint from existing interface method without constraint
- Make GHC deduce one type family constraint from another
- Is it possible to have a "deferred check constraint" in Oracle?
- Stuck at (erno: 150 "Foreign key constraint is incorrectly formed,")
- How to ignore the safe area when using keyboardLayoutGuide?
- Pulp constraints when problem is infeasible
- How to add a monotonic constraint in a GAM model
- LazyColumn and Constraint in JetPack Compose
- Optapy hard constraint is not respected in a VRP
- Annotations from javax.validation.constraints not working
- Constraint to randomize such a way that consecutive 2 bits are set to 1, other bits are 0 for 16-bit variable
- Postgres caseinsensitive unique key constraint: What is the fast option?
- Table constraint for range and null values
- What's the use of constraint in Gradle dependencies resolution?
- Display names of all constraints for a table in Oracle SQL
- constraint vertical slider on top anchor of another object
- How to replace ref-qualifiers of member functions with concept?
- constraint rotated vertical uislider
- Autolayout interaction of Storyboard elements with UI elements created programmatically using Objective-C and Swift
- Validate symfony 4 formfield filetype with mapped false and multiple true
- SystemVerilog constraint for mapping between two 2D arrays
- Random constraints on array of structure elements