Assign Group Manager

From BZFlagWiki
Revision as of 17:08, 5 December 2016 by Zehra (Talk | contribs) (category link)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
Picture Frame.png This page contains a specification document for an enhancement or feature. It is a work of collaborative development, and may not represent the final design. If you are not part of the development or design group, please post comments and suggestions on the talk page and not in the middle of the design.


Introduction[edit]

This use case describes the process a founder or co-founder of a namespace will use to assign a player as the manager of one or more groups within that namespace.

Group Management is a role any player can be assigned by the founder of a namespace, and they do not have to be a member of the group(s) they manage. The sole function of a group manager is to manage the maintenance of that group by adding and removing players to it.

Use Case diagram

The diagram shows the requirements and rules the use case is responsible for (via the <<requirement>> stereotype).


Pre-conditions[edit]

None


Post conditions[edit]

The system has assigned the player indicated by the actor to a group management role for one or more groups.


Included Use Cases[edit]

Search for Player


Requirements and rules realized[edit]

RQ6 Founders able to view all groups and members
The founder, and any co-founders, of a group namespace shall be able to view all groups and group members associated to that namespace


RQ24 Notify players of changes in roles
The system shall notify a player of any change in role they perform for a namespace.

  • 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.


RQ25 Track changes to roles
The system shall store and track changes in the namespace roles assigned to players according to rule BR35.

  • BR35 Record details of role changes

The system shall record the founder who made the change, player, role, group, namespace and date when any role is assigned to or removed from a player.


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[edit]

The flow of events describes the main actor actions and system responses in the execution of the use case.

Activity diagram showing flow of events


Messages[edit]

Step: EX-1
Condition: Actor is not a founder or co-founder of any namespace
Message Number: ERR-1
Message Text: You cannot assign a group manager because you are not the founder or co-founder of any namespace.



Step: AF-1
Condition: Player indicated by Actor is already group manager or founder of current group
Message Number: MSG-1
Message Text: Player <player name> skipped: already a group manager or founder of group <group name>.



Step: BF-10
Condition: Successfully assigned player to role of group manager for group list
Message Number: MSG-2
Message Text: Successfully assigned player <player name> as manager of <group list>.