Zehra: Zehra moved page Search for Player to GMS: Search for Player: let's give prefixes to pages to prevent confusion

2025-11-24T02:22:37Z

Zehra moved page Search for Player to GMS: Search for Player: let's give prefixes to pages to prevent confusion

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

Zehra: category link

2016-12-05T17:09:05Z

category link

← Older revision		Revision as of 17:09, 5 December 2016
Line 50:		Line 50:
	</properties>		</properties>

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

JeffM2501: Move to spec

2013-02-10T08:00:02Z

Move to spec

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

	== Introduction ==		== Introduction ==
Line 49:		Line 49:
	Message Text:= Please provide a player callsign to search for.		Message Text:= Please provide a player callsign to search for.
	</properties>		</properties>

			[[:Category:Group Manager]]

Grans Remedy: New page: {{DesignDocument}} == Introduction == This use case describes the process a group manager will use to search for a player, during the process of adding a player to one or more groups they...

2011-04-26T00:14:28Z

New page: {{DesignDocument}} == Introduction == This use case describes the process a group manager will use to search for a player, during the process of adding a player to one or more groups they...

New page

{{DesignDocument}}

== Introduction ==
This use case describes the process a group manager will use to search for a player, during the process of adding a player to one or more groups they manage.

[[Image:UC_Search_for_player.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 system has displayed details of the player the actor has indicated.

== Requirements and rules realized ==
'''RQ21 Search for player''' 
The system shall enable managers to search for players matching a callsign (name) they provide. 
* ''BR9 Search for exact match then partial'' 
The system shall use the criteria supplied by the actor to search for an exact match. If no exact matches are found then the system shall use a partial match method to find names which are similar. 

'''RQ22 Result set contents''' 
For each player found, the system shall display information in rules BR31 and BR32. 
* ''BR10 Indicate partial match separately'' 
The system shall indicate exact matches and partial matches separately. 
* ''BR29 Sort result set'' 
The system shall sort the result set into ascending alphabetical order using callsign (name). 
* ''BR31 Result list summary'' 
For each player found, the system shall display the player's callsign (name), rank, and the date the callsign was registered. 
* ''BR32 Result detail '' 
The system shall display the following information about the player the actor indicates: the player's callsign (name), rank, the date the callsign was registered, their avatar, and their signature. 

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

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

== Messages ==
<properties>
Step:= EX-1
Condition:= Invalid search criteria or no callsign provided
Message Number:= ERR-1
Message Text:= Please provide a player callsign to search for.
</properties>

GMS: Search for Player - Revision history

Zehra: Zehra moved page Search for Player to GMS: Search for Player: 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 search for a player, during the process of adding a player to one or more groups they...