This use case describes the process a founder or co-founder will use to delete a group.
Note: This use case does not include removing players from a group, or removing a group manager. See those individual use cases for details.
The diagram shows the requirements and rules the use case is responsible for (via the <<requirement>> stereotype).
The system has deleted the group.
Extended Use Cases
Requirements and rules realized
RQ30 Only founders can delete groups
The system shall prevent any player other than the founder or co-founder of a namespace, from deleting a group within that namespace.
RQ29 Track changes to groups
The system shall store and track all changes to a group's name, description and membership policy.
RQ26 Notify founder changes
The system shall notify a namespace founder of any changes according to rules: BR36
- BR36 New, re-named or deleted groups
The system shall notify the namespace founder when a new group has been created, an existing group changed, or a group deleted from within the namespace.
Flow of events
The flow of events describes the main actor actions and system responses in the execution of the use case.
|Condition:||Actor is not a founder or co-founder of any namespace|
|Message Text:||You cannot make changes to a group because you are not a founder/co-founder.|
|Condition:||Successfully deleted group.|
|Message Text:||Successfully deleted group <group name>|