Proj-2013-2014-BrasRobotique-1/SRS - Revision history

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

2014-04-19T04:53:01Z

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

← Older revision		Revision as of 04:53, 19 April 2014
Line 163:		Line 163:
	==3.1 Requirement X.Y.Z (in Structured Natural Language)==		==3.1 Requirement X.Y.Z (in Structured Natural Language)==

	This diagram below describes how our project works		This diagram below describes how our project works.

			[[File:GlobalArchitecture.png\|400px\|thumb\|center]]

	First, the Client Agent launches the detection with ArUco and gets a marker vector. It applies then a regular expression that allows him to extract the coordinates of		First, the Client Agent launches the detection with ArUco and gets a marker vector. It applies then a regular expression that allows him to extract the coordinates of

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

2014-04-19T04:51:32Z

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

← Older revision		Revision as of 04:51, 19 April 2014
Line 164:		Line 164:

	This diagram below describes how our project works		This diagram below describes how our project works


			First, the Client Agent launches the detection with ArUco and gets a marker vector. It applies then a regular expression that allows him to extract the coordinates of
			marker vector and transform them into XML tags that are successively transmitted to the Agent Server that receives them in order to form the file that will allow him to begin its simulation.

	=== 3.1.1 Markers detection ===		=== 3.1.1 Markers detection ===

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

2014-04-19T04:48:24Z

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

← Older revision		Revision as of 04:48, 19 April 2014
Line 163:		Line 163:
	==3.1 Requirement X.Y.Z (in Structured Natural Language)==		==3.1 Requirement X.Y.Z (in Structured Natural Language)==

			This diagram below describes how our project works

	=== 3.1.1 Markers detection ===		=== 3.1.1 Markers detection ===

RICM4-prj14-grp12: /* 3.1.3 Graphic Simulation */

2014-04-19T04:45:42Z

3.1.3 Graphic Simulation

← Older revision		Revision as of 04:45, 19 April 2014
Line 212:		Line 212:
	=== 3.1.3 Graphic Simulation ===		=== 3.1.3 Graphic Simulation ===

	'''Description''': The XML file is parsed, the marker position is calculted and displayed on a graphic interface		'''Description''': The XML file is parsed and then the marker position is calculted and displayed on a graphic interface

	'''Inputs''': An XML file		'''Inputs''': An XML file
Line 223:		Line 223:

	'''Action''':		'''Action''':
	The Server Agent interprets XML tags and gets back the coordinates of the corresponding point and display it. The point depicting the robot is also displayed		The Server Agent interprets XML tags and gets back the coordinates of the corresponding point and display it. The point depicting the robot is also displayed and can be moved with the keyboard

	'''Non functional requirements''': The version of the XML file must be 1.0.		'''Non functional requirements''': The version of the XML file must be 1.0.

	'''Pre-condition''': The XML file is readable and ~~has~~ no error		'''Pre-condition''': The XML file is readable and contains no error

	'''Post-condition''': The point is displayed on the screen		'''Post-condition''': The point is displayed on the screen with the exact coordinates given in parameter

	'''Side-effects''':		'''Side-effects''': A pop-up window is generated when the robot reachs the marker's position

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

RICM4-prj14-grp12: /* 3.1.2 Coordinates transfer */

2014-04-19T04:42:06Z

3.1.2 Coordinates transfer

← Older revision		Revision as of 04:42, 19 April 2014
Line 189:		Line 189:
	=== 3.1.2 Coordinates transfer ===		=== 3.1.2 Coordinates transfer ===

	'''Description''': Coordinates are extracted in the ~~file~~ and transferred as XML Tags		'''Description''': Coordinates are extracted in the marker vector and transferred as XML Tags

	'''Inputs''': A file		'''Inputs''': A file

	'''Source''': Spade Agents (Client and Server), a platform connexion		'''Source''': Spade Agents (Client and Server), a platform connexion

	'''Outputs''': An XML file		'''Outputs''': An XML file

Line 207:		Line 208:
	'''Post-condition''': All messages have reached their destination in order		'''Post-condition''': All messages have reached their destination in order

	'''Side-effects''':		'''Side-effects''': Acknowledgments are sent by the server

	=== 3.1.3 Graphic Simulation ===		=== 3.1.3 Graphic Simulation ===

RICM4-prj14-grp12: /* 3.1.1 Markers detection */

2014-04-19T04:39:57Z

3.1.1 Markers detection

← Older revision		Revision as of 04:39, 19 April 2014
Line 172:		Line 172:
	'''Source''': ArUco library detection		'''Source''': ArUco library detection

	'''Outputs''': Video stream with markers highlighted with their id and an file which contains the marker's id and the coordinates of the four points of ~~the~~ ~~markers~~		'''Outputs''': Video stream with markers highlighted with their id and an file which contains one of the found marker vector (its id and the coordinates of the four points which is made up of)

	'''Destination''': All people, all object which can be taken by the robot		'''Destination''': All people, all object which can be taken by the robot

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

2014-04-19T04:18:42Z

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

← Older revision		Revision as of 04:18, 19 April 2014
Line 164:		Line 164:


	=== a. Markers detection ===		=== 3.1.1 Markers detection ===

	'''Description''': The camera detects the marker on the object and locates it		'''Description''': The camera detects the marker on the object and locates it
Line 187:		Line 187:
	'''Side-effects''': Failure of the marker recognition		'''Side-effects''': Failure of the marker recognition

	=== b. Coordinates transfer ===		=== 3.1.2 Coordinates transfer ===

	'''Description''': Coordinates are extracted in the file and transferred as XML Tags		'''Description''': Coordinates are extracted in the file and transferred as XML Tags
Line 209:		Line 209:
	'''Side-effects''':		'''Side-effects''':

	=== c. Graphic Simulation ===		=== 3.1.3 Graphic Simulation ===

	'''Description''': The XML file is parsed, the marker position is calculted and displayed on a graphic interface		'''Description''': The XML file is parsed, the marker position is calculted and displayed on a graphic interface

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

2014-04-18T23:10:21Z

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

← Older revision		Revision as of 23:10, 18 April 2014
Line 194:		Line 194:

	'''Source''': Spade Agents (Client and Server), a platform connexion		'''Source''': Spade Agents (Client and Server), a platform connexion

	'''Outputs''': An XML file		'''Outputs''': An XML file

Line 212:		Line 211:
	=== c. Graphic Simulation ===		=== c. Graphic Simulation ===

	'''Description''': The XML file is parsed, the marker position is calculted and ~~display~~ on a graphic interface		'''Description''': The XML file is parsed, the marker position is calculted and displayed on a graphic interface

	'''Inputs''': An XML file		'''Inputs''': An XML file

	'''Source''': ~~Spade~~ ~~Agents (Client~~ and ~~Server), a platform~~ ~~connexion~~		'''Source''': Python xmldom and TKinter librairies

	'''Outputs''': An ~~XML~~ ~~file~~		'''Outputs''': A graphical interface

	'''Destination''': ~~The~~ ~~Agent~~ ~~Server~~		'''Destination''': To the robot and people who used it (as the other group)

	'''Action''':		'''Action''':
	The Agent ~~Client~~ ~~applies~~ a ~~regular~~ ~~expression~~ to ~~extract~~ coordinates ~~into~~ the ~~file~~ and ~~send~~ it to the ~~Server~~		The Server Agent interprets XML tags and gets back the coordinates of the corresponding point and display it. The point depicting the robot is also displayed

	'''Non functional requirements''': The ~~messages~~ ~~have~~ to be ~~delivered quickly and arrive in order. A message~~ must ~~not~~ be ~~lost~~.		'''Non functional requirements''': The version of the XML file must be 1.0.

	'''Pre-condition''': ~~Download,~~ ~~configure~~ ~~and~~ ~~launch~~ ~~SPADE~~ ~~platform connexion (in localhost or in a~~ ~~specific~~ IP ~~adress)~~		'''Pre-condition''': The XML file is readable and has no error

	'''Post-condition''': ~~All~~ ~~messages~~ ~~have~~ ~~reached~~ ~~their~~ ~~destination~~ ~~in order~~		'''Post-condition''': The point is displayed on the screen

	'''Side-effects''':		'''Side-effects''':

RICM4-prj14-grp12: /* b. Coordinates transfer */

2014-04-18T22:44:03Z

b. Coordinates transfer

← Older revision		Revision as of 22:44, 18 April 2014
Line 210:		Line 210:
	'''Side-effects''':		'''Side-effects''':

	=== b. ~~Coordinates~~ ~~transfer~~ ===		=== c. Graphic Simulation ===

	'''Description''': ~~Coordinates~~ ~~are~~ ~~extracted~~ in the ~~file~~ and ~~transferred~~ as ~~XML~~ ~~Tags~~		'''Description''': The XML file is parsed, the marker position is calculted and display on a graphic interface

	'''Inputs''': A ~~file~~		'''Inputs''': An XML file

	'''Source''': Spade Agents (Client and Server), a platform connexion		'''Source''': Spade Agents (Client and Server), a platform connexion

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

2014-04-18T22:33:55Z

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

← Older revision		Revision as of 22:33, 18 April 2014
Line 186:		Line 186:

	'''Side-effects''': Failure of the marker recognition		'''Side-effects''': Failure of the marker recognition

			=== b. Coordinates transfer ===

			'''Description''': Coordinates are extracted in the file and transferred as XML Tags

			'''Inputs''': A file

			'''Source''': Spade Agents (Client and Server), a platform connexion

			'''Outputs''': An XML file

			'''Destination''': The Agent Server

			'''Action''':
			The Agent Client applies a regular expression to extract coordinates into the file and send it to the Server

			'''Non functional requirements''': The messages have to be delivered quickly and arrive in order. A message must not be lost.

			'''Pre-condition''': Download, configure and launch SPADE platform connexion (in localhost or in a specific IP adress)

			'''Post-condition''': All messages have reached their destination in order

			'''Side-effects''':

	=== b. Coordinates transfer ===		=== b. Coordinates transfer ===