Changes between Version 5 and Version 6 of ScriptBuilderSRS
- Timestamp:
- 07/27/2017 06:35:30 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ScriptBuilderSRS
v5 v6 9 9 == Table of Contents == 10 10 11 1. Glossary 2[[BR]]12 1. Script Builder Tool Requirements 4[[BR]]13 1. Incidents, Scripts, and Timelines 4[[BR]]14 1. Script Builder File I/O 5[[BR]]15 1. Support for TMC Simulation Control 6[[BR]]16 1. Support for Student Evaluation 7[[BR]]17 1. Supporting Realism in Training 10[[BR]]18 1. Specifying Expected Traffic Network Performance 11[[BR]]19 1. Instructor Support 11[[BR]]20 1. Other Training Goals 12[[BR]]21 1. Instructor Electronic Notebook Requirements 13[[BR]]22 1. General Requirements 13[[BR]]23 1. Simulation Summary Window 14[[BR]]24 1. Simulation Script Window 14[[BR]]25 1. CHP CAD Terminal Window 15[[BR]]26 1. ATMS Display Window 15[[BR]]27 1. Simulation Area Reference Roadway Map Window 16[[BR]]11 1. Glossary [[BR]] 12 1. Script Builder Tool Requirements [[BR]] 13 1. Incidents, Scripts, and Timelines [[BR]] 14 1. Script Builder File I/O [[BR]] 15 1. Support for TMC Simulation Control [[BR]] 16 1. Support for Student Evaluation [[BR]] 17 1. Supporting Realism in Training [[BR]] 18 1. Specifying Expected Traffic Network Performance [[BR]] 19 1. Instructor Support [[BR]] 20 1. Other Training Goals [[BR]] 21 1. Instructor Electronic Notebook Requirements [[BR]] 22 1. General Requirements [[BR]] 23 1. Simulation Summary Window [[BR]] 24 1. Simulation Script Window [[BR]] 25 1. CHP CAD Terminal Window [[BR]] 26 1. ATMS Display Window [[BR]] 27 1. Simulation Area Reference Roadway Map Window [[BR]] 28 28 29 29 == 1. Glossary == … … 60 60 61 61 Script:: A chronological list of hypothetical traffic incidents for training purposes that can be played through the Simulation Manager. 62 Script File:: A script saved to XML file in a format conformant with the Simulation Manager & Script XML Schema. An XML file containing all details for all events within one or more incidents. The events are saved in chronological order (not grouped by incident). 63 62 Script File:: A script saved to XML file in a format conformant with the Simulation Manager & Script XML Schema. An XML file containing all details for all events within one or more incidents. The events are saved in chronological order (not grouped by incident). 64 63 Timeline:: A horizontal line in a graphical display that represents the chronology of incidents in a script. 65 66 Traffic Dot A colored dot as displayed on the ATMS with green indicating free-flow traffic, yellow indicating moderate reductions in speed/flow, and red indicating sever reductions in speed/flow. 67 68 TMT Traffic Management Team 64 Traffic Dot:: A colored dot as displayed on the ATMS with green indicating free-flow traffic, yellow indicating moderate reductions in speed/flow, and red indicating sever reductions in speed/flow. 65 TMT::Traffic Management Team 69 66 70 67 == 2.Script Builder Tool Requirements == … … 72 69 === 2.1 Scripts, Timelines, and Incidents === 73 70 74 ==== 1.Creating a new Script ====75 76 A new script may be created which presents an empty timeline.77 78 ==== 1.Saving a Script ====79 80 Saving a script causes the script and all the incidents it contains to be saved in XML format to an external file .81 82 Adding a new Incident71 ==== 2.1.1 Creating a new Script ==== 72 73 Creating a new script shows an empty timeline available for incidents to be added or inserted. 74 75 ==== 2.1.2 Saving a Script ==== 76 77 Saving a script causes the script and all the incidents it contains to be saved in XML format to an external file in conformance with the standard as detailed in the *Simulation Manager & Script XML Schema. (Look in Google Drive). 78 79 ==== 2.1.3 Adding a new Incident ==== 83 80 84 81 A new incident may be added to the script. When an incident is created the user will enter the properties of that incident: incident number, incident name, color of the incident's line, a description of the incident, the start time of the Incident, and the length of the incident. (Note, we are considering omitting incident number). 85 82 86 Editing Incident Properties 87 88 An incident's properties may be modified after it has been created. 83 ==== 2.1.4 Editing Incident Properties ==== 84 85 An incident's properties may be modified after it has been created. An incident's starting time may be adjusted. 89 86 90 87 Editing Incident Events … … 102 99 Saving an Incident 103 100 104 Saving an incident saves all the incident properties and the events it contains in XML format to an external file. 101 Saving an incident saves all the incident properties and the events it contains in XML format to an external file. Saving also includes all associated resources like audiofiles. Saving will present a custom dialog (instead of a standard file chooser) that constrains the filename that can be used to store the incident data. 102 103 Incident Extractor Wizard 104 105 This wizard allows the user to load a script and extract incidents from it. 105 106 106 107 Event Entry … … 128 129 The Script Builder shall utilize distinct icons to represent all events on the timeline. The icons shall be sufficiently small so that they can be displayed on the incident lines in the timeline. The icons shall be sufficiently distinctive from one another so that they may be easily differentiated from one another by the user. Evaluation event icons shall be identical to their corresponding control event icons, except that they will be differentiated by a unique feature such as an easily visible addition to the icon, e.g. a checkmark, a dot, etc. 129 130 131 {{{ 132 #!html 133 <strike> 130 134 Merging Multiple Scripts onto Timeline 131 135 … … 134 138 Extracting a Script from the Timeline 135 139 136 The Script Builder shall be capable of extracting a script from the timeline. (I think this means exporting incidents,because the timeline has nothing to be extracted from it but incidents. Export includes all associated resources like audiofiles.) 140 The Script Builder shall be capable of extracting a script from the timeline. (I think this means exporting incidents,because the timeline has nothing to be extracted from it but incidents. ) 141 </strike> 142 }}} 137 143 138 144 Page Numbers on Scripts for instructors to use. Was latex. Perhaps PDF. Neal will find what was used before. … … 140 146 The Script Builder shall support the ability to put page numbers on generated script notebooks. 141 147 142 2.2 ScriptBuilder File I/O 143 144 145 146 Script File Format 147 148 The Script Builder shall read from and save generated scripts to an XML file in conformance with the standard as detailed in the *Simulation Manager & Script XML Schema. Look in Google Drive. * 149 150 Opening an existing Script File 151 152 The Script Builder shall allow the user to open ascript using standard Windows controls such as a pull-down menu (File-> Open) and/or an icon. 153 154 Savinga Script File 155 156 The Script Builder shall allow the user to save anscript to file with a name of their choice or save changes to anexisting script using standard Windows controls such as pull-downmenus (File->Save and File->Save As) and/or an icon. 157 158 2.3 Supportfor TMC Simulation Control 148 149 150 2.3 Support for TMC Simulation Control 159 151 160 152 Simulation Control Events - General
