Image by Marco Pomponio

(Purpose and scope)

Requirements

Purpose and scope

TrackDrown has the purpose of lowering the possibilities of losing valuable items, such as wallets, bags, backpacks, laptops etc. and reducing the chances of having valuable objects stolen. The system is based on the localization of antennas (one antenna per valuable item) in the indoor spaces of the campus. A series of detectors displaced inside the campus will track the antennas’ movements, and store the collected information in a database. Whenever a suspicious movement of an antenna is detected (e.g. one antenna departs from the smartphone), an alert is sent to the user.

Definitions

Glossary

  • Item: an object whose position/movements inside the campus needs to be monitored. It is intended to be a valuable object for the user (wallets, bags, backpacks, laptops, etc.).
  • Antenna: a small object associated to each item that will be tracked by the system.
  • Hot-spot detectors: permanent transmitters placed around the campus whose location is known by the system.
  • App: a mobile application that can be installed on user’s smartphone to interact with the system.
  • TrackDown: the system as a whole (all the antennas, the hot-spot detectors, the database and the App).

Actors

  • User: TrackDown is intended for every person spending their days (or portions of it) in the campus and whose belongings can be considered valuable.
  • Stakeholders: both users and the Politecnico di Torino as an institution (in particular employees involved in security services of the campus).

System requirements

Functional requirements

Functional Area Description

Functional Area Description
1 User login, registration and logout
2 Notifications sent by the system to user devices
3 Tracking
4 Interface for setting user preferences

1.1 User registration
* The user can create an account on the TrackDown system.
* Priority: 1

1.2 Antennas registration
* The user can register his antennas.
* Priority: 1

1.3 Deleting account
* The user can remove its account from Trackdown.
* Priority: 5

1.4 Log in on the app
* The user can login in order to use his smartphone as a localizer, track an antenna and change settings.
* Priority: 1

2.1 Getting away alert
* As soon as one of the antennas is detected to have departed from the smartphone, a notification is pushed to user. * Priority: 3

3.1 Locate me
* When the user realizes that an antenna is missing, and it is out of range, he can access all of the antenna’s previous locations recorded by the hot-spot detectors.
* Priority: 1

4.1 Getting away alert-delay
* With this setting the Getting away function can be frozen for a certain amount of time: this way you can leave your items without being warned if you go for a coffee.
* Priority: 3

4.2 Getting away alert-range
* With this setting the user can choose the threshold distance between smartphone and antenna, if they are further the smartphone will alert the user.
* Priority: 3

Non-functional requirements

  1. The antenna must be smaller than 60x60 mm and its power supply should guarantee at least 4 days of autonomy between recharges. (Product > Efficiency > Space)
  2. The maximum distance for having an antenna located by the smartphone is in the order of tens of meters. (Product > Efficiency > Performance)
  3. The maximum distance for having an antenna located by the hotspot detectors is in the order of tens of meters.(Product > Efficiency > Performance)
  4. The application running on smartphone must be compatible with Android 4.3 and with iOS 7.0. (Product > Portability)
  5. The application should be responsive to different display resolutions. (Product > Portability)

Open issues

  1. How to set-up the detectors network exploiting the available infrastructure inside the campus.
  2. How to guarantee battery autonomy keeping a satisfactory level of reactivity.
  3. How to use a smartphone’s Bluetooth API or eventually choosing a better standard.

How we solved them (update)

  1. The hotspots we developed exploit the available PoliTo network to send data.
  2. This issue was automatically solved by choosing a LE Bluetooth technology.
  3. The technology chosen came with its own interfacing APIs.