GMS: Functional Requirements - Revision history

Zehra: Zehra moved page Group management system functional requirements to GMS: Functional Requirements: let's give prefixes to pages to prevent confusion

2025-11-24T02:13:09Z

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

2016-12-05T03:04:06Z

category link

2013-02-10T07:57:14Z

← Older revision		Revision as of 07:57, 10 February 2013
Line 1:		Line 1:
	{{~~DesignDocument~~}}		{{Specification}}
	The functional requirements for the Group Management System will be detailed in the following sections with [http://en.wikipedia.org/wiki/Use_case Use Cases] and other [http://en.wikipedia.org/wiki/Unified_Modeling_Language UML] models.		The functional requirements for the Group Management System will be detailed in the following sections with [http://en.wikipedia.org/wiki/Use_case Use Cases] and other [http://en.wikipedia.org/wiki/Unified_Modeling_Language UML] models.

Line 48:		Line 48:

	[[GMS Detailed Design]]		[[GMS Detailed Design]]

			[[:Category:Group Manager]]

2011-06-13T07:45:02Z

← Older revision		Revision as of 07:45, 13 June 2011
Line 34:		Line 34:
	16. [[Get Player Groups]] <br />		16. [[Get Player Groups]] <br />
	17. [[Make System Change]] <br />		17. [[Make System Change]] <br />


			== Architecture ==
			The proposed architecture for the Group Management System follows the proven 3-tier model, with the separation of concerns of presentation, application logic and data access.

			[[GMS Architecture]]


			== Detailed Design ==
			The detailed design will be modelled with UML Sequence diagrams for each Use Case, showing a view of participating classes and the messages sent to each class. A class model of the database schema will detail the physical table structure, and show the ''proposed'' integration with the BZFlag forum database for user management.

			Note: this integration is needed to provide a 'single-sign-on' to the Group Management System, where a registered player will not need a separate set of credentials to use the GMS.

			[[GMS Detailed Design]]

2011-04-27T08:13:29Z

Use Cases

2011-04-25T03:41:30Z

Use Cases

← Older revision		Revision as of 03:41, 25 April 2011
Line 22:		Line 22:
	4. [[Search for Groups]] <br />		4. [[Search for Groups]] <br />
	5. [[Update Membership Request]] <br />		5. [[Update Membership Request]] <br />
			6. [[Assign User to Group]] <br />
			7. [[Remove User from Group]] <br />
			8. [[Assign Group Manager]] <br />
			9. [[Remove Group Manager]] <br />
			10. [[Create Group]] <br />
			11. [[Rename Group]] <br />
			12. [[Delete Group]] <br />
			13. [[Assign co-founder]] <br />
			14. [[Remove co-founder]] <br />
			15. [[Verify Player]] <br />
			16. [[Get Player Groups]] <br />
			17. [[Make System Change]] <br />

2011-04-24T23:40:14Z

Use Cases

← Older revision		Revision as of 23:40, 24 April 2011
Line 21:		Line 21:
	3. [[Join Group]] <br />		3. [[Join Group]] <br />
	4. [[Search for Groups]] <br />		4. [[Search for Groups]] <br />
	5. [[Request ~~Membership~~]] <br />		5. [[Update Membership Request]] <br />

2011-04-18T08:39:42Z

Use Cases

2011-04-10T00:48:02Z

Use Cases

2011-04-06T09:58:40Z

Use Cases

← Older revision		Revision as of 09:58, 6 April 2011
Line 17:		Line 17:
	Use Cases describe the functional requirements of the system from the end users perspective, where each use case is a goal or purpose the user has in using the system.		Use Cases describe the functional requirements of the system from the end users perspective, where each use case is a goal or purpose the user has in using the system.

	1. [[Register Group Namespace]]		1. [[Register Group Namespace]]<br />
	2. [[View Groups]]		2. [[View Groups]]