Proj-2013-2014-COQP/SRS

=1.  Introduction=

1.5 Overview of the remainder of the document
=2.  General description=

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

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

Side-effects
=4. Product evolution= =5. Appendices=

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: =6. Index=
 * http://www.cs.st-andrews.ac.uk/~ifs/Books/SE9/Presentations/PPTX/Ch4.pptx
 * http://en.wikipedia.org/wiki/Software_requirements_specification
 * IEEE Recommended Practice for Software Requirements Specifications IEEE Std 830-1998