|
|
| Page | 17/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:
|
07/05/2016
|
Notes:
|
|
Scenarios:
|
Basic Path
Conventions:
-
Mobile application.
-
Wear application.
-
Server.
|
|
1. A player decline a game.
2. Notify host
3. UC-032 Cancel match
|
|
Restrictions
|
|
Name of the use case:
| |
Author:
|
Andres Camilo Jimenez Vargas
|
Creation date:
|
24/02/2016
|
Modification date:
|
09/03/2016
|
Notes:
|
|
Scenarios:
|
Basic Path
Conventions:
-
Mobile application.
-
Wear application.
-
Server.
|
| -
A new game instance is created with a unique id.
-
All information of the teams is stored in the game instance.
-
Wait for the player to be ready.
|
|
Restrictions
|
Pre-condition (Approved)
|
All players must be registered in the server.
|
|
Pre-condition (Approved)
|
A notification request arrived from a mobile application.
|
|
|
Name of the use case:
| UC-032 Cancel match |
Author:
|
Andres Camilo Jimenez Vargas
|
Creation date:
|
24/02/2016
|
Modification date:
|
07/05/2016
|
Notes:
|
|
Scenarios:
|
Basic Path
Conventions:
-
Mobile application.
-
Wear application.
-
Server.
|
|
1. Send message to finish game to players.
2. Send message to finish game to host.
|
|
Restrictions
|
Invariant (Approved)
|
All players are registered
|
|
Invariant (Approved)
|
A player declines a game
|
|
|
7.3 Functional Requirement Document
POLYTECHNIC OF TURIN
Faculty of Engineering
Master's Degree
in Computer Engineering
Functional Requirements Specification
Andres Camilo Jimenez Vargas
Share with your friends: |
|
|
