GMS: Join Group - Revision history

Zehra: Zehra moved page Join Group to GMS: Join Group: let's give prefixes to pages to prevent confusion

2025-11-24T02:18:32Z

Zehra moved page Join Group to GMS: Join Group: let's give prefixes to pages to prevent confusion

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

Zehra: category link

2016-12-05T17:05:00Z

category link

← Older revision		Revision as of 17:05, 5 December 2016
Line 46:		Line 46:
	They system shall use a forum private message, email message, and a message displayed on the group management system main page to alert group managers of pending requests. <br />		They system shall use a forum private message, email message, and a message displayed on the group management system main page to alert group managers of pending requests. <br />

	~~[[:Category:Group Manager]]~~
	* ''BR10 Prevent duplicate requests'' <br />		* ''BR10 Prevent duplicate requests'' <br />
	The system shall prevent players from requesting to join a group where they have a request for the same group pending, or a previous identical request was actioned within the last 30 days. <br />		The system shall prevent players from requesting to join a group where they have a request for the same group pending, or a previous identical request was actioned within the last 30 days. <br />
Line 63:		Line 62:
	Message Text:= You were successfully added to the following group(s) <<added group list>>. Additionally, your requests to join the following groups <<request group list>> have been sent to the respective group managers.		Message Text:= You were successfully added to the following group(s) <<added group list>>. Additionally, your requests to join the following groups <<request group list>> have been sent to the respective group managers.
	</properties>		</properties>
			[[Category:Group Manager]]

JeffM2501: Move to spec

2013-02-10T07:58:45Z

Move to spec

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

	== Introduction ==		== Introduction ==
Line 46:		Line 46:
	They system shall use a forum private message, email message, and a message displayed on the group management system main page to alert group managers of pending requests. <br />		They system shall use a forum private message, email message, and a message displayed on the group management system main page to alert group managers of pending requests. <br />

			[[:Category:Group Manager]]
	* ''BR10 Prevent duplicate requests'' <br />		* ''BR10 Prevent duplicate requests'' <br />
	The system shall prevent players from requesting to join a group where they have a request for the same group pending, or a previous identical request was actioned within the last 30 days. <br />		The system shall prevent players from requesting to join a group where they have a request for the same group pending, or a previous identical request was actioned within the last 30 days. <br />

Grans Remedy: /* Requirements and rules realized */

2011-04-24T23:34:47Z

Requirements and rules realized

← Older revision		Revision as of 23:34, 24 April 2011
Line 47:		Line 47:

	* ''BR10 Prevent duplicate requests'' <br />		* ''BR10 Prevent duplicate requests'' <br />
	The system shall prevent players from requesting to join a group where they have a request for the same group pending, or ~~their~~ previous request was actioned within the last 30 days. <br />		The system shall prevent players from requesting to join a group where they have a request for the same group pending, or a previous identical request was actioned within the last 30 days. <br />


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

Grans Remedy: Added notification format and duplicate request rules

2011-04-24T23:33:13Z

Added notification format and duplicate request rules

← Older revision		Revision as of 23:33, 24 April 2011
Line 21:		Line 21:


	== ~~Extension use cases~~ ==		== Requirements and rules realized ==
	~~[[Request Membership]]~~		'''RQ10 Private groups are always closed'''<br />
			The system shall prevent the actor from joining a private group.<br />


	~~== Requirements and rules realized ==~~		'''RQ8 Groups have a membership policy''' <br />
	* ''~~RQ10 Private~~ groups ~~are always closed~~''		A groups membership policy determines whether a player can join the group or not.<br />
	The system shall ~~prevent the actor from joining~~ a ~~private~~ group.		* ''BR4 Open groups'' <br />
			The system shall enable any player to join a public group with an open membership policy.<br />

	* ''~~RQ8 Groups have a membership policy~~''		* ''BR5 By Request groups''<br />
	~~A groups~~ membership ~~policy determines whether~~ a ~~player can join the~~ group ~~or not~~.		The system shall enable any player to request membership of a public group with a by-request membership policy.<br />

	* ''~~BR4 Open~~ groups''		* ''BR6 Closed groups''<br />
	The system shall ~~enable~~ any player to join a public group with ~~an open~~ membership policy.		The system shall prevent any player from joining, or requesting to join, a public group with a closed membership policy.<br />

	* ''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~~''		'''RQ11 Track the status of membership requests'''<br />
	The system shall ~~prevent any player from joining, or requesting to join, a public~~ group ~~with~~ a ~~closed~~ membership ~~policy~~.		The system shall store and track the status of membership requests.<br />
			* ''BR7 Alert group managers''<br />
			The system shall notify group managers of a membership request for a group they manage.<br />

	* ''~~RQ11 Track the status of membership requests~~''		* ''BR9 Notification format''<br />
	~~The~~ system shall ~~store~~ and ~~track~~ the ~~status~~ of ~~membership~~ requests.		They system shall use a forum private message, email message, and a message displayed on the group management system main page to alert group managers of pending requests. <br />

	* ''~~BR7 Alert managers of membership~~ requests''		* ''BR10 Prevent duplicate requests'' <br />
	The system shall ~~notify~~ group ~~managers of~~ a ~~membership~~ request for a group ~~they manage~~.		The system shall prevent players from requesting to join a group where they have a request for the same group pending, or their previous request was actioned within the last 30 days. <br />

Grans Remedy: /* Messages */

2011-04-23T02:57:15Z

Messages

← Older revision		Revision as of 02:57, 23 April 2011
Line 59:		Line 59:
	Condition:= Player added to group		Condition:= Player added to group
	Message Number:= Msg 4		Message Number:= Msg 4
	Message Text:= You were successfully added to the following group(s) <<group ~~name~~ list>>.		Message Text:= You were successfully added to the following group(s) <<added group list>>. Additionally, your requests to join the following groups <<request group list>> have been sent to the respective group managers.
	</properties>		</properties>

Grans Remedy: /* Messages */

2011-04-23T02:10:52Z

Messages

← Older revision		Revision as of 02:10, 23 April 2011
Line 55:		Line 55:

	== Messages ==		== Messages ==
	~~<properties>~~
	~~Step:= EX-1~~
	~~Condition:= No group found~~
	~~Message Number:= Err 1~~
	~~Message Text:= No group with that name was found.~~
	~~</properties>~~

	~~----~~

	<properties>		<properties>
	Step:= BF-9		Step:= BF-9
	Condition:= Player added to group		Condition:= Player added to group
	Message Number:= Msg 4		Message Number:= Msg 4
	Message Text:= You were successfully added to the group <<group name>>.		Message Text:= You were successfully added to the following group(s) <<group name list>>.
	</properties>		</properties>

Grans Remedy at 08:37, 18 April 2011

2011-04-18T08:37:42Z

← Older revision		Revision as of 08:37, 18 April 2011
Line 7:		Line 7:

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


	== Pre-conditions ==		== Pre-conditions ==
Line 14:		Line 15:
	== Post conditions ==		== Post conditions ==
	The actor has joined a player group or requested membership in a group.		The actor has joined a player group or requested membership in a group.


			== Included use cases ==
			[[Search for Groups]]


			== Extension use cases ==
			[[Request Membership]]


	== Requirements and rules realized ==		== Requirements and rules realized ==
Line 36:		Line 46:
	* ''BR7 Alert managers of membership requests''		* ''BR7 Alert managers of membership requests''
	The system shall notify group managers of a membership request for a group they manage.		The system shall notify group managers of a membership request for a group they manage.


	== Flow of events ==		== Flow of events ==
Line 41:		Line 52:

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


	== Messages ==		== Messages ==

Grans Remedy: /* Messages */

2011-04-10T03:21:19Z

Messages

← Older revision		Revision as of 03:21, 10 April 2011
Line 43:		Line 43:

	== Messages ==		== Messages ==
			<properties>
			Step:= EX-1
			Condition:= No group found
			Message Number:= Err 1
			Message Text:= No group with that name was found.
			</properties>

			----

			<properties>
			Step:= BF-9
			Condition:= Player added to group
			Message Number:= Msg 4
			Message Text:= You were successfully added to the group <<group name>>.
			</properties>

Grans Remedy: /* Flow of events */

2011-04-10T03:13:57Z

Flow of events

← Older revision		Revision as of 03:13, 10 April 2011
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 ==