Difference between revisions of "RICM4 2017 2018 - UltraTeamMV : UML"
Jump to navigation
Jump to search
Enzo.Molion (talk | contribs) (End user own geolocation reading on the map + Template) |
Enzo.Molion (talk | contribs) (End user course creation) |
||
Line 17: | Line 17: | ||
The smartphone displays the map with a marker on end user's geolocation |
The smartphone displays the map with a marker on end user's geolocation |
||
+ | ;Normal execution |
||
− | ;Post-condition: |
||
+ | # Smartphone loads geolocation from application |
||
− | ∅ |
||
+ | # Smartphone loads relevant map part |
||
+ | # Smartphone displays map |
||
+ | # Smartphone displays end user's geolocation as a marker |
||
+ | |||
+ | ;Alternative execution |
||
+ | * If map can't be loaded or displayed, redirect to another page and display an error message |
||
+ | * If geolocation can't be loaded, display a loaded map and display an error message |
||
+ | |||
+ | ;Non-functional constraint |
||
+ | * Loading should take less than 2 seconds as it is a main feature hence frequently used. |
||
+ | * Map should be readable even in a non urban area (a acceptable default zoom level shall be used). |
||
+ | |||
+ | |||
+ | |||
+ | === Read other hikers’ geolocation on the map === |
||
+ | ;Pre-condition : |
||
+ | * Smartphone should be on, with a loaded map into the app |
||
+ | * The other hikers’ geolocation should be stored in the app |
||
+ | * The UI should be on map page |
||
+ | |||
+ | ;Start: |
||
+ | The smartphone does not display anything, the page is blank. |
||
+ | |||
+ | ;End: |
||
+ | The smartphone displays the map with a marker on every other hikers’ geolocation |
||
+ | |||
+ | ;Normal execution |
||
+ | # Smartphone loads other hikers’ geolocation from application |
||
+ | # Smartphone loads relevant map part |
||
+ | # Smartphone displays map |
||
+ | # Smartphone displays other hikers’ geolocation as a marker |
||
+ | |||
+ | ;Alternative execution |
||
+ | * If map can't be loaded or displayed, redirect to another page and display an error message |
||
+ | * If an other hikers’ geolocation can't be loaded or displayed, proceed as if it did not exists |
||
+ | |||
+ | |||
+ | |||
+ | ===End user own geolocation reading on the map=== |
||
+ | ;Pre-condition : |
||
+ | * Smartphone should be on, with a loaded map into the app |
||
+ | * The geolocation should be stored in the app |
||
+ | * The UI should be on map page |
||
+ | |||
+ | ;Start: |
||
+ | The smartphone does not display anything, the page is blank. |
||
+ | |||
+ | ;End: |
||
+ | The smartphone displays the map with a marker on end user's geolocation |
||
;Normal execution |
;Normal execution |
||
Line 27: | Line 76: | ||
;Alternative execution |
;Alternative execution |
||
− | * If map can't be loaded or displayed, redirect to |
+ | * If map can't be loaded or displayed, redirect to another page and display an error message |
* If geolocation can't be loaded, keep map displayed and display an error message |
* If geolocation can't be loaded, keep map displayed and display an error message |
||
Line 36: | Line 85: | ||
+ | === Read specific hiker’s geolocation on the map === |
||
− | ===Template=== |
||
+ | ;Pre-condition : |
||
+ | * Smartphone should be on, with a loaded map into the app |
||
+ | * The other hiker’s geolocation should be stored in the app |
||
+ | * The UI should be on map page |
||
+ | |||
+ | ;Start: |
||
+ | The smartphone does not display anything, the page is blank. |
||
+ | |||
+ | ;End: |
||
+ | The smartphone displays the map centered on a marker displaying other hiker’s geolocation |
||
+ | |||
+ | ;Normal execution |
||
+ | # Smartphone loads specific hiker’s geolocation from application |
||
+ | # Smartphone loads map |
||
+ | # Smartphone displays map centered on |
||
+ | # Smartphone displays other hikers’ geolocation as a marker |
||
+ | |||
+ | ;Alternative execution |
||
+ | * If map can't be loaded or displayed, redirect to another page and display an error message |
||
+ | * If an other hikers’ geolocation can't be loaded or displayed, proceed as if it did not exists |
||
+ | |||
+ | |||
+ | |||
+ | === End user course creation === |
||
+ | ;Pre-condition : |
||
+ | * Application is launched on home page. |
||
+ | |||
+ | ;Start: |
||
+ | Course does not exist. |
||
+ | |||
+ | ;End: |
||
+ | A course was created. Application generated an AES encryption key. |
||
+ | |||
+ | ;Normal execution |
||
+ | # User clicks on "Create course" |
||
+ | # AES encryption key is generated |
||
+ | # A QRCode is displayed on screen |
||
+ | |||
+ | ;Alternative execution |
||
+ | * If something goes wrong, smartphone should display a "cancel | recreate course" button |
||
+ | |||
+ | ;Non-functional constraint |
||
+ | * QRCode generation should be under 10 seconds |
||
+ | * Smartphone display should be large and bright enough for other users to flash it |
||
+ | |||
+ | |||
+ | |||
+ | === Template === |
||
;Pre-condition : |
;Pre-condition : |
||
* |
* |
||
Line 47: | Line 144: | ||
;End: |
;End: |
||
− | |||
− | ;Post-condition: |
||
Revision as of 13:08, 12 February 2018
Usecase
Graph
Case details
End user own geolocation reading on the map
- Pre-condition
- Smartphone should be on, with a loaded map into the app
- The geolocation should be stored in the app
- The UI should be on map page
- Start
The smartphone does not display anything, the page is blank.
- End
The smartphone displays the map with a marker on end user's geolocation
- Normal execution
- Smartphone loads geolocation from application
- Smartphone loads relevant map part
- Smartphone displays map
- Smartphone displays end user's geolocation as a marker
- Alternative execution
- If map can't be loaded or displayed, redirect to another page and display an error message
- If geolocation can't be loaded, display a loaded map and display an error message
- Non-functional constraint
- Loading should take less than 2 seconds as it is a main feature hence frequently used.
- Map should be readable even in a non urban area (a acceptable default zoom level shall be used).
Read other hikers’ geolocation on the map
- Pre-condition
- Smartphone should be on, with a loaded map into the app
- The other hikers’ geolocation should be stored in the app
- The UI should be on map page
- Start
The smartphone does not display anything, the page is blank.
- End
The smartphone displays the map with a marker on every other hikers’ geolocation
- Normal execution
- Smartphone loads other hikers’ geolocation from application
- Smartphone loads relevant map part
- Smartphone displays map
- Smartphone displays other hikers’ geolocation as a marker
- Alternative execution
- If map can't be loaded or displayed, redirect to another page and display an error message
- If an other hikers’ geolocation can't be loaded or displayed, proceed as if it did not exists
End user own geolocation reading on the map
- Pre-condition
- Smartphone should be on, with a loaded map into the app
- The geolocation should be stored in the app
- The UI should be on map page
- Start
The smartphone does not display anything, the page is blank.
- End
The smartphone displays the map with a marker on end user's geolocation
- Normal execution
- Smartphone loads map
- Smartphone displays map
- Smartphone loads geolocation from application
- Smartphone displays end user's geolocation as a marker
- Alternative execution
- If map can't be loaded or displayed, redirect to another page and display an error message
- If geolocation can't be loaded, keep map displayed and display an error message
- Non-functional constraint
- Loading should take less than 2 seconds as it is a main feature hence frequently used.
- Map should be readable even in a non urban area (a acceptable default zoom level shall be used).
Read specific hiker’s geolocation on the map
- Pre-condition
- Smartphone should be on, with a loaded map into the app
- The other hiker’s geolocation should be stored in the app
- The UI should be on map page
- Start
The smartphone does not display anything, the page is blank.
- End
The smartphone displays the map centered on a marker displaying other hiker’s geolocation
- Normal execution
- Smartphone loads specific hiker’s geolocation from application
- Smartphone loads map
- Smartphone displays map centered on
- Smartphone displays other hikers’ geolocation as a marker
- Alternative execution
- If map can't be loaded or displayed, redirect to another page and display an error message
- If an other hikers’ geolocation can't be loaded or displayed, proceed as if it did not exists
End user course creation
- Pre-condition
- Application is launched on home page.
- Start
Course does not exist.
- End
A course was created. Application generated an AES encryption key.
- Normal execution
- User clicks on "Create course"
- AES encryption key is generated
- A QRCode is displayed on screen
- Alternative execution
- If something goes wrong, smartphone should display a "cancel | recreate course" button
- Non-functional constraint
- QRCode generation should be under 10 seconds
- Smartphone display should be large and bright enough for other users to flash it
Template
- Pre-condition
- Start
- End
- Normal execution
- Alternative execution
- Non-functional constraint
[Suggestions :]
- Time
- Cost
- Direct environment constraints (physical environment, connections, interfaces, safety, testability, deployment...)
- Indirect environment constraints : PESTLE analysis (Political, Economic, Social, Technological, Environmental, Legal)