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

Read first:

Document History
	Version	Date	Authors	Description	Validator	Validation Date
	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

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: guide people

Description: The main goal of this projetc is to develop a brand new feature allowing us to locate ourselves.

Inputs: tablet, software, and proximity sensors

Source: tablet, wencam, STM32

Outputs: tablet, software

Destination: RobAIR control system

Action:

RobAIR must be able to guide people within the building (IMAG).
It must be able to communicate with people by showing them the path to be taken and clearly explaining what it is doing.
RobAIR must be able to move around autonomously and figure its path out
Avoid obstacles.

Non functional requirements:

WebRTC
Ros
Arduino
Web server
Custumed power supply unit
Low cost

Pre-condition: functional RobAIR

Post-condition: People reach their destination

Side-effects:

Bad guidance
Collisions

RICM4 2017 2018 - RobAIRDL/ SRS

Contents