Difference between revisions of "Proj-2013-2014-SmartCitizen2014/SRS"
Jump to navigation
Jump to search
| Line 53: | Line 53: | ||
* Json data from Twitter |
* Json data from Twitter |
||
* MQTT data from sensors |
* MQTT data from sensors |
||
| + | * XML + picture from Android Application |
||
'''Source''': |
'''Source''': |
||
* Twitter stream |
* Twitter stream |
||
* Sensors |
* Sensors |
||
| + | * Android application |
||
'''Outputs''': |
'''Outputs''': |
||
| Line 66: | Line 68: | ||
'''Action''': |
'''Action''': |
||
| + | * Alert by e-mail to Town hall when a threshol is reached |
||
| − | * Store information from sensors and Twitter into a database |
||
| + | * Post a tweet when a threshol is reached |
||
'''Non functional requirements''': |
'''Non functional requirements''': |
||
| + | * Sensors are not blocked |
||
'''Pre-condition''': |
'''Pre-condition''': |
||
| Line 87: | Line 91: | ||
'''Side-effects''': |
'''Side-effects''': |
||
| + | * Real time information |
||
| + | * Reactivity from the Town hall |
||
| + | * |
||
=4. Product evolution= |
=4. Product evolution= |
||
Revision as of 13:48, 27 January 2014
The document provides a template of the Software Requirements Specification (SRS). It is inspired of the IEEE/ANSI 830-1998 Standard.
| 0.1 | 27/01/2014 | Labat Paul, Fréby Rodolphe | SRS of SmartCitizen project | 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:
- Gather information from several sensors and a Twitter steam
- Post information on a map, available from a browser
Description:
Inputs:
- Json data from Twitter
- MQTT data from sensors
- XML + picture from Android Application
Source:
- Twitter stream
- Sensors
- Android application
Outputs:
- A web site
Destination:
- Citizen
- Town hall
Action:
- Alert by e-mail to Town hall when a threshol is reached
- Post a tweet when a threshol is reached
Non functional requirements:
- Sensors are not blocked
Pre-condition:
- Hardware:
- - Intel Galileo
- - Senors with MQTT compatibility
- Software:
- - Nodejs
- - Red-node
- - Mongodb
- - Mosquitto
Post-condition:
Side-effects:
- Real time information
- Reactivity from the Town hall