Zehra: Zehra moved page Update Membership Request to GMS: Update Membership Request: let's give prefixes to pages to prevent confusion

2025-11-24T02:23:23Z

Zehra moved page Update Membership Request to GMS: Update Membership Request: let's give prefixes to pages to prevent confusion

← Older revision		Revision as of 02:23, 24 November 2025
(No difference)

Zehra: category link

2016-12-05T17:06:28Z

category link

← Older revision		Revision as of 17:06, 5 December 2016
Line 48:		Line 48:
	The system shall notify the player who submitted the request of any change in its status. <br />		The system shall notify the player who submitted the request of any change in its status. <br />

	~~[[:Category:Group Manager]]~~

	== Flow of events ==		== Flow of events ==
Line 72:		Line 71:
	Message Text:= The membership request has been updated, and the player notified of the result.		Message Text:= The membership request has been updated, and the player notified of the result.
	</properties>		</properties>

			[[Category:Group Manager]]

JeffM2501: Move to spec

2013-02-10T07:57:58Z

Move to spec

← Older revision		Revision as of 07:57, 10 February 2013
Line 1:		Line 1:
	{{~~DesignDocument~~}}		{{Specification}}

	== Introduction ==		== Introduction ==
Line 48:		Line 48:
	The system shall notify the player who submitted the request of any change in its status. <br />		The system shall notify the player who submitted the request of any change in its status. <br />

			[[:Category:Group Manager]]

	== Flow of events ==		== Flow of events ==

Grans Remedy: New page: {{DesignDocument}} == Introduction == This use case describes the process a group manager will use to approve or decline a request from a player to join a group. [[Image:UC_Update_Membe...

2011-04-25T02:44:27Z

New page: {{DesignDocument}} == Introduction == This use case describes the process a group manager will use to approve or decline a request from a player to join a group. [[Image:UC_Update_Membe...

New page

{{DesignDocument}}

== Introduction ==
This use case describes the process a group manager will use to approve or decline a request from a player to join a group.

[[Image:UC_Update_Membership_Request.png|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 membership request has been updated.

== Requirements and rules realized ==
'''RQ11 Track the status of membership requests''' 
The system shall store and track the status of membership requests. 
* ''BR19 Record change in request status'' 
The system shall record the change in status from 'pending' to 'actioned', and optionally a note, for each request when one of the groups managers has indicated the outcome of the request. 
* ''BR20 Record request result'' 
The system shall record the result of each request which shall be either 'approved' or 'declined', along with the date of the decision, the manager who made it and optionally a note. 
* ''BR21 Membership request information'' 
The system shall record the player, date, group and optionally a note from the player for each membership request. 
* ''BR25 Actioned requests cannot be updated'' 
The system shall prevent a request which has already been actioned from having its result changed. 

'''RQ14 Viewing membership requests''' 
The system shall enable players to view the requests they have submitted. 
* ''BR22 Group managers view all requests'' 
The system shall enable group managers to view all requests, both pending and actioned, for the groups they manage. 

'''RQ16 Format of request list''' 
The system shall format the list of membership requests according to the following rules: BR23, BR24 
* ''BR23 Group by namespace'' 
The system shall enable the actor to view the requests belonging to each namespace separately. 
* ''BR24 Filter by status'' 
The system shall enable the actor to filter the requests by status; viewing only those 'pending', 'resulted', or both. 

'''RQ15 Notify player of changes''' 
The system shall notify the player who submitted the request of any change in its status. 

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

[[Image:Activity_Update_Membership.png|Activity diagram showing flow of events]]

== Messages ==
<properties>
Step:= BF-3
Condition:= Actor indicated update request
Message Number:= MSG-1
Message Text:= Please confirm that you want to <approve | decline> this request.
</properties>

----

<properties>
Step:= BF-7
Condition:= Request updated
Message Number:= MSG-2
Message Text:= The membership request has been updated, and the player notified of the result.
</properties>

GMS: Update Membership Request - Revision history

Zehra: Zehra moved page Update Membership Request to GMS: Update Membership Request: let's give prefixes to pages to prevent confusion

Zehra: category link

JeffM2501: Move to spec

Grans Remedy: New page: {{DesignDocument}} == Introduction == This use case describes the process a group manager will use to approve or decline a request from a player to join a group. [[Image:UC_Update_Membe...