Trodomètre/SRS: Difference between revisions
No edit summary |
|||
Line 25: | Line 25: | ||
| TBC |
| TBC |
||
| TBC |
| TBC |
||
!scope="row" | |
|||
| 0.1.0 |
|||
| TBC |
|||
| TBC |
|||
| TBC |
|||
| TBC |
|||
| TBC |
|||
|} |
|} |
||
Revision as of 13:46, 11 February 2013
The document provides a template of the Software Requirements Specification (SRS). It is inspired of the IEEE/ANSI 830-1998 Standard.
Read first:
- 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
Version | Date | Authors | Description | Validator | Validation Date | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
0.1.0 | TBC | TBC | TBC | TBC | TBC | 0.1.0 | TBC | TBC | TBC | TBC | TBC |
Introduction
Purpose of the requirements document
Scope of the product
The goal of the “Trodometre” project is to provide a system to make accurate measurements during a journey. This system is able to calculate both indoor and outdoor measurements. In fact, it doesn’t use a localization system for its position in real time. Moreover, GPS is not available indoor and consumes a lot of energy which reduces the battery life of a system. Information collected by the program can be exported in XML format and used in OpenStreetMap. We can trace an itinerary everywhere precisely on the map. So, every circuit can be shared with everybody. The system is separated into two parts. The first part is the hardware. It is made up of sensors, based on ANT + technology (or BTLE), and moving means (scooter). Then, there is a second part with software which is based on Android an adaptability on every smartphone and mobile system. This system will be used by another project, Navigation of Visually Impaired People (http://autonomie.minalogic.net/index.en.html). This project is intended to facilitate mobility and independence of people with visual impairments. It works both indoors and outdoors, and facilitates access to public transport. Our system enables new itineraries to be created quickly and speeds up completion of those available.
Definitions, acronyms and abbreviations
Operating System
Android: Android is a Linux-based operating system designed primarily for touchscreen mobile devices such as smartphones and tablet computers. Initially developed by Android, Inc.
Communication System
ANT + : ANT is a proprietary wireless sensor network technology featuring a wireless communications protocol stack that enables semiconductor radios operating in the 2.4 GHz Industrial, Scientific and Medical allocation of the RF spectrum ("ISM band") to communicate by establishing standard rules for co-existence, data representation, signalling, authentication and error detection.
Bluetooth low energy : BLTE is a feature of Bluetooth 4.0 wireless radio technology, aimed at new, principally low-power and low-latency, applications for wireless devices within a short range (up to 50 metres / 160 feet -see table below). This facilitates a wide range of applications and smaller form factor devices in the healthcare, fitness, security, and home entertainment industries.
References
Android - https://developers.google.com/android/
ANT+ - http://www.thisisant.com/
Wahoo Fitness sensors - http://www.wahoofitness.com/Products/Wahoo-Fitness-Wahoo-Cycling-SpeedCadence-Sensor.asp
Bluetooh Low Energy - http://www.bluetooth.com/Pages/Low-Energy.aspx
General description
Product perspective
Product functions
User characteristics
General constraints
Support of the project must be mobile, discrete and lightweight. We are able to travel long and short distances easily. In addition, it must provide for attachment points for the sensors, and cheerful smartphone software. Our system should be work even without connection to Internet. We can imagine it being used everywhere in the world. Thanks to this, it is possible to save measurements in a XML file in the smartphone.
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: