|
|
| Page | 12/23 | | Date | 30.06.2017 | | Size | 1.14 Mb. | | #22137 |
|
Name of the use case:
| |
Author:
|
Andres Camilo Jimenez Vargas
|
Creation date:
|
24/02/2016
|
Modification date:
|
09/03/2016
|
Notes:
|
|
Scenarios:
|
Alternate
Conventions:
-
Mobile application.
-
Wear application.
-
Server.
|
| -
The user sweeps the notification to the left for the link to open the game.
-
The user taps the button to open the game.
-
UC-029 Send decline game.
-
Close the activity.
|
Basic Path
Conventions:
-
Mobile application.
-
Wear application.
-
Server.
|
| -
The user sweeps the notification to the left for the link to open the game.
-
The user clicks the button to start the game.
-
UC-027 Notify player ready.
-
A new activity rises and wait for the opponent to be ready.
|
|
Restrictions
|
|
Name of the use case:
| |
Author:
|
Andres Camilo Jimenez Vargas
|
Creation date:
|
09/03/2016
|
Modification date:
|
09/03/2016
|
Notes:
|
|
Scenarios:
|
Basic Path
Conventions:
-
Mobile application.
-
Wear application.
-
Server.
|
| -
Create a game instance with the teams.
-
UC-004 Send notification to device.
-
Receive the game id from the server.
|
|
Restrictions
|
Pre-condition (Approved)
|
The match creator selected all team's players.
|
|
Pre-condition (Approved)
|
All players are registered in the server.
|
|
|
Share with your friends: |
|
|
