Difference between revisions of "SRS RobAir RICM Group"
Jump to navigation
Jump to search
Line 25: | Line 25: | ||
This Software Requirements Specification (SRS) identifies the requirements for the robot [[RobAIR2013 | RobAIR]]. |
This Software Requirements Specification (SRS) identifies the requirements for the robot [[RobAIR2013 | RobAIR]]. |
||
==1.2 Scope of the product== |
==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== |
==1.3 Definitions, acronyms and abbreviations== |
||
* [[Robot_Operating_System|ROS]]: Robot Operating System is an open-source software framework for robot software development. |
* [[Robot_Operating_System|ROS]]: Robot Operating System is an open-source software framework for robot software development. |
Revision as of 20:00, 7 February 2013
Version | Date | Authors | Description | Validator | Validation Date | |
---|---|---|---|---|---|---|
0.1.0 | January 27th, 2013 | Laurène Guelorget | First draft | 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)
1.4 References
1.5 Overview of the remainder of the document
2. General description
2.1 Product perspective
2.2 Product functions
2.3 User characteristics
2.4 General constraints
2.5 Assumptions and dependencies
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: