This wiki is archived and useful information is being migrated to the main bzflag.org website
Difference between revisions of "Join Group"
Grans Remedy (Talk | contribs) m (→Introduction) |
Grans Remedy (Talk | contribs) m (→Flow of events) |
||
Line 38: | Line 38: | ||
== Flow of events == | == Flow of events == | ||
+ | The flow of events describes the main actor actions and system responses in the execution of the use case. | ||
+ | [[Image:Activity_Join_Group.png|Activity diagram showing flow of events]] | ||
== Messages == | == Messages == |
Revision as of 03:13, 10 April 2011
Contents
Introduction
This use case describes the process a player will use to join a group. Some groups permit anyone to join them, others require that a request be approved by one of the groups managers (or founders).
The diagram shows the requirements and rules the use case is responsible for (via the <<requirement>> stereotype).
Pre-conditions
None
Post conditions
The actor has joined a player group or requested membership in a group.
Requirements and rules realized
- RQ10 Private groups are always closed
The system shall prevent the actor from joining a private group.
- RQ8 Groups have a membership policy
A groups membership policy determines whether a player can join the group or not.
- BR4 Open groups
The system shall enable any player to join a public group with an open membership policy.
- BR5 By Request groups
The system shall enable any player to request membership of a public group with a by-request membership policy.
- BR6 Closed groups
The system shall prevent any player from joining, or requesting to join, a public group with a closed membership policy.
- RQ11 Track the status of membership requests
The system shall store and track the status of membership requests.
- BR7 Alert managers of membership requests
The system shall notify group managers of a membership request for a group they manage.
Flow of events
The flow of events describes the main actor actions and system responses in the execution of the use case.