Changes between Version 3 and Version 4 of ScriptBuilderSRS


Ignore:
Timestamp:
07/27/2017 05:50:31 PM (9 years ago)
Author:
jdalbey
Comment:

under construction

Legend:

Unmodified
Added
Removed
Modified
  • ScriptBuilderSRS

    v3 v4  
    1010 
    11111. Glossary     2[[BR]] 
    12 2. Script Builder Tool Requirements     4[[BR]] 
    13 2.1 Incidents,  Scripts, and Timelines  4[[BR]] 
    14 2.2 Script      Builder File I/O        5[[BR]] 
    15 2.3 Support for TMC Simulation Control  6[[BR]] 
    16 2.4 Support for Student Evaluation      7[[BR]] 
    17 2.5 Supporting  Realism in Training     10[[BR]] 
    18 2.6 Specifying  Expected Traffic Network Performance    11[[BR]] 
    19 2.7 Instructor  Support 11[[BR]] 
    20 2.8 Other       Training Goals  12[[BR]] 
    21 3. Instructor Electronic Notebook Requirements  13[[BR]] 
    22 3.1 General     Requirements    13[[BR]] 
    23 3.2 Simulation  Summary Window  14[[BR]] 
    24 3.3 Simulation  Script Window   14[[BR]] 
    25 3.4 CHP CAD     Terminal Window 15[[BR]] 
    26 3.5 ATMS Display        Window  15[[BR]] 
    27 3.6 Simulation  Area Reference Roadway Map Window       16[[BR]] 
    28  
     121. 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]] 
     211. 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]] 
    2928 
    3029== 1. Glossary == 
    3130 
    32 ATMS    Advanced Traffic Management System – a tool utilized within Caltrans 
    33  
    34 CHP CAD California Highway Patrol (CHP) Computer Aided Dispatch (CAD) 
    35  
    36 CCTV    Closed circuit television – used to monitor roadways remotely from a TMC. 
     31 ATMS:: Advanced Traffic Management System – a tool utilized within Caltrans 
     32 CHP CAD::      California Highway Patrol (CHP) Computer Aided Dispatch (CAD) 
     33 CCTV:: Closed circuit television – used to monitor roadways remotely from a TMC. 
    3734 
    3835CMS     Changeable Message Sign 
     
    5855Incident Line   A graphical line in the timeline. An incident line represents an incident. 
    5956 
    60 LCS     LaneClosure System – a tool used by Caltrans to manage lane closureswithin the highway system. 
     57LCS     Lane Closure System – a tool used by Caltrans to manage lane closures within the highway system. 
    6158 
    6259Paramics        A tool which performs microscopic traffic simulation of the traffic network.  Note that Paramics is planned for deprecation from the TMCsimulator. 
    6360 
    64 Script  An XML file containing all details for all events within one or more incidents.  
    65  
    66 Script File     A script saved to XML file in a format conformant with the Simulation Manager & Script XML Schema. 
    67  
    68 Timeline        A graphical display of a script. 
     61 Script:: A chronological list of simulated 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 
     64 Timeline:: A horizontal line in a graphical display that represents the chronology of incidents in a script. 
    6965 
    7066Traffic 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. 
     
    7470== 2.Script Builder Tool Requirements == 
    7571 
    76 2.1 Incidents, Scripts, and Timelines 
    77  
    78 Incident Description & Summary 
    79  
    80 The Script Builder shall allow incidents to be entered. When an incident is entered, the user will enter information regarding that incident. Incident information shall include 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. 
     72=== 2.1 Scripts, Timelines, and Incidents === 
     73 
     74==== 1. Creating a new Script ==== 
     75 
     76A new script may be created which presents an empty timeline. 
     77 
     78==== 1. Saving a Script ==== 
     79 
     80Saving a script causes the script and all the incidents it contains to be saved in XML format to an external file. 
     81 
     82Adding a new Incident  
     83 
     84A 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 
     86Editing Incident Properties 
     87 
     88An incident's properties may be modified after it has been created. 
     89 
     90Editing Incident Events 
     91 
     92Editing an incident makes it available for events to be added, modified, and removed. 
     93 
     94Deleting an Incident 
     95 
     96Erases all the incident properties and events from the timeline. 
     97 
     98Inserting an Incident 
     99 
     100Inserting an incident displays a pool of available incidents (on auxiliary storage) and allows the user to select one for inclusion in the script being edited.  (Shall we disallow inserting the same incident twice in the same script?) 
     101 
     102Saving an Incident 
     103 
     104Saving an incident saves all the incident properties and the events it contains in XML format to an external file. 
    81105 
    82106Event Entry 
     
    86110Event Removal 
    87111 
    88 The user shall be able to remove events from incidents, by right-clicking on the event's icon and selecting“remove” from a pop-up menu. The user shall be able to remove an event by clicking on it and pressing the delete key. 
    89  
    90 Time-based Incident Display 
     112The user shall be able to remove events from incidents, by right-clicking on the event's icon and selecting “remove” from a pop-up menu. The user shall be able to remove an event by clicking on it and pressing the delete key. 
     113 
     114Graphical User Interface showing Time-based Incident Display 
    91115 
    92116The Script Builder shall allow the entry and modification of scripts using a timeline. The timeline will show each incident in the script as a line. Each event, represented by an icon,will be positioned on its corresponding incident's line.  This display shall show all individual events within a script, e.g. CADdata population, radio traffic, instructor/student phone call, etc.,with icons for each type of event.