Difference between revisions of "Tachymètre"

From air
Jump to navigation Jump to search
 
(12 intermediate revisions by 2 users not shown)
Line 1: Line 1:
  +
=Objective of the project=
The document provides a template of the Software Requirements Specification (SRS). It is inspired of the IEEE/ANSI 830-1998 Standard.
 
  +
The aim of the project is to use a doppler sensor to develop a web application that displays the historic of all passages in front of the sensor, with date, hour, speed, and direction. The sensor is connected to a Raspberry Pi with an Arduino to process the raw data and send the measures to a SQLite server. The server stores all the values and makes them available to the web client. This client is a user interface that allows the owner of the sensor to see the historic of passages in a legibly and interactive way (date range, graphs).
   
  +
This application has to be developped with Cohorte, a service oriented platform that allows to split the application in different independant components. These components can be coded in different programming languages, and the communication between them is entirely managed by Cohorte. The application consists in the interaction between the components that provides and use services.
   
  +
= Technical environment =
'''Read first:'''
 
  +
* Cohorte
* http://www.cs.st-andrews.ac.uk/~ifs/Books/SE9/Presentations/PPTX/Ch4.pptx
 
  +
* Raspberry Pi
* http://en.wikipedia.org/wiki/Software_requirements_specification
 
  +
* Arduino
* [http://www.cse.msu.edu/~chengb/RE-491/Papers/IEEE-SRS-practice.pdf IEEE Recommended Practice for Software Requirements Specifications IEEE Std 830-1998]
 
  +
* [[HB100 Doppler Sensor]]
 
'''Cohorte'''
 
* cohorte.github.io
 
 
'''Microwave Motion Sensor'''
 
* https://www.openimpulse.com/blog/wp-content/uploads/wpsc/downloadables/HB100_Microwave_Sensor_Module_Datasheet.pdf
 
* https://www.openimpulse.com/blog/wp-content/uploads/wpsc/downloadables/HB100_Microwave_Sensor_Application_Note.pdf
 
 
'''Making the electronics for $7 USD doppler motion sensor'''
 
* http://ch.linkedin.com/in/mathieustephan
 
* http://www.limpkin.fr/index.php?post/2013/08/09/Making-the-electronics-for-a-%247-USD-doppler-motion-sensor
 
 
'''Raspberry Frequency measurment'''
 
* http://raspberrypi.stackexchange.com/questions/26166/count-rpm-frequency-pulses-on-gpio-ports-maximum
 
* http://blog.durablescope.com/2015/03/build-speed-camera-and-traffic-logger.html
 
* http://abyz.co.uk/rpi/pigpio/examples.html#C_code
 
* https://www.raspberrypi.org/forums/viewtopic.php?f=37&t=97795
 
* http://raspberrypi.stackexchange.com/questions/24812/measuring-frequency-via-gpio
 
* http://hacker.instanet.net/forums/viewtopic.php?f=4&t=104
 
 
{|class="wikitable alternance"
 
|+ Document History
 
|-
 
|
 
!scope="col"| Version
 
!scope="col"| Date
 
!scope="col"| Authors
 
!scope="col"| Description
 
!scope="col"| Validator
 
!scope="col"| Validation Date
 
|-
 
!scope="row" |
 
| 0.0.1
 
| 18/01/2016
 
| MACE Quentin, NOUGUIER Thibaut, RAMEL Régis
 
| Développement d'une application de détection de passages devant un capteur de présence
 
| Oliver Gattaz
 
| 06/04/2016
 
 
|}
 
 
 
=. Introduction=
 
==. Purpose of the requirements document==
 
==. Scope of the product==
 
==. Definitions, acronyms and abbreviations==
 
==. References==
 
==. Overview of the remainder of the document==
 
=. General description=
 
==. Product perspective==
 
==. Product functions==
 
==. User characteristics==
 
==. General constraints==
 
==. Assumptions and dependencies==
 
=. 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.
 
 
==. Requirement X.Y.Z (in Structured Natural Language)==
 
'''Function''':
 
 
'''Description''':
 
 
'''Inputs''':
 
 
'''Source''':
 
 
'''Outputs''':
 
 
'''Destination''':
 
 
'''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''':
 
 
'''Post-condition''':
 
 
'''Side-effects''':
 
 
=. Product evolution=
 
 
=. Appendices=
 
=. Index=
 

Latest revision as of 10:16, 18 January 2017

Objective of the project

The aim of the project is to use a doppler sensor to develop a web application that displays the historic of all passages in front of the sensor, with date, hour, speed, and direction. The sensor is connected to a Raspberry Pi with an Arduino to process the raw data and send the measures to a SQLite server. The server stores all the values and makes them available to the web client. This client is a user interface that allows the owner of the sensor to see the historic of passages in a legibly and interactive way (date range, graphs).

This application has to be developped with Cohorte, a service oriented platform that allows to split the application in different independant components. These components can be coded in different programming languages, and the communication between them is entirely managed by Cohorte. The application consists in the interaction between the components that provides and use services.

Technical environment