more variants using intermediate elements of generalisation.keep only the association of the normal user to the general use case, and use a constraint on the deletion use case, to make clear that it requires the user to be superuser (this would be my preferred one, as it would allow also to get rid of the (too?) detailed uc):.Associate the normal user to the three specializations and the admin to the deletion only. keep the general use case without actors.Multiple modeling standards to ensure adherence Archimate, UML, SysML, boxes and arrows, C4, and more. Build a library of use case diagrams ready to present to stakeholders. If you would just have the CRUD cases inheriting from the more general Manage users, an Administrator could, by way of use case specialisation, also realize the more sensitive Delete user. DESIGN & ANALYZE Easiest Way to Create Use Case Diagrams Use predefined templates to start modeling use cases. The right way to address this issue - if this level of detail is really desired - is to use generalisation on the use case side as well. You‘ll find more arguments in this other answer. The «extend» approach is not suitable because it requires the use-case Manage users to add value on its own without any of the extensions.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |