Overview
The document records the requirements to be met by the Delight high level replay tool. The Delight tool will be used by a range of maritime operators to gain a high-level familiarity with events recorded over a limited time period.
Aims
- easy to use: minimal user interface to meet functionality
- graphically rich: attractive, welcoming user interface
- versatile: capable of replaying wide range of scenarios
- low footprint: should be classed as "data-file" rather than application - to avoid integration/testing hurdles
Glossary
- annotation
- text-label at geographic location, potentially time-stamped
- backdrop
- image displayed "behind" track data, showing raster or vector data (possibly with vector snapped as raster)
- narrative
- series of time-stamped diary entries, possibly including 'type' or 'author' of diary entry
- plot
- graphic image of projected track data, with annotations, over backdrop
- track
- series of vehicle positions, date-stamped, in 2 or 3 dimensions
Target Scenarios
- post-event ownship analysis
- (onboard replay of own tracks)
- post-event collaborative analysis
- (onboard replay of exchanged tracks - includes either combining multiple data-files into one, or successively loading multiple files)
- Quick-look Analysis
- Field Analyst collates data immediately after event, possibly adding comments, distributes resultant files back to participants prior to exercise completion.
- Exercise feedback
- Track data analysed by Shore Analyst (using heavyweight analysis tool), collates serials of interest (including analysis comments), distributes files alongside analysis report. (once analyis complete, analyst collates serials of interest, distributes to participants and as analysis report accompaniment)
- Archive Analysis
- Shore-based organisation collates data-files stored in online repository. Shore Analyst browses through available data-sets, drilling-down as required.
Target users
| User | Background | Goal |
| Field analyst | scientific or uniformed laptop-equipped user | Verify data recordings, identify early lessons to speed lessons process or affect ongoing trial |
| Field participant | uniformed laptop-equipped user | Verify data recordings, perform quick look analysis to generate feedback for command team |
| Shore executive | uniformed desktop-equipped user | Perform high-level analysis of events, possibly including findings in report/briefings. Browse through legacy data-files |
| Shore analyst | scientific or uniformed desktop-equipped user | Perform initial analysis of events, possibly with aim of verifying data, moving through large body of data files to select data for subsequent analysis with heavyweight tool. Potentially collate tracks, narratives, backdrops for onward release to shore executive |
Use Cases
Requirements
System Requirements
- what it must do
- command line options
- break up by subsystem
such as:
- i18n - to handle different markets/branding
- help guidance (try to make it novel - cartoon-like drawings?)
- update management (probably offline)
- version number indication
- log-file access
UI Requirements
- extractable mini-doc to forward to designers
- mockups
- themes/skins
- branding
- what graphic imagery is required
Tools Requirements
Support tools around the periphery of the application
- how plots, narratives, backdrops are going to be produced
- installer requirements
Service Requirements
- Any API/etc to be exposed by the application
- Logging within the application
Risk Analysis
- what could go wrong...
Competitor analysis
- SWOT? type analysis of what else is out there
