Difference between revisions of "SRS RobAir RICM Group"
Jump to navigation
Jump to search
(Created page with " {|class="wikitable alternance" |+ Document History |- | !scope="col"| Version !scope="col"| Date !scope="col"| Authors !scope="col"| Description !scope="col"| Validator …") |
|||
Line 12: | Line 12: | ||
!scope="row" | |
!scope="row" | |
||
| 0.1.0 |
| 0.1.0 |
||
+ | | January 27th, 2013 |
||
− | | TBC |
||
+ | | [[User:Laurene.Guelorget|Laurène Guelorget]] |
||
− | | TBC |
||
− | | |
+ | | First draft |
| TBC |
| TBC |
||
| TBC |
| TBC |
Revision as of 16:49, 27 January 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
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: