SRS RobAir RICM Group

This document describe the software requirements specifications of the project RobAIR2013.

Document History

	Version	Date	Authors	Description	Validator	Validation Date
	0.1.0	January 27th, 2013	Laurène Guelorget	First draft	TBC	TBC
	1.1.0	January 29th, 2013	Morgan bidois	First draft	January 29th, 2013	Thomas Nunes
	1.2.0	January 31th, 2013	Morgan bidois	Definitions 1.3 & some reference 1.4	January 1st, 2013	Thomas Nunes
	1.3.0	January 1st, 2013	Thomas Nunes	General description 2.1 to 2.5	January 4th, 2013	Morgan bidois
	1.3.0	January 4th, 2013	Morgan bidois	Evolution 4 & specific requieremnt 3	January 4th, 2013	Thomas Nunes
	0.1.1	February 7th, 2013	Laurène Guelorget	Scope	TBC	TBC
	1.4.0	January 7th, 2013	Thomas Nunes	3.1 requierement	January 7th, 2013	Morgan bidois
	1.5.0	January 8th, 2013	Morgan bidois	appendices 5 & complete part 2	January 8th, 2013	Thomas Nunes
	2.0.0	January 11th, 2013	Thomas Nunes	Merge of two SRS for a group of 6.	TBC	TBC

1. Introduction

1.1 Purpose of the requirements document

This Software Requirements Specification (SRS) identifies the requirements for the robot RobAIR.

1.2 Scope of the product

• The product we are developing is a telepresence robot that can be used for museum tours and the user will be able to guide the robot with an Android tablet.
• It is a low cost robot (well below the maket price).
• The platform and software used for this robot are extensible and open-source.

1.3 Definitions, acronyms and abbreviations

• ROS: Robot Operating System is an open-source software framework for robot software development.
• Roaming: It ensures that a wireless device is kept connected to the network, without losing the connection.
• ... (à compléter)

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

• document external interfaces,
• describe system functionality and performance
• specify logical database requirements,
• design constraints,
• emergent system properties and quality characteristics.

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

Function:

Description:

Inputs:

Source:

Outputs:

Destination:

Action:

• 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:

Pre-condition:

Post-condition:

Side-effects: