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 between us application and robair, battery charged, access to steering commands the robot, all requirements of last years projects, ROS is used only on Linux systems

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, press buttun

Source: directional button, webcam, skype

Outputs: webcam, directions information

Destination: robair for the direction, robair and us application for the video

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:

materials conditions:

- A RobAIR 2013 connected in the selected place.

- A ubuntu server connected to a display device and a camera.

- A android tablet.

Software conditions:

- Install the RobAIR2013-Server software on the ubuntu server.

- Install the RobAIR2013 android application.

- skype must be used in the server and client.

Post-condition:

- The user can do videoconferencing with people who met the robot.

- The user can control the robot by us interface

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:

Proj-2013-2014-RobAIR-1-SRS

Contents