This use case describes the process of editing a group in the ACME system.
- Administrator
- User
- The user is logged into the system.
- The Admin displays a list of groups
- The Admin selects one group from the list, then selects an option to edit that group
- The system displays the following required group information in read/write mode:
- The group name
- A list of the group functional areas and their corresponding access levels
- The Admin can change the group name and edit the access level of the functional areas
- The Admin saves the changes
- If the group name is invalid
- The system tells the Admin the group name is invalid and displays proper format options
- When the Admin disposes the message
- The system leaves the contents of the group name data entry field as-is
- The system places focus in the group name field
- Else, the system saves the changes
- The group name may be different
- Any users in that group stay in that group, even though the group has a different name
- Functional areas for the group may have different access levels
- This will not affect users currently logged into the system
- This will affect users the next time they log into the system
- The User displays a list of groups
- The User selects one group from the list
- The system makes a View option available to the user
- When the user selects the View option the system displays the following required group information in read-only mode:
- The group name
- A list of the group functional areas and their corresponding access levels
- There should be no data changes to any group
- From an information standpoint, the user who viewed this information will know the access levels of any groups that they viewed
None.
None.
|
|