Difference between revisions of "Proj-2013-2014-RobAIR-1-SRS"

From air
Jump to navigation Jump to search
(Created page with "=1. Introduction= ==1.1 Purpose of the requirements document== ==1.2 Scope of the product== ==1.3 Definitions, acronyms and abbreviations== ==1.4 References== ==1.5 ...")
 
Line 19: Line 19:
   
 
==3.1 Requirement X.Y.Z (in Structured Natural Language)==
 
==3.1 Requirement X.Y.Z (in Structured Natural Language)==
  +
  +
Requirement : skype must be installed, internet connection for us application and robair, battery charged, access to steering commands the robot,
  +
 
'''Function''': receive video trafic, put it on us interface and add directional buttun for control robair remotely via skype encoding (for VoIP)
 
'''Function''': receive video trafic, put it on us interface and add directional buttun for control robair remotely via skype encoding (for VoIP)
   

Revision as of 13:29, 27 January 2014

1. Introduction

1.1 Purpose of the requirements document

1.2 Scope of the product

1.3 Definitions, acronyms and abbreviations

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)

Requirement : skype must be installed, internet connection for us application and robair, battery charged, access to steering commands the robot,

Function: receive video trafic, put it on us interface and add directional buttun for control robair remotely via skype encoding (for VoIP)

Description: use skype interface for video-conference to allow us to control robair

Inputs: webcam

Source: directional button, webcam, skype

Outputs: webcam

Destination: robair

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: skype must be used in the server and client

Post-condition:

Side-effects: latency? used a new interface and not skype interface

4. Product evolution

5. Appendices

5.1. SRS structure

The document is based on template of the Software Requirements Specification (SRS) inspired of the IEEE/ANSI 830-1998 Standard.

References:

6. Index