Difference between revisions of "Search for Player"
m (Move to spec)
|Line 50:||Line 50:|
Latest revision as of 17:09, 5 December 2016
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.
The diagram shows the requirements and rules the use case is responsible for (via the <<requirement>> stereotype).
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.
|Condition:||Invalid search criteria or no callsign provided|
|Message Text:||Please provide a player callsign to search for.|