Difference between revisions of "RobAIR2013-RICM4-Groupe3-SRS"
Jump to navigation
Jump to search
Thomas.Nunes (talk | contribs) |
Thomas.Nunes (talk | contribs) (Blanked the page) |
||
(29 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
− | |||
− | {|class="wikitable alternance" |
||
− | |+ Document History |
||
− | |- |
||
− | | |
||
− | !scope="col"| Version |
||
− | !scope="col"| Date |
||
− | !scope="col"| Authors |
||
− | !scope="col"| Description |
||
− | !scope="col"| Validator |
||
− | !scope="col"| Validation Date |
||
− | |- |
||
− | !scope="row" | |
||
− | | 0.1.0 |
||
− | | TBC |
||
− | | TBC |
||
− | | TBC |
||
− | | 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''': |
||
− | |||
− | =4. Product evolution= |
||
− | |||
− | =5. Appendices= |
||
− | =6. Index= |