Proj-2013-2014-RobAIR-1-SRS - Revision history

RICM4-prj14-grp2: /* 1.4 References */

2014-04-08T12:54:36Z

1.4 References

← Older revision		Revision as of 12:54, 8 April 2014
Line 20:		Line 20:
	:- [[RobAIR2013-RICM4-Groupe2-Suivi \| Group 2]]		:- [[RobAIR2013-RICM4-Groupe2-Suivi \| Group 2]]
	:- [[RobAIR2013-RICM4-Groupe3-Suivi \| Group 3]]		:- [[RobAIR2013-RICM4-Groupe3-Suivi \| Group 3]]
	* The other group who work on robair : [[http://air.imag.fr/index.php/Proj-2013-2014-RobAIR-2\|here]]
	* official website[http://www.webrtc.org/ webrtc.org]		* official website[http://www.webrtc.org/ webrtc.org]
	* all old projects already done on [http://air.imag.fr/index.php/RobAIR RobAIR]		* all old projects already done on [http://air.imag.fr/index.php/RobAIR RobAIR]

RICM4-prj14-grp2: /* 4. Product evolution */

2014-04-08T12:54:21Z

4. Product evolution

← Older revision		Revision as of 12:54, 8 April 2014
Line 116:		Line 116:

	=4. Product evolution=		=4. Product evolution=
	::- add other project like '''~~QOS~~''' to selected whitch ROBAIR you want.		::- add other project like '''COQP''' to selected whitch ROBAIR you want.
	::- Switch between different robots.		::- Switch between different robots.
	::- Control the robot thanks to a neuronal device.		::- Control the robot thanks to a neuronal device.

RICM4-prj14-grp2: /* 4. Product evolution */

2014-04-04T16:29:57Z

4. Product evolution

← Older revision		Revision as of 16:29, 4 April 2014
Line 116:		Line 116:

	=4. Product evolution=		=4. Product evolution=
			::- add other project like '''QOS''' to selected whitch ROBAIR you want.
			::- Switch between different robots.
			::- Control the robot thanks to a neuronal device.
			::- Thanks to a lidar, the robot makes its own map. (in progress...)
			::- Ability to read QRcodes and display related contents on the tablet.
			::- able to do as we want talk and not with previously saved text

	=5. Appendices=		=5. Appendices=

RICM4-prj14-grp2: /* 1.4 References */

2014-04-04T16:25:44Z

1.4 References

← Older revision		Revision as of 16:25, 4 April 2014
Line 20:		Line 20:
	:- [[RobAIR2013-RICM4-Groupe2-Suivi \| Group 2]]		:- [[RobAIR2013-RICM4-Groupe2-Suivi \| Group 2]]
	:- [[RobAIR2013-RICM4-Groupe3-Suivi \| Group 3]]		:- [[RobAIR2013-RICM4-Groupe3-Suivi \| Group 3]]
	* The other group who work on robair :		* The other group who work on robair : [[http://air.imag.fr/index.php/Proj-2013-2014-RobAIR-2\|here]]
	* official website[http://www.webrtc.org/ webrtc.org]		* official website[http://www.webrtc.org/ webrtc.org]
	* all old projects already done on [http://air.imag.fr/index.php/RobAIR RobAIR]		* all old projects already done on [http://air.imag.fr/index.php/RobAIR RobAIR]

RICM4-prj14-grp2 at 16:22, 4 April 2014

2014-04-04T16:22:48Z

← Older revision		Revision as of 16:22, 4 April 2014
Line 15:		Line 15:

	==1.4 References==		==1.4 References==
			* The global project's page can be found [[RobAIR2014\|here]].
			* The last RICM4 groups are working on this project. Here are their wiki page:
			:- [[RobAIR2013-RICM4-Groupe1-Suivi \| Group 1]]
			:- [[RobAIR2013-RICM4-Groupe2-Suivi \| Group 2]]
			:- [[RobAIR2013-RICM4-Groupe3-Suivi \| Group 3]]
			* The other group who work on robair :
	* official website[http://www.webrtc.org/ webrtc.org]		* official website[http://www.webrtc.org/ webrtc.org]
	* all old projects already done on [http://air.imag.fr/index.php/RobAIR RobAIR]		* all old projects already done on [http://air.imag.fr/index.php/RobAIR RobAIR]
	* the second group work on robair [http://air.imag.fr/index.php/Proj-2013-2014-RobAIR-2 Proj-2013-2014-RobAIR-]		* the second group work on robair [http://air.imag.fr/index.php/Proj-2013-2014-RobAIR-2 Proj-2013-2014-RobAIR-]
	* so much git on webrtc. The most importante are : - [https://developer.mozilla.org/fr/docs/WebRTC developer.mozilla.org] <br>
	::- [http://www.html5rocks.com/en/tutorials/webrtc/basics/ www.html5rocks.com] <br>
	::- [http://www.w3.org/TR/2013/WD-webrtc-20130910/ www.w3.org] (official documentation)<br>
	::- [http://www.simpl.info/index.html www.simpl.info] <br>

	==1.5 Overview of the remainder of the document==		==1.5 Overview of the remainder of the document==
Line 132:		Line 134:
	::- [http://www.simpl.info/index.html www.simpl.info] <br>		::- [http://www.simpl.info/index.html www.simpl.info] <br>

			==5.3 Licensing Requirements==
	=6. Index=
			RobAIR will be released under a GPL license and will be open-source.

RICM4-prj14-grp2: /* 5. Appendices */

2014-04-04T16:21:10Z

5. Appendices

← Older revision		Revision as of 16:21, 4 April 2014
Line 124:		Line 124:
	* http://en.wikipedia.org/wiki/Software_requirements_specification		* http://en.wikipedia.org/wiki/Software_requirements_specification
	* [http://www.cse.msu.edu/~chengb/RE-491/Papers/IEEE-SRS-practice.pdf IEEE Recommended Practice for Software Requirements Specifications IEEE Std 830-1998]		* [http://www.cse.msu.edu/~chengb/RE-491/Papers/IEEE-SRS-practice.pdf IEEE Recommended Practice for Software Requirements Specifications IEEE Std 830-1998]

			==5.2 Sources==
			::- The other groups who work on ROBAIR :
			::- [https://developer.mozilla.org/fr/docs/WebRTC developer.mozilla.org] <br>
			::- [http://www.html5rocks.com/en/tutorials/webrtc/basics/ www.html5rocks.com] <br>
			::- [http://www.w3.org/TR/2013/WD-webrtc-20130910/ www.w3.org] (official documentation)<br>
			::- [http://www.simpl.info/index.html www.simpl.info] <br>

	=6. Index=		=6. Index=

RICM4-prj14-grp2: /* 3.1 Requirement X.Y.Z (in Structured Natural Language) */

2014-04-04T16:14:30Z

3.1 Requirement X.Y.Z (in Structured Natural Language)

← Older revision		Revision as of 16:14, 4 April 2014
Line 68:		Line 68:
	==3.1 Requirement X.Y.Z (in Structured Natural Language)==		==3.1 Requirement X.Y.Z (in Structured Natural Language)==

	Requirement : ~~skype~~ must be installed, internet connection between us application and robair, battery charged, access to steering commands the robot, all requirements of last years projects, ROS is used only on Linux systems		Requirement : chrome/mozilla browser must be installed, internet connection between our application and robair, battery charged, access to steering commands the robot, all requirements of last years projects, ROS is used only on Linux systems.

	'''Function''': receive video trafic, put it on us interface and add directional buttun for control robair remotely via ~~skype~~ encoding ~~(for VoIP)~~		'''Function''': receive video trafic, put it on our interface and add directional buttun for control robair remotely via webRTC encoding

	'''Description''': use ~~skype~~ interface for video-conference to allow us to control robair		'''Description''': use browser interface for video-conference to allow us to control robair

	'''Inputs''': webcam, ~~press~~ ~~buttun~~		'''Inputs''': webcam, directionnal buttons, voice buttons, create and join channel.

	'''Source''': directional button, webcam, ~~skype~~		'''Source''': directional button, webcam, webrtc

	'''Outputs''': webcam, directions information		'''Outputs''': webcam, directions information, voices information

	'''Destination''': robair for the direction, robair and us application for the video		'''Destination''': robair for the direction, robair and us application for the video

	'''Action''':		'''Action''':
			* Etablished connection between many user
	* Natural language sentences (with MUST, MAY, SHALL)
			* Send/receive video stream
	* Graphical Notations : UML Sequence w/o collaboration diagrams, Process maps, Task Analysis (HTA, CTT)
			* Controle ROBAIR with our interface
	* Mathematical Notations
			* Send data (text, sound, directionnal command)
	* Tabular notations for several (condition --> action) tuples

	'''Non functional requirements''':		'''Non functional requirements''':
			::- beautiful HMI.
			::- We can't restart video after shut down the stream.
			::- we can't redirect the video stream to a other device.
			::- All users have the directionnal buttons in their interface. We want only one (in progress...)

	'''Pre-condition''':		'''Pre-condition''':
	*materials conditions:		*materials conditions:
	::- A RobAIR ~~2013~~ connected in the selected place.		::- A RobAIR must be connected in the selected place.
	::- A ~~ubuntu~~ server ~~connected~~ to ~~a display device~~ ~~and~~ a ~~camera~~.		::- A server to log our website connection.
			::- A equipments with chrome or mozilla browsers.
	::- A android/windows/Linux tablet.

	*Software conditions:		*Software conditions:
	::- Install the ~~RobAIR2013~~-Server software on the ubuntu server.		::- Install the RobAIR2014-Server software on the ubuntu server on ROBAIR.
			::- Just need lastest chrome/mozilla version.
	::- Install the RobAIR2013 android application.
	::- skype must be used in the server and client.

	'''Post-condition''':		'''Post-condition''':
	::- The user can do videoconferencing with people who met the robot.		::- The user can do videoconferencing with people who met the robot.
	::- The user can control the robot by us interface		::- The user can control the robot by us interface.
			::- The user can send voices data to robair speak.

	'''Side-effects''': ~~latency? used a new interface and not skype interface~~		'''Side-effects''':
			::- bit latency of the stream (in general the quality is nice).
			::- sometimes we have a fail of connection, just restart the connection and all will be functional.

	=4. Product evolution=		=4. Product evolution=

RICM4-prj14-grp2: /* 2. General description */

2014-04-04T15:53:08Z

2. General description

← Older revision		Revision as of 15:53, 4 April 2014
Line 32:		Line 32:

	==2.2 Product functions==		==2.2 Product functions==
	[[File:connection.png\|400px\|It's was how webRTC connection works]]<br/>		[[File:connection.png\|400px]]\|It's was how webRTC connection works<br/>
	If a user want to join ROBAIR, he will click on "JoinRobair" button. If he want to shut down his stream video, he will click on "stop Video Stream" button.		If a user want to join ROBAIR, he will click on "JoinRobair" button. If he want to shut down his stream video, he will click on "stop Video Stream" button.
	We need a ROS node to convert webrtc instructions to ROS.		We need a ROS node to convert webrtc instructions to ROS.
Line 54:		Line 54:

	==2.5 Assumptions and dependencies==		==2.5 Assumptions and dependencies==
			::- The robot site has wifi access in all the visit area.
			::- The robot base can be accessed at any time.
			::- The robot can be connected with many users
			::- The robot can be control by one user.

	=3.Specific requirements, covering functional, non-functional and interface requirements=		=3.Specific requirements, covering functional, non-functional and interface requirements=

RICM4-prj14-grp2: /* 2.2 Product functions */

2014-04-04T15:50:01Z

2.2 Product functions

← Older revision		Revision as of 15:50, 4 April 2014
Line 32:		Line 32:

	==2.2 Product functions==		==2.2 Product functions==
	[[File:connection.png\|400px]]		[[File:connection.png\|400px\|It's was how webRTC connection works]]<br/>
	If a user want to join ROBAIR, he will click on "JoinRobair" button. If he want to shut down his stream video, he will click on "stop Video Stream" button.		If a user want to join ROBAIR, he will click on "JoinRobair" button. If he want to shut down his stream video, he will click on "stop Video Stream" button.
	We need a ROS node to convert webrtc instructions to ROS.		We need a ROS node to convert webrtc instructions to ROS.

RICM4-prj14-grp2: /* 2.2 Product functions */

2014-04-04T15:46:22Z

2.2 Product functions

← Older revision		Revision as of 15:46, 4 April 2014
Line 32:		Line 32:

	==2.2 Product functions==		==2.2 Product functions==
	[[File:connection.png]]		[[File:connection.png\|400px]]
	If a user want to join ROBAIR, he will click on "JoinRobair" button. If he want to shut down his stream video, he will click on "stop Video Stream" button.		If a user want to join ROBAIR, he will click on "JoinRobair" button. If he want to shut down his stream video, he will click on "stop Video Stream" button.
	We need a ROS node to convert webrtc instructions to ROS.		We need a ROS node to convert webrtc instructions to ROS.