RICM4 2017 2018 - SeriousGame Polystar /UML: Difference between revisions
Tim.Lepage (talk | contribs) No edit summary |
|||
| (17 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
= Use case = |
|||
'''Cas n°1''' |
|||
== Case n ° 1 == |
|||
Cas d'utilisation : Jouer une partie |
|||
Description : Les joueurs jouent une partie et le teacher supervise la partie |
|||
'''Use case:''' Play a game |
|||
Acteur : Joueurs et Teacher |
|||
'''Description:''' Players play a game and the teacher supervises the game |
|||
Parties prenantes et leurs intérêts : - Joueurs, objectif : gagner la partie |
|||
- Teacher, objectif : superviser la partie |
|||
'''Actor:''' Players and Teacher |
|||
Pré-conditions : Suffisamment de joueurs sont réunis pour jouer et lancent la partie |
|||
'''Stakeholders and their interests:''' |
|||
Scénario nominal : |
|||
- Players, goal: win the game |
|||
- Le système affiche le menu |
|||
- Teacher, goal: supervise the game |
|||
'''Pre-conditions:''' Enough players are gathered to play and throw the game |
|||
- Les joueurs sélectionnent le type de partie (unit et langue) |
|||
'''Nominal scenario:''' |
|||
- Le système affiche la page de jeu |
|||
- The system displays the menu |
|||
- Les joueurs jouent au jeu |
|||
- Players select the type of game (unit and language) |
|||
- Les joueurs finissent la partie |
|||
- The system displays the game page |
|||
Les scénarios alternatifs : |
|||
- Les joueurs quittent le jeu avant la fin |
|||
- Players play the game |
|||
Fin : scénarios d ou e selon décision des utilisateurs |
|||
- Players finish the game |
|||
''' |
'''Alternative scenarios:''' |
||
- Players leave the game early |
|||
Cas d'utilisation : Modifier le jeu |
|||
Description : Le Teacher modifie le jeu en supprimant / ajoutant / modifiant des cartes |
|||
'''End:''' scenarios d or e according to user's decision |
|||
Acteur : Teacher |
|||
Parties prenantes et leurs intérêts : - Teacher, objectif : modifier le jeu |
|||
Pré-conditions : Authentification par un mot de passe |
|||
== Case n ° 2 == |
|||
Scénario nominal: |
|||
Le système affiche le menu |
|||
Le Teacher sélectionne “modify” |
|||
'''Use case:''' Edit game |
|||
Le système affiche le système d’authentification |
|||
Le Teacher s’identifie |
|||
'''Description:''' The Teacher modifies the game by deleting / adding / modifying cards |
|||
Le système affiche les options de modification |
|||
Le Teacher modifie le jeu |
|||
'''Actor:''' Teacher |
|||
Le système demande confirmation de la modification |
|||
La modification est prise en compte par le système |
|||
'''Stakeholders and their interests:''' - Teacher, goal: modify the game |
|||
Les scénarios alternatifs: |
|||
Le Teacher ne s’identifie pas |
|||
'''Pre-conditions:''' Authentication with a password |
|||
Le Teacher quitte l’écran de modification |
|||
Le Teacher ne valide pas les modifications |
|||
'''Nominal scenario:''' |
|||
Fin: scénarios c, e, g ou h selon les décisions de l’utilisateur |
|||
- The system displays the menu |
|||
- Teacher selects "modify" |
|||
- The system displays the authentication system |
|||
- The Teacher identifies himself |
|||
- The system displays modification options |
|||
- The teacher modifies the game |
|||
- The system requests confirmation of the change |
|||
- The modification is taken into account by the system |
|||
'''Alternative scenarios:''' |
|||
- Teacher does not identify himself |
|||
- The Teacher exits the edit screen |
|||
- Teacher does not validate changes |
|||
'''End:''' scenarios c, e, g or h according to the user's decisions |
|||
=UML Diagram= |
|||
[[File:Polystar_usage_diagram.png]] |
|||
=Sequence Diagram= |
|||
The sequence diagram bellow depicts the first turn of the game. |
|||
[[File:Polystar_game_diagram.png]] |
|||
The following sequence diagram depicts the different ways to modifiy the collection of cards. |
|||
[[File:Polystar_modification_diagram.png]] |
|||
=Deployment Diagram= |
|||
[[File: DeploymentDiagram_Polystar.jpg]] |
|||
Latest revision as of 12:15, 4 April 2018
Use case
Case n ° 1
Use case: Play a game
Description: Players play a game and the teacher supervises the game
Actor: Players and Teacher
Stakeholders and their interests:
- Players, goal: win the game
- Teacher, goal: supervise the game
Pre-conditions: Enough players are gathered to play and throw the game
Nominal scenario:
- The system displays the menu
- Players select the type of game (unit and language)
- The system displays the game page
- Players play the game
- Players finish the game
Alternative scenarios: - Players leave the game early
End: scenarios d or e according to user's decision
Case n ° 2
Use case: Edit game
Description: The Teacher modifies the game by deleting / adding / modifying cards
Actor: Teacher
Stakeholders and their interests: - Teacher, goal: modify the game
Pre-conditions: Authentication with a password
Nominal scenario:
- The system displays the menu
- Teacher selects "modify"
- The system displays the authentication system
- The Teacher identifies himself
- The system displays modification options
- The teacher modifies the game
- The system requests confirmation of the change
- The modification is taken into account by the system
Alternative scenarios:
- Teacher does not identify himself
- The Teacher exits the edit screen
- Teacher does not validate changes
End: scenarios c, e, g or h according to the user's decisions
UML Diagram
Sequence Diagram
The sequence diagram bellow depicts the first turn of the game.
The following sequence diagram depicts the different ways to modifiy the collection of cards.
Deployment Diagram
