Proj-2013-2014-BrasRobot-Handicap-2/SRS - Revision history

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

2014-04-18T20:59:03Z

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

← Older revision		Revision as of 20:59, 18 April 2014
Line 107:		Line 107:

	'''Non functional requirements''':		'''Non functional requirements''':


	'''Pre-condition''':		'''Pre-condition''':

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

2014-04-18T20:58:51Z

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

← Older revision		Revision as of 20:58, 18 April 2014
Line 105:		Line 105:

	The simulated robot take the object and bring it to a place		The simulated robot take the object and bring it to a place


	'''Non functional requirements''':		'''Non functional requirements''':

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

2014-04-18T20:57:27Z

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

← Older revision		Revision as of 20:57, 18 April 2014
Line 100:		Line 100:

	'''Action''':		'''Action''':

	The simulated robot follows a path to find the marker		The simulated robot follows a path to find the marker

	The detection program of the other groups give the displacement of the camera by sending data in sockets		The detection program of the other groups give the displacement of the camera by sending data in sockets

	The simulated robot take the object and bring it to a place		The simulated robot take the object and bring it to a place

RICM4-prj14-grp12: /* a. Markers detection */

2014-04-18T20:56:55Z

a. Markers detection

← Older revision		Revision as of 20:56, 18 April 2014
Line 80:		Line 80:

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

	== a. Markers detection ==

	'''Description''': The camera detect the marker on the object and locate it

	'''Inputs''': Video stream and markers

	'''Source''': ArUco library detection

	'''Outputs''': video stream with markers highlighted with their id and an xml file which contains the marker's id and the coordinates of the four points of the markers

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

	'''Action''':
	The ArUco library detects borders and analyzes in rectangular regions which may be markers. When a

	'''Non functional requirements''': The marker detection should be done in real time and faster

	'''Pre-condition''': have a camera and ArUco library installed

	'''Post-condition''': The marker has to be well recognized.

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


	'''Function''':		'''Function''':
	Help the camera to detect the marker on the object, localise the object on the simulator relative to the robotic arm base, take it and bring it back		Help the camera to detect the marker on the object, localise the object on the simulator relative to the robotic arm base, take it and bring it back

	'''Description''':		'''Description''':
	Implement a simulator to move the robotic clamp in spacial coordinates		Implement a simulator to move the robotic clamp in spacial coordinates

	'''Inputs''':		'''Inputs''':
	Webcam, marker on the object, a users which can move all the robotic arm to make the object reachable		Webcam, marker on the object, a users which can move all the robotic arm to make the object reachable

	'''Source''':		'''Source''':

	'''Outputs''':		'''Outputs''':
	A persons with arm disabilities can take an object		A persons with arm disabilities can take an object

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

	'''Action''':		'''Action''':

RICM4-prj14-grp12: /* b. Markers detection */

2014-04-18T20:55:59Z

b. Markers detection

← Older revision		Revision as of 20:55, 18 April 2014
Line 105:		Line 105:


		⚫	'''Function''':
	== b. Markers detection ==
			Help the camera to detect the marker on the object, localise the object on the simulator relative to the robotic arm base, take it and bring it back
			'''Description''':
			Implement a simulator to move the robotic clamp in spacial coordinates
			'''Inputs''':
			Webcam, marker on the object, a users which can move all the robotic arm to make the object reachable
			'''Source''':

			'''Outputs''':
	'''Description''': The camera detect the marker on the object and locate it
			A persons with arm disabilities can take an object
			'''Destination''':
		⚫	All people, all object which can be taken by the robot (dimension)
			'''Action''':

			The simulated robot follows a path to find the marker
	'''Inputs''': Video stream and markers
			The detection program of the other groups give the displacement of the camera by sending data in sockets
			The simulated robot take the object and bring it to a place

	'''Source''': ArUco library detection

			'''Non functional requirements''':
	'''Outputs''': video stream with markers highlighted with their id and an xml file which contains the marker's id and the coordinates of the four points of the markers

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

⚫	'''~~Action~~''':
	The ArUco library detects borders and analyzes in rectangular regions which may be markers. When a

	'''Non functional requirements''': The marker detection should be done in real time and faster

	'''Pre-condition''': ~~have a camera and ArUco library installed~~		'''Pre-condition''':

	'''Post-condition''': ~~The marker has to be well recognized.~~		'''Post-condition''':

	'''Side-effects''': ~~failure of the marker recognition~~		'''Side-effects''':

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

RICM4-prj14-grp12: /* a. Markers detection */

2014-04-18T20:51:10Z

a. Markers detection

← Older revision		Revision as of 20:51, 18 April 2014
Line 82:		Line 82:

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

			'''Description''': The camera detect the marker on the object and locate it

			'''Inputs''': Video stream and markers

			'''Source''': ArUco library detection

			'''Outputs''': video stream with markers highlighted with their id and an xml file which contains the marker's id and the coordinates of the four points of the markers

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

			'''Action''':
			The ArUco library detects borders and analyzes in rectangular regions which may be markers. When a

			'''Non functional requirements''': The marker detection should be done in real time and faster

			'''Pre-condition''': have a camera and ArUco library installed

			'''Post-condition''': The marker has to be well recognized.

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


			== b. Markers detection ==

	'''Description''': The camera detect the marker on the object and locate it		'''Description''': The camera detect the marker on the object and locate it

RICM4-prj14-grp12: /* a. Markers detection */

2014-04-18T20:48:11Z

a. Markers detection

← Older revision		Revision as of 20:48, 18 April 2014
Line 94:		Line 94:

	'''Action''':		'''Action''':
	The ArUco library detects borders and analyzes in rectangular regions which may be markers		The ArUco library detects borders and analyzes in rectangular regions which may be markers. When a

	'''Non functional requirements''': The marker detection should be done in real time and faster		'''Non functional requirements''': The marker detection should be done in real time and faster

	'''Pre-condition''': ~~Using~~ ~~the~~ ~~Creative~~ ~~Camera,~~ ~~ambient~~ ~~light~~ ~~should be enough to see correctly user´s movements.~~		'''Pre-condition''': have a camera and ArUco library installed
	Using the leap motion, hands should be above the sensor.
	The recognized gesture is present in the data base.

	'''Post-condition''': The ~~user~~ ~~hand~~ ~~movement has~~ ~~been~~ well recognized.		'''Post-condition''': The marker has to be well recognized.

	'''Side-effects''': ~~Bad~~ ~~gesture~~ recognition		'''Side-effects''': failure of the marker recognition

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

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

2014-04-18T20:23:47Z

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

@@ Line 80: / Line 80: @@
 ==3.1 Requirement X.Y.Z (in Structured Natural Language)==
-'''Post-condition''':
+'''Post-condition''': The user hand movement has been well recognized.
-'''Side-effects''':
+'''Side-effects''': Bad gesture recognition
 =4. Product evolution=

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

2014-04-11T13:03:36Z

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

← Older revision		Revision as of 13:03, 11 April 2014
Line 98:		Line 98:
	The simulated robot take the object and bring it to a place		The simulated robot take the object and bring it to a place




	* Natural language sentences (with MUST, MAY, SHALL)
	* Graphical Notations : UML Sequence w/o collaboration diagrams, Process maps, Task Analysis (HTA, CTT)
	* Mathematical Notations
	* Tabular notations for several (condition --> action) tuples

	'''Non functional requirements''':		'''Non functional requirements''':

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

2014-04-11T13:02:02Z

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

← Older revision		Revision as of 13:02, 11 April 2014
Line 81:		Line 81:
	==3.1 Requirement X.Y.Z (in Structured Natural Language)==		==3.1 Requirement X.Y.Z (in Structured Natural Language)==
	'''Function''':		'''Function''':
			Help the camera to detect the marker on the object, localise the object on the simulator relative to the robotic arm base, take it and bring it back

	'''Description''':		'''Description''':
			Implement a simulator to move the robotic clamp in spacial coordinates

	'''Inputs''':		'''Inputs''':
			Webcam, marker on the object, a users which can move all the robotic arm to make the object reachable

	'''Source''':		'''Source''':

	'''Outputs''':		'''Outputs''':
			A persons with arm disabilities can take an object

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

	'''Action''':		'''Action''':

			The simulated robot follows a path to find the marker
			The detection program of the other groups give the displacement of the camera by sending data in sockets
			The simulated robot take the object and bring it to a place




	* Natural language sentences (with MUST, MAY, SHALL)		* Natural language sentences (with MUST, MAY, SHALL)
	* Graphical Notations : UML Sequence w/o collaboration diagrams, Process maps, Task Analysis (HTA, CTT)		* Graphical Notations : UML Sequence w/o collaboration diagrams, Process maps, Task Analysis (HTA, CTT)
Line 99:		Line 107:

	'''Non functional requirements''':		'''Non functional requirements''':


	'''Pre-condition''':		'''Pre-condition''':