Difference between revisions of "Trodomètre/SRS"

From air
Jump to navigation Jump to search
Line 59: Line 59:
== Product perspective==
== Product perspective==
== Product functions==
== Product functions==
1. Define a departure point
This case corresponds to the definition of the starting point. Three different methods are possible: the first is to obtain the current position of the user, with a tracking system. That needs to be outdoors and have a tracking module on the smartphone. The second method is to ask the user. He selects a point on the map, and retrieves its value. This requires an access map (online or local). The third method asks the user for latitude and longitude. The selected point can be saved for repeated use.
2. Create an itinerary
This case corresponds to the recorded itinerary with the system. For this, the user needs a system and declares the point of departure (case 1). The user activates the record and navigates on the itinerary.
3. See orientation
The user can see the current system’s orientation and its modification. The modifications appear when the user turns. The system must be in itinerary creation (case 2).
4. Read the current itinerary state
The user can see the different measures step. For example, the first distance after the first turn, the first POI emplacement… The system must be in itinerary creation (case 2).
5. Record POI
The user has the ability to save POI. To do this, after he has activated the function, it must name the POI. Then, optionally, the user can record a corresponding sound. This function allows you to add information about the route. For example, in a station, you can add POI to represent a lift, to warn the person following the route. The system must be in itinerary creation (case 2).
6. Backup the itineraries :
The user can save the current itinerary, and start a new measurement.
7. Export Data
The user can export data. This export can be done in two ways: the first is to save it on a storage device, such as an SD card. The second method is to send the data via email. For this method, the software requires the user to connect to the internet.
8. Display an itinerary
The user can display an itinerary in OpenStreetMap view. For this, the route should be saved, and selected by the user.
9. Set option
The user can set the system and improve the reliability. The user can modify the diameter of the wheel, and the number of sensors available on the wheel.
== User characteristics==
== User characteristics==

Revision as of 14:52, 11 February 2013

Document History
Version Date Authors Description Validator Validation Date


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.


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

We have an actor class, the user. The user represents the person who wants to interact with the system. This interaction is divided into different tasks that the user can carry out.

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)








  • 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:




Product evolution