Difference between revisions of "Remove User from Group"
(Move to spec)
|Line 56:||Line 56:|
Latest revision as of 17:12, 5 December 2016
This use case describes the process a group manager will use to remove a player from a group they manage.
The diagram shows the requirements and rules the use case is responsible for (via the <<requirement>> stereotype).
The system has removed the player from a group.
Included Use Cases
Requirements and rules realized
RQ7 Group managers can view the list of members
The system shall enable group managers to view the list of members in any group they manage.
- BR33 Managers cannot remove founders
The system shall prevent a group manager from removing a player from a group where the player is also the groups founder or co-founder.
RQ19 Notify players of changes in membership
The system shall notify a player if they have been added to, or removed from, any group.
- BR28 Player notification format
The system shall use a forum private message, email message, and a message displayed on the 'my groups' page to alert players of changes to their membership.
RQ20 Track changes to group memberships
The system shall store and track the details of changes in membership of each group, according to rules: BR26
- BR26 Record details
The system shall store the date, player, manager and group for each change in membership.
- BR34 Provide reason for removal
The system shall require a manager to provide a reason for removing a player from a group.
Flow of events
The flow of events describes the main actor actions and system responses in the execution of the use case.
|Condition:||Successfully removed player from group|
|Message Text:||Player <player name> has been removed from Group <group name>.|