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

3.1 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.

Function

For the raspberry Pi

- Establish the communication between sensors and the raspberry pi and between the raspberry pi and dysoweb .

- Analyse data from sensor to deduct if someone is inside the room

- Analyse data from dysoweb to know if the room should be taken

- Send the state of te room to dysoweb

For the android's tablet

- Book a room with the tablet

- Establish the communication between dysoweb and the tablet

Description

Inputs

- sensor's data message

- room's calendar

- notification of reservation

Source

-A sensolux presence sensor to send data to raspberry pi via EnOcean radio signal

-A Dysoweb calendar to have the state of the room

-A android's tablet to send notification of reservation to Dysoweb

Outputs

Destination

Action

Non functional requirements

Pre-condition

Post-condition

Side-effects

4. Product evolution

5. Appendices

5.1 Specification

5.2 Sources

5.3 Licensing Requirements

5.4. 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-COQP/SRS

Contents