Difference between revisions of "RICM4 2017 2018 - Dashboard/UML"
Jump to navigation
Jump to search
Line 1: | Line 1: | ||
+ | This page gathers the UML diagram of our project [https://air.imag.fr/index.php/Dashboard_pour_gestionnaire_de_t%C3%A2ches Dashboard]. |
||
+ | |||
=Use Case Diagram= |
=Use Case Diagram= |
||
[[File:UserCaseDiagram.jpeg|800px|center]] |
[[File:UserCaseDiagram.jpeg|800px|center]] |
||
+ | |||
+ | ==Detailed Use Case== |
||
+ | We will detail only 3 cases here, because the others work relatively the same. Adding, Modifying, Deleting a job or a resources works the same way, except for the request sent to OAR and the pre-condition. The latter is : |
||
+ | * 'User needs to be authenticated' for all the jobs related actions |
||
+ | * 'User needs to be an administrator' for all the resources related actions |
||
+ | |||
+ | ===Log in=== |
||
+ | '''Pre-conditions''' |
||
+ | * User must be on the login page |
||
+ | * User must not be already logged in |
||
+ | |||
+ | '''Start''' |
||
+ | |||
+ | When the user enters name and password and clicks on 'Log in'. |
||
+ | |||
+ | '''End''' |
||
+ | |||
+ | Once the home page is loaded. |
||
+ | |||
+ | '''Normal execution''' |
||
+ | * User clicks on 'Log in' |
||
+ | * The application gets the name and password |
||
+ | * It sends it to OAR via a request |
||
+ | * It evaluates the answer and get the user's data |
||
+ | * It loads automatically on the home page. |
||
+ | |||
+ | '''Alternatives''' |
||
+ | |||
+ | If the user enters a wrong name or password, a error message pops up. |
||
+ | |||
+ | ===Log out=== |
||
+ | '''Pre-conditions''' |
||
+ | * User needs to be authenticated |
||
+ | |||
+ | '''Start''' |
||
+ | |||
+ | When the user clicks on 'Log out'. |
||
+ | |||
+ | '''End''' |
||
+ | |||
+ | Once the home page is reloaded. |
||
+ | |||
+ | '''Execution''' |
||
+ | * User clicks on 'Log Out' |
||
+ | * The application remove the user's data |
||
+ | * It reloads the home page. |
||
+ | |||
+ | |||
+ | ===Add job=== |
||
+ | '''Pre-conditions''' |
||
+ | * User needs to be authenticated |
||
+ | |||
+ | '''Start''' |
||
+ | |||
+ | When the user clicks on 'Add Job'. |
||
+ | |||
+ | '''End''' |
||
+ | |||
+ | Once the home page is reloaded. |
||
+ | |||
+ | '''Execution''' |
||
+ | * User clicks on 'Add job' |
||
+ | * User fill out the form |
||
+ | * The application gets the data |
||
+ | * It sends it to OAR via a request |
||
+ | * It evaluates the answer and request for the new list of jobs submitted |
||
+ | * It evaluates the answer and loads automatically on the 'Jobs' list' page. |
||
=Sequence Diagrams= |
=Sequence Diagrams= |
||
+ | |||
==Adding job== |
==Adding job== |
||
[[File:AddSequenceDiagram.jpeg|800px|center]] |
[[File:AddSequenceDiagram.jpeg|800px|center]] |
Revision as of 20:43, 7 April 2018
This page gathers the UML diagram of our project Dashboard.
Use Case Diagram
Detailed Use Case
We will detail only 3 cases here, because the others work relatively the same. Adding, Modifying, Deleting a job or a resources works the same way, except for the request sent to OAR and the pre-condition. The latter is :
- 'User needs to be authenticated' for all the jobs related actions
- 'User needs to be an administrator' for all the resources related actions
Log in
Pre-conditions
- User must be on the login page
- User must not be already logged in
Start
When the user enters name and password and clicks on 'Log in'.
End
Once the home page is loaded.
Normal execution
- User clicks on 'Log in'
- The application gets the name and password
- It sends it to OAR via a request
- It evaluates the answer and get the user's data
- It loads automatically on the home page.
Alternatives
If the user enters a wrong name or password, a error message pops up.
Log out
Pre-conditions
- User needs to be authenticated
Start
When the user clicks on 'Log out'.
End
Once the home page is reloaded.
Execution
- User clicks on 'Log Out'
- The application remove the user's data
- It reloads the home page.
Add job
Pre-conditions
- User needs to be authenticated
Start
When the user clicks on 'Add Job'.
End
Once the home page is reloaded.
Execution
- User clicks on 'Add job'
- User fill out the form
- The application gets the data
- It sends it to OAR via a request
- It evaluates the answer and request for the new list of jobs submitted
- It evaluates the answer and loads automatically on the 'Jobs' list' page.