| scrollbar |
|---|
The script editor should allow for easy reconstruction of the historical timeline. This includes:
Method to add historical events.
This will be facilitated via the .XML file approach (see below on GUI).
Assign document files to a script (PDF or TXT)
Place the additional data in the historical timeline.
Additional functionalities to create events within the timeline, i.e. adapt the script:
Choices for the player / Decision points
This can be implemented with an additional screen filled with x (16) phone numbers / contacts, as discussed during the user meeting on 2011-04-18. If you click on a contact you get a result which depends on the game time. During certain time windows you will get an answer, outside of those windows not. Additionally, it could be made possible to show/hide this screen at certain moments (via configuration file).
Whether or not information is available can depend on triggers, such as the forecast as entered in the forecast display.
Actions to be taken by the player
User group doesn't see a direct purpose for this option (i.e. branching), therefore this will not be implemented (see MoM kick-off user group 2011-04-18 (.doc)).
Things going wrong: data and systems not available (electricity failure, etc)
This can be implemented by manipulating the available data. This is not part of the script editor, but of the scenario editor (see below).
Things going wrong: contacts temporarily unavailable (not currently foreseen)
This can be implemented via the "Phone screen" (see above).
Hints and suggestions to modify difficulty level
Hints and suggestions to help the player should be easily turned on/off
Scoring in the game based on points is not relevant at this stage (see MoM kick-off user group 2011-04-18 (.doc)). However, it would be interesting to allow the player to give a motivation together with the forecast (I used this model, because.. etc). This can be used in the evaluation with a (senior) colleague.
UI game. Based on the first uses of the games, the following additions would increase the user experience of the game (both additions have a low priority):
Button to jump back to the previous event
Option to sort messages on oldest or newest first.
The GUI of the script editor. could be implemented in several ways. The user group doesn't give a high priority to the development of an (expensive) Graphical User Interdace (see MoM kick-off user group 2011-04-18 (.doc)). Therefore, this year we will put our efforts on the expansion of the functionality of the game rather than on a GUI for the script editor. However, in a later stage, one of the other options can be considered.
Based on the current XML file (+ documentation) as used in the FEWS game. This scheme can be edited in XMLspy. Additional buttons to attach files should be added. Alex Minett will ask his UK clients to edit a script in this way.
Something similar to the HABITAT solution. Alex Minett will look into this option.
Using the script editor IDM from TNO
materiaal verzamelen
Based on the list of relevant data, methods or procedures have to be created and agreed upon with internal and external parties (like KNMI) to save the relevant data that cannot be copied from the FEWS local datastore or the MATROOS database.
Additional data sources can be things like:
Faxes
Phone calls. The calls to and from the SVSD room are automatically recorded.
Discussion within the team (this is not automatically recorded).
Forecasts
Evaluation of the SVSD team afterwards
SVSD Stormflits (summary made afterwards). This post-analysis includes comments to model performance in a specific situation.
Script maken
Leerdoelen
- Knoppencursus
- focus op vaardigheid
- basis verwachting maken
...