RobAIR2013-RICM4-Groupe3-SRS: Difference between revisions
Jump to navigation
Jump to search
Thomas.Nunes (talk | contribs) |
Thomas.Nunes (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
{|class="wikitable alternance" |
{|class="wikitable alternance" |
||
|+ Document History |
|+ Document History |
||
| Line 13: | Line 12: | ||
!scope="row" | |
!scope="row" | |
||
| 0.1.0 |
| 0.1.0 |
||
| 28/02/2013 |
|||
| N.Thomas |
|||
| First Version |
|||
| TBC |
| TBC |
||
| TBC |
| TBC |
||
|- |
|||
!scope="row" | |
|||
| 0.1.1 |
|||
| 28/02/2013 |
|||
| N.Thomas |
|||
| Description & abreviation |
|||
| TBC |
| TBC |
||
| TBC |
| TBC |
||
| TBC |
|||
|} |
|} |
||
Revision as of 09:45, 28 January 2013
| Version | Date | Authors | Description | Validator | Validation Date | |
|---|---|---|---|---|---|---|
| 0.1.0 | 28/02/2013 | N.Thomas | First Version | TBC | TBC | |
| 0.1.1 | 28/02/2013 | N.Thomas | Description & abreviation | TBC | TBC |
1. Introduction
1.1 Purpose of the requirements document
1.2 Scope of the product
1.3 Definitions, acronyms and abbreviations
- XML: (Extensible Markup Language) is a markup language that defines a set of rules for encoding documents in a format that is both human-readable and machine-readable.
- XMPP: (Extensible Messaging and Presence Protocol) is a communications protocol for message-oriented middleware.
- Jingle: Jingle is an extension to (XMPP) which adds peer-to-peer (P2P) session control for multimedia interactions like videoconferencing communication.
- ROS: (Robot Operating System) It is a software framework for robot software development.
- Jitsi: is a VoIP, videoconferencing and instant messaging application devlopped in JAVA and using XMPP/Jingle.
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: