Difference between revisions of "Remove User from Group"

From BZFlagWiki
Jump to: navigation, search
(New page: {{DesignDocument}} == Introduction == This use case describes the process a group manager will use to remove a player from a group they manage. [[Image:UC_Remove_player_from_group.png|Us...)
 
(Move to spec)
Line 1: Line 1:
{{DesignDocument}}
+
{{Specification}}
  
 
== Introduction ==
 
== Introduction ==
Line 55: Line 55:
 
Message Text:= Player <player name> has been removed from Group <group name>.
 
Message Text:= Player <player name> has been removed from Group <group name>.
 
</properties>
 
</properties>
 +
 +
[[:Category:Group Manager]]

Revision as of 07:58, 10 February 2013

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

This use case describes the process a group manager will use to remove a player from a group they manage.

Use Case diagram

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


Pre-conditions

None


Post conditions

The system has removed the player from a group.


Included Use Cases

View Groups


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.

Activity diagram showing flow of events


Messages

Step: BF-6
Condition: Successfully removed player from group
Message Number: MSG-1
Message Text: Player <player name> has been removed from Group <group name>.


Category:Group Manager