RICM4 2017 2018 - UltraTeamMV : UML - Revision history

Enzo.Molion: /* Relationship diagram */

2018-04-07T15:57:58Z

Relationship diagram

← Older revision		Revision as of 15:57, 7 April 2018
Line 207:		Line 207:

	=Relationship diagram =		=Relationship diagram =

			The following relationship diagram the simple database which is stored in smartphone application :

			[[File:ClassUMLApp.png \| center]]

Enzo.Molion: Deleted Activity diagram section

2018-04-07T15:53:03Z

Deleted Activity diagram section

← Older revision		Revision as of 15:53, 7 April 2018
Line 205:		Line 205:
	== Graph ==		== Graph ==
	[[File:UltrateamMVDeploymentUML.png\|center]]		[[File:UltrateamMVDeploymentUML.png\|center]]

	=Activity diagram=


	=Relationship diagram =		=Relationship diagram =

Enzo.Molion: Deleted template

2018-04-07T15:52:38Z

Deleted template

@@ Line 190: / Line 190: @@
 * Bugfixes should be done as fast as possible,
 * New version should allow retro-compatibility.
 =Sequence diagram=

Enzo.Molion: /* Deployment diagram */

2018-02-23T18:59:38Z

Deployment diagram

← Older revision		Revision as of 18:59, 23 February 2018
Line 234:		Line 234:

	=Deployment diagram=		=Deployment diagram=
			== Graph ==

			[[File:UltrateamMVDeploymentUML.png\|center]]

	=Activity diagram=		=Activity diagram=

Enzo.Molion: /* Graphs */

2018-02-23T18:08:26Z

Graphs

← Older revision		Revision as of 18:08, 23 February 2018
Line 227:		Line 227:

	The following sequence diagram depicts a 3 users course creation :		The following sequence diagram depicts a 3 users course creation :
			[[File:UltrateamMVSequenceUMLCourseCreation.png\|center\|1100px]]
	* TODO


	The following sequence diagram depicts a "Distress signal" situation, where user signals this situation by clicking a button on his ESP32 and nothing is known to any device at this time :		The following sequence diagram depicts a "Distress signal" situation, where user signals this situation by clicking a button on his ESP32 and nothing is known to any device at this time :
	[[File:UltrateamMVSequenceUML.png\|center]]		[[File:UltrateamMVSequenceUML.png\|center\|1100px]]

	=Deployment diagram=		=Deployment diagram=

Enzo.Molion: /* Sequence diagram */

2018-02-23T17:28:41Z

Sequence diagram

← Older revision		Revision as of 17:28, 23 February 2018
Line 224:		Line 224:
	=Sequence diagram=		=Sequence diagram=

			== Graphs ==

			The following sequence diagram depicts a 3 users course creation :
			* TODO

			The following sequence diagram depicts a "Distress signal" situation, where user signals this situation by clicking a button on his ESP32 and nothing is known to any device at this time :
			[[File:UltrateamMVSequenceUML.png\|center]]

	=Deployment diagram=		=Deployment diagram=

Enzo.Molion: /* Graphs */

2018-02-23T16:37:43Z

Graphs

← Older revision		Revision as of 16:37, 23 February 2018
Line 8:		Line 8:

	==Graphs==		==Graphs==
	[[File:UltrateamMVUseCaseUML.png\|~~600px~~\|center]]		[[File:UltrateamMVUseCaseUML.png\|500px\|center]]

	==Case details==		==Case details==

Enzo.Molion: /* Usecase */

2018-02-23T15:16:50Z

Usecase

@@ Line 6: / Line 6: @@
 =Usecase=
 ==Graphs==
 [[File:UltrateamMVUseCaseUML.png|600px|center]]
 ==Case details==
 === End user → Read self geolocation on map===
 ;Pre-conditions :
@@ Line 197: / Line 190: @@
 * Bugfixes should be done as fast as possible,
 * New version should allow retro-compatibility.

Enzo.Molion: /* Case details */

2018-02-13T10:46:09Z

Case details

← Older revision		Revision as of 10:46, 13 February 2018
Line 19:		Line 19:
	=== H ===		=== H ===
	=== End user → Read self geolocation on map===		=== End user → Read self geolocation on map===
	;Pre-~~condition~~ :		;Pre-conditions :
	* Smartphone should be on, with a loaded map into the app		* Smartphone should be on, with a loaded map into the app,
	* The geolocation should be stored in the app		* The geolocation should be stored in the app.

	;Start:		;Start:
Line 36:		Line 36:
	# Smartphone displays end user's geolocation as a marker.		# Smartphone displays end user's geolocation as a marker.

	;Alternative ~~execution~~		;Alternative executions
	* If map can't be loaded or displayed, redirect to another page and display an error message,		* 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.		* If geolocation can't be loaded, display a loaded map and display an error message.

	;Non-functional ~~constraint~~		;Non-functional constraints
	* Loading should take less than 2 seconds as it is a main feature hence frequently used,		* 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).		* Map should be readable even in a non urban area (a acceptable default zoom level shall be used).

	=== End user → Read other hikers’ geolocation on map ===		=== End user → Read other hikers’ geolocation on map ===
	;Pre-~~condition~~ :		;Pre-conditions :
	* Smartphone should be on, with a loaded map into the app		* Smartphone should be on, with a loaded map into the app
	* ~~The other~~ hikers’ geolocation should be stored in the app		* Other hikers’ geolocation should be stored in the app
	* The UI should be on map page

	;Start:		;Start:
	The smartphone ~~does~~ ~~not display anything, the~~ page ~~is blank~~.		The smartphone displays another page.

	;End:		;End:
	The smartphone displays the map with a marker on every other hikers’ geolocation		The smartphone displays the map page with a marker on every other hikers’ geolocation.

	;Normal execution		;Normal execution
			# User clicks on "map page" in menu,
⚫	# Smartphone ~~loads~~ other hikers’ geolocation ~~from~~ ~~application~~
	# Smartphone loads ~~relevant~~ ~~map~~ ~~part~~		# Smartphone loads other hikers’ geolocation from application,
	# Smartphone ~~displays~~ map		# Smartphone loads relevant map part,
	# Smartphone displays ~~other hikers’ geolocation as a marker~~		# Smartphone displays map,
		⚫	# Smartphone displays other hikers’ geolocation as a marker,
			# User scrolls map → smartphone restarts loading and displaying steps.

	;Alternative execution		;Alternative execution
	* If map can't be loaded or displayed, redirect to another page and display an error message		* 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		* If an other hikers’ geolocation can't be loaded or displayed, proceed as if it did not exists

			;Non-functional constraints
			* 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).

Enzo.Molion: /* End user → Read self geolocation on map */

2018-02-13T10:40:06Z

End user → Read self geolocation on map

← Older revision		Revision as of 10:40, 13 February 2018
Line 22:		Line 22:
	* Smartphone should be on, with a loaded map into the app		* Smartphone should be on, with a loaded map into the app
	* The geolocation should be stored in the app		* The geolocation should be stored in the app
	* The UI should be on map page

	;Start:		;Start:
	The smartphone ~~does~~ ~~not display anything, the~~ page ~~is blank~~.		The smartphone displays another page.

	;End:		;End:
	The smartphone displays the map with a marker on end user's geolocation		The smartphone displays the map page with a marker on end user's geolocation.

	;Normal execution		;Normal execution
			# User clicks on "map page" in menu,
⚫	# Smartphone ~~loads~~ geolocation ~~from~~ ~~application~~
	# Smartphone loads ~~relevant~~ ~~map~~ ~~part~~		# Smartphone loads geolocation from application,
	# Smartphone ~~displays~~ map		# Smartphone loads relevant map part,
	# Smartphone displays ~~end user's geolocation as a marker~~		# Smartphone displays map,
		⚫	# Smartphone displays end user's geolocation as a marker.

	;Alternative execution		;Alternative execution
	* If map can't be loaded or displayed, redirect to another page and display an error message		* 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		* If geolocation can't be loaded, display a loaded map and display an error message.

	;Non-functional constraint		;Non-functional constraint
	* Loading should take less than 2 seconds as it is a main feature hence frequently used.		* 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).		* Map should be readable even in a non urban area (a acceptable default zoom level shall be used).



	=== End user → Read other hikers’ geolocation on map ===		=== End user → Read other hikers’ geolocation on map ===