This is an old revision of the document!
The trackwork system stories covers all of the Trackwork software and tools as they relate to one another. It also serves as a release point story timeline.
The customer related Trackwork system parts (that we know now) are:
- Trackwork Desktop
- TrackManager
- Track/Access Server
- SimpleTrack
Internal tools for demonstration and testing
Track Editor tool
- Change Track Day
- Copy Track data (Create new track)
- Shift Track location?
- Trim Track (implies some visual editing (time bar, geographic)
- Copy Pieces of track data
Trackwork Concepts
Views Time & Geo slicing of data (tracks) for reporting
Concepts Track-one machine on server.
In most cases we don't upload track data points from Trackwork. The exception would be a G-Ray or other non-connected sensor. We save modifications and View settings.
Views are what track work creates When we save we're really saving a view with a couple of exceptions. Trim and delete track all together.
Upload is probably wrong terminology for reporting/view saving function. Tech terminology is Publish but not user appropriate. Save ????? which saves view segmenting, cycle lines, stat areas up to the server is probably a better descriptor
The view concept is a powerful idea that translates to all programs and web. For example the report area concept in track work is really a view. We don't save it now but this would be away.
Objects I can imagine in there would be a time range. The track it points to. A label/tag/s associated with the track. You could also see things like cycle lines, geographic polygon descriptions (statistic/report areas)
How do we represent that to track work users?
