Ive been asked to document a day in the life of each class of user for a new application. Does anyone have suggestions about tools to document this? my PM is asking for pictures...
Submitted by smojumder on Tue, 2009-12-15 11:34. *
I did this task for a number of projects where i created security diagram for each role and hope the below will help you. Please note that security model is slightly different from use case model though i actually created use case diagram for one role at a time.
Security model - create one model for each system user role. Add the role and all the system use cases (one oval for each use case as usual) that the role will execute (includes both read-write and read-only). From the name of the use case, it should be clear whether the user has read-only access or read-write access. Ex: "withdraw cash" use case is read-write whereas "View transaction history" is read-only. Do not use any related or linked use case (avoid showing include, extend, inheritence relations).
Use case model - add the primary use case in the diagram and arrow link to all the user roles that will initiate/execute the use case. Show all the linked use cases by showing include/extend/inheritence relations.
Tool - use any CASE tool that you are using to model your project use cases (rose, enterprise architect, visio, modeler, ...).
Security model?
I did this task for a number of projects where i created security diagram for each role and hope the below will help you. Please note that security model is slightly different from use case model though i actually created use case diagram for one role at a time.
Security model - create one model for each system user role. Add the role and all the system use cases (one oval for each use case as usual) that the role will execute (includes both read-write and read-only). From the name of the use case, it should be clear whether the user has read-only access or read-write access. Ex: "withdraw cash" use case is read-write whereas "View transaction history" is read-only. Do not use any related or linked use case (avoid showing include, extend, inheritence relations).
Use case model - add the primary use case in the diagram and arrow link to all the user roles that will initiate/execute the use case. Show all the linked use cases by showing include/extend/inheritence relations.
Tool - use any CASE tool that you are using to model your project use cases (rose, enterprise architect, visio, modeler, ...).
Thanks, Sulata