RICM4 2017 2018 - UltraTeamMV : SRS - Revision history

Enzo.Molion: /* Specific requirements, covering functional, non-functional and interface requirements */

2018-02-23T15:14:13Z

Specific requirements, covering functional, non-functional and interface requirements

← Older revision		Revision as of 15:14, 23 February 2018
Line 59:		Line 59:
	A team needs at least 1 smartphone (with GPS connection) and 1 ESP32 per hiker.		A team needs at least 1 smartphone (with GPS connection) and 1 ESP32 per hiker.

	=Specific ~~requirements, covering functional, non-functional and interface~~ requirements=		=Specific requirements=

	'''This section is supposed to describe two types of requirements : '''		'''This section is supposed to describe two types of requirements : '''

2018-02-23T15:13:41Z

Purpose of the requirements document

← Older revision		Revision as of 15:13, 23 February 2018
Line 4:		Line 4:
	==Purpose of the requirements document==		==Purpose of the requirements document==
	This Software Requirements Specification (SRS) identifies the requirements for project [https://air.imag.fr/index.php/RICM4_2017_2018_-_UltraTeamMV UltraTeamMV] project.		This Software Requirements Specification (SRS) identifies the requirements for project [https://air.imag.fr/index.php/RICM4_2017_2018_-_UltraTeamMV UltraTeamMV] project.

	It will present our solution's functionalities and problem solved but also list our system requirements.		It will present our solution's functionalities and problem solved but also list our system requirements.

	==Scope of the product==		==Scope of the product==

2018-02-23T15:13:22Z

Scope of the product

← Older revision		Revision as of 15:13, 23 February 2018
Line 7:		Line 7:

	==Scope of the product==		==Scope of the product==
			This project consists of :
⚫	This project ~~mainly consists of a web application development. This app~~ should allow a hikers team to localise each other in real time.
			* a LoRa and BLE protocol conception a and implementation,
			* a web application development.
		⚫	This project should allow a hikers team to localise each other in real time.

	It should be really easy to add new members (Numeric code, QRCode, NFC, …).		It should be really easy to add new members (Numeric code, QRCode, NFC, …).

	The system should work whether or not there is a 2G/3G/4G or LoRa connection.		The system should work whether or not there is a 2G/3G/4G or LoRa connection.

2018-02-23T15:11:52Z

Product perspective

← Older revision		Revision as of 15:11, 23 February 2018
Line 26:		Line 26:
	==Product perspective==		==Product perspective==
	The product is supposed to be an open source.		The product is supposed to be an open source.

	It is a web based system implementing client-server model. The UltraTeamMV System provides simple mechanism for outdoor geolocation in white & gray network areas.		It is a web based system implementing client-server model. The UltraTeamMV System provides simple mechanism for outdoor geolocation in white & gray network areas.

2018-02-23T15:11:31Z

Product functions

← Older revision		Revision as of 15:11, 23 February 2018
Line 30:		Line 30:
	==Product functions==		==Product functions==
	This system should allow low energy cost localisation.		This system should allow low energy cost localisation.

	It should be decentralized as 2G/3G/4G network is sporadic in such environnement.		It should be decentralized as 2G/3G/4G network is sporadic in such environnement.

	It should also centralize all data to allow sending it to appropriate services (rescue team for instance).		It should also centralize all data to allow sending it to appropriate services (rescue team for instance).

2018-02-23T15:11:16Z

User characteristics

← Older revision		Revision as of 15:11, 23 February 2018
Line 35:		Line 35:
	==User characteristics==		==User characteristics==
	Hikers team, comfortable with using a smartphone but not a technology expert.		Hikers team, comfortable with using a smartphone but not a technology expert.

	No financial criteria other than having a smartphone as an ESP32 costs about 5€.		No financial criteria other than having a smartphone as an ESP32 costs about 5€.

	~~Age~~ group ~~= any~~ that is comfortable with using a smartphone hence (~15-70).		About age group, anyone that is comfortable with using a smartphone (hence ~15-70).

	==General constraints==		==General constraints==

2018-02-23T15:10:23Z

Assumptions and dependencies

← Older revision		Revision as of 15:10, 23 February 2018
Line 45:		Line 45:
	==Assumptions and dependencies==		==Assumptions and dependencies==
	As few environnement assumptions as possible.		As few environnement assumptions as possible.

	A team needs at least 1 smartphone (with GPS connection) and 1 ESP32 per hiker.		A team needs at least 1 smartphone (with GPS connection) and 1 ESP32 per hiker.

2018-02-23T15:10:12Z

General constraints

← Older revision		Revision as of 15:10, 23 February 2018
Line 40:		Line 40:
	==General constraints==		==General constraints==
	The system should work whether or not there is a 2G/3G/4G connection		The system should work whether or not there is a 2G/3G/4G connection

	Limited localisation accuracy : GPS.		Limited localisation accuracy : GPS.

2018-02-23T15:09:36Z

Requirement 10 : Geolocation information retrievement

@@ Line 379: / Line 379: @@
 '''Pre-condition''':
 Smartphone should have a working 3G/4G connection.
 '''Post-condition''':

2018-02-23T14:56:45Z

Requirement 9 : Server information download

@@ Line 337: / Line 337: @@
 # Forge an API request,
 # Send request.
 '''Non functional requirements''':