User Tools

Site Tools


access:trackwork_v.2_feature_requirements

This is an old revision of the document!


Main Page

Required Features

  • Store GPS points
  • Send and Retrieve GPS Points
  • Create representative summary view for app (tracks, both TMM like device and RTK)
  • Administration utilities (backup, migration, archive, restore, add customer, delete customer, shipping delivery mechanism (ie: generating xml authentication if necessary)
  • Authentication for routing ID
  • Single (or few) ports open for entry
  • Support for existing TMM's
  • bounded logs/ intelligent segregation
  • Version aware C/C++ Client API for Windows/Windows Mobile applications
  • friendly name association. Manual or RFID (assuming hardware becomes available)
Useful Errata

6 devices running create:

  • 172,800 pts per day (8 hours)
  • 864,000 pts per week (5 day)
  • 3,456,000 pts per 4 week month
  • 44,928,000 pts per year

Possible Future Features

These are things I can see us doing but could also be a major undertaking: They're included as talking points and may either disappear through consensus or move up to the feature requirements. Feel free to tack on stuff.

  • File Storage Capability (subset of Box.net capabilities)
    • Benefits
      • single login, shared data
      • simplified user experience, create web page interface
      • total control
    • Drawbacks
      • Time, big project
      • added complexity
      • probably more expensive
  • Project Permissions/ Access Control
    • Benefits
      • Potential customer hygiene solution.
      • Sales Demo examples can be shared without fear of inadvertent deletion.
    • Drawbacks
      • Affects all of the server design considerably. We can't tack this on after the fact.
      • Higher complexity for us and possibly the customer.
access/trackwork_v.2_feature_requirements.1245805626.txt.gz · Last modified: 2012/10/10 17:12 (external edit)