This use case describes the process a founder or co-founder will use to create a new group.
The diagram shows the requirements and rules the use case is responsible for (via the <<requirement>> stereotype).
The namespace for the group must have been registered previously.
The system has created the new group.
Requirements and rules realized
RQ8 Groups have a membership policy
A groups membership policy determines whether a player can join the group or not.
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 re-named, or a group deleted from within the namespace.
RQ27 Group names unique
The system shall require a group name to be unique within its namespace.
- BR37 Group names are case insensitive
When determining whether a group name is unique, the system shall ignore the case of the characters, so that for example, COP and cop shall be treated as identical.
RQ23 Founders and co-founders assign group managers
The system shall prevent any player other than the namespace founder or co-founder, from creating groups or assigning group managers within that 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 create a new group because you have not registered any namespaces.|
|Condition:||Group name empty or existing, group description missing, or no membership policy selected.|
|Message Text:||Cannot create group - the name is empty or identical to an existing name, the description is missing or no membership policy selected.|
|Condition:||Successfully created new group.|
|Message Text:||Successfully created group <group name>|