RICM4 2017 2018 - UltraTeamMV : UML

From air
Revision as of 12:38, 12 February 2018 by Enzo.Molion (talk | contribs) (End user own geolocation reading on the map + Template)
Jump to navigation Jump to search

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

Post-condition

Normal execution
  1. Smartphone loads map
  2. Smartphone displays map
  3. Smartphone loads geolocation from application
  4. Smartphone displays end user's geolocation as a marker
Alternative execution
  • If map can't be loaded or displayed, redirect to previous 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).


Template

Pre-condition
Start


End


Post-condition


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)

Sequence diagram

Deployment diagram

Activity diagram

Relationship diagram