This use case describes the process a founder will use to assign a player as a co-founder for a namespace.
The diagram shows the requirements and rules the use case is responsible for (via the <<requirement>> stereotype).
The system has granted the player indicated by the actor a co-founder role for the selected namespace.
Included Use Cases
Requirements and rules realized
RQ31 Founders manage co-founders
The system shall prevent any player other than the founder of a namespace, from assigning or removing co-founders from that namespace.
RQ26 Notify founder changes
The system shall notify a namespace founder of any changes according to rules: BR36, BR38
- BR38 Changes to namespaces
The system shall notify the namespace founders and co-founders when a co-founder has been assigned or removed from a namespace.
RQ19 Notify players of changes in membership
The system shall notify a player if they have been added to, or removed from any group or granted or forfeited any role.
- 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 and roles.
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 namespace because you are not a founder/co-founder.|
|Condition:||Selected player is already a co-founder of selected namespace|
|Message Text:||Player <player name> is already a co-founder of the <namespace name> namespace|
|Condition:||Successfully assigned co-founder.|
|Message Text:||Successfully assigned player <player name> as co-founder of <namespace name> namespace.|