I-15 REVERSIBLE LANE

CONTROL SYSTEM PROJECT

GUI REQUIREMENTS DOCUMENT

Prepared for:

State of California

Department of Transportation

San Diego, CA

Prepared by:

![](media/image1.wmf){width="2.9993055555555554in"
height="0.9354166666666667in"}

300 south Harbor Boulevard

Suite 516

Anaheim, CA 92805

JUNE 18, 1999

Version Control

  ----------------------------------------------------------------------------------
  **REVISION                                              
  HISTORY**                                               
  ------------- ---------- ------------- ---------------- --------------------------
  **Date**      **Rev.**   **SPCR(s)**   **Section(s)**   **Description**

  24 May 1999   DRAFT                                     Draft release for review.

  18 June 1999  Final                                     Final document submittal.

                                                          

                                                          
  ----------------------------------------------------------------------------------

Table of Contents

1\. Scope [1-1](#scope)

2\. Applicable Documents [2-1](#applicable-documents)

3\. GUI Requirements [3-1](#gui-requirements)

3.1 User / Task Functional Requirements
[3-1](#user-task-functional-requirements)

3.1.1 User Profiles [3-1](#user-profiles)

3.1.2 Task Profiles [3-2](#task-profiles)

3.2 User Interface Functional Requirements
[3-5](#user-interface-functional-requirements)

3.2.1 System Icons [3-5](#system-icons)

3.3 Windows [3-12](#windows)

3.3.1 Map Window [3-12](#map-window)

3.3.2 Command Toolbar [3-13](#command-toolbar)

3.3.3 Device Control Window [3-13](#device-control-window)

3.3.4 Summary Device Status Window [3-14](#summary-device-status-window)

3.3.5 Detailed Device Status Window
[3-14](#detailed-device-status-window)

3.3.6 Incident Entry / Edit Window [3-15](#incident-entry-edit-window)

3.3.7 Daily Diary Window [3-16](#daily-diary-window)

3.3.8 Problem Work Order Window [3-16](#problem-work-order-window)

3.3.9 Scheduler Window [3-17](#scheduler-window)

3.3.10 Paging Contact Window [3-17](#paging-contact-window)

3.3.11 Macro Editor Window [3-17](#macro-editor-window)

3.3.12 Macro Control Window [3-18](#macro-control-window)

3.3.13 Logon Window [3-18](#logon-window)

3.3.14 User Identification Window [3-19](#user-identification-window)

3.3.15 User Administration Window [3-19](#user-administration-window)

3.3.16 Report Windows [3-19](#report-windows)

3.3.17 Scenario Editor Window [3-19](#scenario-editor-window)

3.3.18 Scenario Control Window [3-20](#scenario-control-window)

3.3.19 Help Window [3-20](#help-window)

3.4 Performance Requirements [3-20](#performance-requirements)

4\. Graphical User Interface Guidelines
[4-1](#graphical-user-interface-guidelines)

4.1 General Guidelines [4-1](#general-guidelines)

4.1.1 Icons [4-1](#icons)

4.1.2 Form Entry [4-1](#form-entry)

4.1.3 Field Validation [4-2](#field-validation)

4.1.4 Error Message Window [4-2](#error-message-window)

4.1.5 Fonts [4-2](#fonts)

4.1.6 Combination Boxes [4-2](#combination-boxes)

4.1.7 Hot Keys [4-2](#hot-keys)

4.1.8 User Login [4-3](#user-login)

4.1.9 Window Configuration [4-3](#window-configuration)

LIST OF EXHIBITS AND TABLES

Table 3.1: Task Profiles by User 3-2

# Scope

This document extracts the requirements for the Graphical User Interface
(GUI) from the I-15 HOV Reversible Lane Control System Project, System
Requirements Document, and organizes them into a top-level design for
the user interface. This document identifies the user type requirements
and user security requirements. This defines several levels of user
access capabilities. The document then identifies all required user
tasks, by user type and user security level. Each identified task
creates a need for a user interface design feature to implement the
requirement and provide the user with an efficient means of
accomplishing the task.

The document then identifies those user interface design features and
groups them into categories. These categories include:

-   Map presentations, including icons for representing the type,
    location, state and status of field devices, such as gates, pop-ups,
    CCTV cameras, etc.

-   Windows for presenting text and graphic information and for
    presenting menus of user commands and response actions.

Finally, the document identifies a set of general rules for navigating
through and between the windows. These general rules will define a
consistent and efficient interface for the various users.

# Applicable Documents

1.  System Requirements Document, Version C, for the I-15 HOV Reversible
    Lane Control System Project, TransCore, December 4, 1998

2.  Designing the User Interface, 3^rd^ Edition, Ben Shneiderman,
    Addison-Wesley 1998

3.  Guidelines for Enterprise-Wide GUI Design, Susan Weinschenk,
    Sarah C. Yeo, John Wiley, 1995

4.  Designing Visual Interfaces, Kevin Mullet, Darrell Sano, Prentice
    Hall PTR, 1995

# GUI Requirements

## User / Task Functional Requirements

### User Profiles

Users shall be defined by four attributes:

-   Which type of workstation they are using

-   Their authorized user type as assigned by the system administrator

-   Their authorized security level as assigned by the system
    administrator

-   Their authorized control level as assigned by the system
    administrator

#### Type of Workstation

The system shall support six different locations for user. Each location
shall have different features and capabilities. For example, video
display is only available at the workstations at the TMC and is not
available to workstations at the FCU or the DCU. The system shall
support the following six locations:

1.  TMC HOV User

```{=html}
<!-- -->
```
5.  TMC Maintenance User

6.  TMC Trainer

7.  FCU Dial-in User

8.  FCU User

9.  DCU User

Each user type will exist on the simulation system and on the live
system. Commands issued at the simulator workstation will only control
the simulator components, not the live field devices.

#### Security Level

The system shall support six levels of security authorization for users.
The system administrator shall assign the security level when a user is
registered on the system. The six levels of security enable the system
to accommodate and control the actions of who have a; variety of
capabilities and needs.

The six levels of security, in descending order, are:

-   System Administrator -- highest access privilege, access to
    Configuration Tasks and all lower security level tasks

-   Security Level 1 -- access to all command tasks (Command Level 3),
    initiation and override commands and all lower security level tasks

-   Security Level 2 -- access to macro command tasks (Command Level 2
    and all lower security level tasks

-   Security Level 3 -- access to super macro command tasks (Command
    Level 1) and lower security level tasks

-   Security Level 4 -- no command tasks, only data entry tasks and
    lower security level tasks

-   Security Level 5 -- review and print reports viewing system status

#### Command Level

The system shall support three levels of command authority. Each command
levels shall be associated with a security level. The three command
levels are:

-   Control Level 1 -- super macro command tasks (open / close)

-   Control Level 2 -- macro command tasks (groups of devices)

-   Control Level 3 -- individual device command tasks

### Task Profiles

The system shall support the following task profiles:

Table 3.1 - Task Profiles by User

+---+---------------+-----------+-----------+-------------------------+
| \ | TASK          | USER TYPE | SECURITY  | TASK DETAILS            |
| # |               |           | LEVEL     |                         |
+===+===============+===========+===========+=========================+
| 1 | Logon         | All       | All       | Operator shall enter    |
|   |               |           |           | user name and password. |
|   |               |           |           | After successful login, |
|   |               |           |           | user name, date and     |
|   |               |           |           | time, and workstation   |
|   |               |           |           | location shall be       |
|   |               |           |           | displayed.              |
+---+---------------+-----------+-----------+-------------------------+
| 2 | Accept        | All       | Level 3   | After successful logon, |
|   | Command       | except 3  | and up    | the user will be asked  |
|   | Control       |           |           | to accept or deny       |
|   |               |           |           | command control (become |
|   |               |           |           | the operator) if their  |
|   |               |           |           | configured security     |
|   |               |           |           | level is higher than or |
|   |               |           |           | equal to the current    |
|   |               |           |           | operator's              |
+---+---------------+-----------+-----------+-------------------------+
| 3 | Transfer      | All       | Level 3   | Transfer operator       |
|   | Command       | except 3  | and up    | status to another       |
|   | Control       |           |           | logged on user by       |
|   |               |           |           | current operator only   |
+---+---------------+-----------+-----------+-------------------------+
| 4 | Zoom-in /     | All       | All       | Select different scale  |
|   | zoom-out on   | except 3  |           | maps                    |
|   | map           |           |           |                         |
+---+---------------+-----------+-----------+-------------------------+
| 5 | Select        | All       | All       |                         |
|   | display of:   | except 3  |           |                         |
|   |               |           |           |                         |
|   | Device Status |           |           |                         |
|   |               |           |           |                         |
|   | HOV facility  |           |           |                         |
|   | status        |           |           |                         |
+---+---------------+-----------+-----------+-------------------------+
| 6 | Select        | All       | All       |                         |
|   | display of:   | except 3  |           |                         |
|   |               | and 6     |           |                         |
|   | Map           |           |           |                         |
|   |               |           |           |                         |
|   | Device and    |           |           |                         |
|   | device        |           |           |                         |
|   | location      |           |           |                         |
|   |               |           |           |                         |
|   | Traffic       |           |           |                         |
|   | volume        |           |           |                         |
|   |               |           |           |                         |
|   | Traffic speed |           |           |                         |
|   |               |           |           |                         |
|   | Incidents     |           |           |                         |
|   |               |           |           |                         |
|   | Direction of  |           |           |                         |
|   | traffic flow  |           |           |                         |
|   |               |           |           |                         |
|   | External      |           |           |                         |
|   | interface and |           |           |                         |
|   | status        |           |           |                         |
+---+---------------+-----------+-----------+-------------------------+
| 7 | Level 1       | 1 only    | Level 3   | Control, by current     |
|   | System        |           | and up    | operator only, to open  |
|   | Control       |           |           | north or south bound in |
|   | (super macro  |           |           | AM or PM or emergency   |
|   | control)      |           |           |                         |
+---+---------------+-----------+-----------+-------------------------+
| 8 | Level 2       | 1, 2, 4,  | Level 2   | Control, by current     |
|   | Device Group  | 5         | and up    | operator only, of:      |
|   | Control       |           |           |                         |
|   | (macro level  |           |           | -   pop-ups by location |
|   | control)      |           |           |     (with location 1    |
|   |               |           |           |     split into an       |
|   |               |           |           |     entrance and a      |
|   |               |           |           |     wrong-way part)     |
|   |               |           |           |                         |
|   |               |           |           | -   gate                |
|   |               |           |           |                         |
|   |               |           |           | -   lights by location  |
|   |               |           |           |                         |
|   |               |           |           | -   CMSs by highway (NB |
|   |               |           |           |     15, NB 163, SB 15)  |
+---+---------------+-----------+-----------+-------------------------+
| 9 | Level 3       | All       | Level 1   | Control, by current     |
|   | Individual    | except 3  | and up    | operator only, of:      |
|   | Device        |           |           |                         |
|   | Control       |           |           | -   Pop-up by bank      |
|   |               |           |           |                         |
|   |               |           |           | -   Individual CMS      |
+---+---------------+-----------+-----------+-------------------------+
| 1 | Device Reset  | All       | Level 3   | Reset of non-responsive |
| 0 |               | except 3  | and up    | device by current       |
|   |               |           |           | operator only           |
+---+---------------+-----------+-----------+-------------------------+
| 1 | Command       | All       | Level 3   | Confirmation of         |
| 1 | Confirmation  | except 3  | and up    | individual device       |
|   |               |           |           | response to a command   |
|   |               |           |           | by current operator     |
|   |               |           |           | only                    |
+---+---------------+-----------+-----------+-------------------------+
| 1 | Command       | All       | Level 3   | Allows the current      |
| 2 | Override      | except 3  | and up    | operator only to skip a |
|   |               |           |           | command                 |
+---+---------------+-----------+-----------+-------------------------+
| 1 | Set Device    | All       | Level 3   | Allows a field device   |
| 3 | Status        |           | and up    | or external interface   |
|   |               |           |           | to be manually          |
|   |               |           |           | designated as operable  |
|   |               |           |           | or inoperable           |
+---+---------------+-----------+-----------+-------------------------+
| 1 | Set, edit and | 1 only    | System    |                         |
| 4 | delete user,  |           | Admi      |                         |
|   | user security |           | nistrator |                         |
|   | level, user   |           |           |                         |
|   | name and      |           |           |                         |
|   | password      |           |           |                         |
+---+---------------+-----------+-----------+-------------------------+
| 1 | Edit User     | 1 only    | System    |                         |
| 5 | Display       |           | Admi      |                         |
|   | Profile       |           | nistrator |                         |
+---+---------------+-----------+-----------+-------------------------+
| 1 | Set Logon     | 1 only    | System    |                         |
| 6 | Timeout       |           | Admi      |                         |
|   | Parameter     |           | nistrator |                         |
+---+---------------+-----------+-----------+-------------------------+
| 1 | Edit Contact  | 1 only    | System    |                         |
| 7 | List          |           | Admi      |                         |
|   |               |           | nistrator |                         |
+---+---------------+-----------+-----------+-------------------------+
| 1 | Edit "Daily   | All       | Level 4   |                         |
| 8 | Diary"        |           | and up    |                         |
+---+---------------+-----------+-----------+-------------------------+
| 1 | Create, edit, | All       | Level 4   |                         |
| 9 | export and    |           | and up    |                         |
|   | delete        |           |           |                         |
|   | Problem Work  |           |           |                         |
|   | Orders        |           |           |                         |
+---+---------------+-----------+-----------+-------------------------+
| 2 | Edit Schedule | All       | Level 4   |                         |
| 0 |               |           | and up    |                         |
+---+---------------+-----------+-----------+-------------------------+
| 2 | Page Contacts | All       | Level 4   | Allows the contact list |
| 1 |               |           | and up    | to be paged because of  |
|   |               |           |           | a Critical Alarm        |
+---+---------------+-----------+-----------+-------------------------+
| 2 | Specify and   | All       | All       | Retrieve reports from   |
| 2 | Retrieve      | except 6  |           | archive media           |
|   | Archived      |           |           |                         |
|   | Reports       |           |           |                         |
+---+---------------+-----------+-----------+-------------------------+
| 2 | Display /     | All       | All       | Print capability only   |
| 3 | Print /Export | except 6  |           | at TSU and FCU dial-in  |
|   | Report, Daily |           |           | workstations            |
|   | Diary,        |           |           |                         |
|   | Problem Work  |           |           |                         |
|   | Order,        |           |           |                         |
|   | Schedule and  |           |           |                         |
|   | Contact List  |           |           |                         |
+---+---------------+-----------+-----------+-------------------------+
| 2 | Display Help  | All       | All       |                         |
| 4 | Screen        |           |           |                         |
+---+---------------+-----------+-----------+-------------------------+
| 2 | Select Camera | 1 and 2   | Level 3   | Allow user to select    |
| 5 | Image         |           | and up    | the video image from a  |
|   |               |           |           | specific camera for     |
|   |               |           |           | display (selection by   |
|   |               |           |           | the operator will       |
|   |               |           |           | override, if necessary, |
|   |               |           |           | selection by any other  |
|   |               |           |           | user)                   |
+---+---------------+-----------+-----------+-------------------------+
| 2 | Pan, tilt,    | 1 and 2   | Level 3   | Allows a user to point  |
| 6 | and zoom      |           | and up    | and zoom a surveillance |
|   | Surveillance  |           |           | camera unless that      |
|   | Camera        |           |           | camera's video is       |
|   |               |           |           | selected by the current |
|   |               |           |           | operator                |
+---+---------------+-----------+-----------+-------------------------+
| 2 | Transfer      | 1, 4, 5   | Level 3   | Allows the current      |
| 7 | Control of    |           | and up    | operator to transfer    |
|   | Camera to /   |           |           | control of a camera, or |
|   | from ATMS     |           |           | group of cameras, to or |
|   |               |           |           | from an ATMS Operator   |
+---+---------------+-----------+-----------+-------------------------+
| 2 | Configure     | All       | System    | Add or delete a field   |
| 8 | Field Device  | except 6  | Admi      | device from the system  |
|   |               |           | nistrator |                         |
+---+---------------+-----------+-----------+-------------------------+
| 2 | Generate      | 3 only    | Level 3   |                         |
| 9 | Training      |           | and up    |                         |
|   | Scenarios     |           |           |                         |
+---+---------------+-----------+-----------+-------------------------+
| 3 | Select and    | 3 only    | Level 3   |                         |
| 0 | Execute       |           | and up    |                         |
|   | Training      |           |           |                         |
|   | Scenario      |           |           |                         |
+---+---------------+-----------+-----------+-------------------------+
| 3 | Enter, edit   | All       | Level 3   |                         |
| 1 | and delete    |           | and up    |                         |
|   | incident      |           |           |                         |
|   | information   |           |           |                         |
+---+---------------+-----------+-----------+-------------------------+

## User Interface Functional Requirements

### System Icons

This section describes required icons and the required functionality of
the icons for the I‑15 Reversible Lane Control System. The specifics of
the icons will be defined during the detailed design.

#### Gates

The gates referred to in this section are the entrance blocking gates at
both ends of the freeway.

##### An icon shall be selected during detailed design to show a gate in a closed position.

##### An icon shall be selected during detailed design to show a gate in an open position.

##### An icon shall be selected during detailed design to show a gate in a partially open (15%) open position.

##### The gate icon shall be configurable to show the name of the gate with the icon.

##### The gate icon shall be configurable to show the state of the gate (e.g., open or close).

##### The gate icon shall be configurable to show the status of the gate (operational, failed, or no data). The color of the gate icon shall be changed to show the status of the gate.

##### When the operator moves the mouse over a gate icon a text window shall be displayed showing a summary of the gate status. The details of the summary status display will be defined in the GUI design document.

##### The operator shall be able to activate a detailed device status window for the selected gate by double left clicking on the icon. This action shall cause a circle to be displayed over the gate icon for as long as the detailed device status window is displayed for that gate.

##### The operator shall be able to activate a device control window for the selected gate by right clicking on the icon. The right click on the icons shall display a pop-up menu of available device actions from which the user may select. This action shall cause a circle to be displayed over the gate icon for as long as the device control window is displayed for that gate.

###### If operation of the device is locked out for safety reasons a command option will be "grayed out" and not selectable.

#### Popups

##### An icon shall be selected during detailed design to indicate a group of popups in an "Up" or entrance closed position.

##### An icon shall be selected during detailed design to indicate a group of popups in a "Down" or entrance opened position.

##### An icon shall be selected during detailed design to indicate a failure status when some popups in a group are in a "Down" position and some popups in the same group are in an "Up' position.

##### The popup icon shall be configurable to display the name of the popup group.

##### The popup icon shall be configurable to display the state of the popup group (up or down).

##### The popup icon shall be configurable to display the status of the popup group. The color of the icon shall be changed to show the status of the popup group.

##### When the operator moves the mouse over a popup icon a text window shall be displayed showing a summary of the popup group status. The details of the status display will be defined in the GUI design document.

##### The operator shall be able to activate a detailed device status window for the selected popup group by double left clicking on the icon. A circle shall be displayed over the icon as long as the detailed status window is displayed for the icon.

##### The operator shall be able to activate a device control window for the selected popup by right clicking on the icon. The right click on the icon shall display a pop-up menu of available device actions from which the user may select. A circle shall be displayed over the icon as long as the device control window is displayed for the icon.

###### If operation of the device is locked out for safety reasons a command option will be "grayed out" and not selectable.

#### CMS

##### An icon shall be selected during detailed design to indicate changeable message signs.

##### An icon shall be selected during detailed design to indicate a changeable message sign that is displaying a message.

##### The CMS icon shall be configurable to display the name of the sign with the icon.

##### The CMS icon shall be configurable to display an abbreviated message text with the icon.

##### The CMS icon shall be configurable to display the status of the sign associated with the icon. The CMS icon color shall represent the operational status of the CMS sign: green for operational, yellow for operational with errors, gray for no communications and red for failed.

##### If the operator moves the mouse over the CMS icon then a text window shall be displayed with a summary of the operational state and status of the sign and the text of any message being displayed on the sign.

##### The operator shall be able to activate a detailed device status window for the sign by double left clicking on the selected icon. A circle shall be displayed over the icon as long as the detailed device status window is displayed for that icon.

##### The operator shall be able to activate a device control window for the CMS sign by right clicking on the selected icon. The right click on the icon shall display a pop-up menu of available device actions from which the user may select. A circle shall be displayed over the icon as long as the device control window is displayed for that icon.

###### If operation of the device is locked out for safety reasons a command option will be "grayed out" and not selectable.

#### CCTV Camera

##### An icon shall be selected to indicate a CCTV camera

##### The camera icon shall be configurable to show the name of the camera with the icon.

##### The camera icon shall be configurable to show the state of the camera.

##### The camera icon shall be configurable to show the status of the camera. The color of the camera icon shall be changed to show the status of the camera.

##### When a user moves the mouse over a camera icon a text window shall be displayed showing a summary of the camera status.

##### The user shall be able to activate a detailed device status window for the selected camera by double left clicking on the icon. This action shall cause a circle to be displayed over the camera icon for as long as the detailed device status window is displayed for that camera.

##### The user shall be able to activate a device control window for the selected camera by right clicking on the icon. The right click on the icon shall display a pop-up menu of available device actions from which the user may select. This action shall cause a circle to be displayed over the camera icon for as long as the device control window is displayed for that camera.

#### Draw Lights

##### An icon shall be selected during detailed design to indicate a group of draw lights that are off.

##### An icon shall be selected during detailed design to indicate a group of draw lights that are on.

##### An icon shall be selected during detailed design to indicate a group of draw lights where some are on and some are off.

##### The draw light icon shall be configurable to display the name of the draw lights.

##### The draw light icon shall be configurable to display the state of the draw lights.

##### The draw light icon shall be configurable to display the status of the draw lights. The color of the draw light icon shall represent the status of the draw light: green for operational, yellow for operational with errors, gray for no communications and red for failed.

##### When the operator moves the mouse over a draw light icon a text window shall be displayed showing a summary of the status of the group of draw lights. The details of the status display will be defined in the GUI design document.

##### The operator shall be able to activate a detailed device status window for the draw lights by double left clicking on the selected icon. A circle shall be displayed over the icon as long as the detailed device status window is displayed for that icon.

##### The operator shall be able to activate a device control window for the draw lights by right clicking on the selected icon. The right click on the icon shall display a pop-up menu of available device actions from which the user may select. A circle shall be displayed over the icon as long as the device control window is displayed for that icon.

###### If operation of the device is locked out for safety reasons the command option will be "grayed out" and not selectable.

#### Wrong Way Lights

##### An icon shall be selected during detailed design to indicate a group of wrong way lights that are off.

##### An icon shall be selected during detailed design to indicate a group of wrong way lights that are on.

##### An icon shall be selected during detailed design to indicate a group of wrong way lights where some are on and some are off.

##### The wrong way light icon shall be configurable to display the name of the draw lights.

##### The wrong way light icon shall be configurable to display the state of the wrong way lights.

##### The wrong way light icon shall be configurable to display the status of the group of wrong way lights. The color of the wrong way light icon shall represent the status of the wrong way light: green for operational, yellow for operational with errors, gray for no communications and red for failed.

##### When the operator moves the mouse over a wrong way light icon a text window shall be displayed showing a summary of the status of the group of wrong way lights. The details of the status display will be defined in the GUI design document.

##### The operator shall be able to activate a detailed device status window for the wrong way lights by double left clicking on the selected icon. A circle shall be displayed over the icon as long as the detailed device status window is displayed for that icon.

##### The operator shall be able to activate the control window for the wrong way light by right clicking on the selected icon. The right click on the icon shall display a pop-up menu of available device actions from which the user may select. A circle shall be displayed over the icon as long as the device control window is displayed for that icon.

###### If operation of the device is locked out for safety a command option will be "grayed out" and not selectable.

#### Loop Detectors

##### An icon shall be selected during detailed design to indicate a loop detector.

##### An icon shall be selected during detailed design to indicate a group of loop detectors.

##### The loop detector and group detector icons shall use color to indicate either speed, volume, or occupancy is within a specified range or if no data is available from the detector or from all loop detectors in a group.

##### The color used to indicate a range shall be configurable.

##### The data being displayed by color shall be *configurable*.

##### The range being displayed by a color shall be configurable.

##### The operator shall be able to configure the color, the range and/or the data type without restarting the application.

##### The loop detector icon shall be configurable to display the name of the loop detector.

##### The loop detector icon shall be configurable to display the N second volume, speed and occupancy values as text associated with the icon. The value on N shall be configurable.

##### The group detector icon shall be configurable to display the name of the detector group name as text with the icon.

##### The group detector icon shall be configurable to display the N second average of volume, speed and occupancy for all detectors in the group as text with the icon. The value of N shall be configurable.

##### The detector loop icon shall be configurable to display the status of the loop detector or group of loop detectors.

##### When the operator moves the mouse over a detector loop icon a text window shall be displayed showing a summary of the status of the loop detector or the group of detector loops. The details of the status display will be defined in the GUI design document.

##### The operator shall be able to activate a detailed device status window for the loop or group of loops by double left clicking on the selected icon. A circle shall be displayed over the icon as long as the detailed device status window for that icon.

#### FCU and DCU/MCU

##### Icons shall be selected during detailed design to represent the FCUs and the DCU/MCUs.

##### The FCU icon and the DCU/MCU icon shall be configurable to show the name of the site with the icon.

##### The icons shall be configurable to show the status of the equipment at the site. The color of the icons shall be changed to show the status of the equipment.

##### When the operator moves the mouse over an FCU or DCU/MCU icon a text window shall be displayed showing a summary of the site status. The details of the status display will be defined in the GUI design document.

##### The operator shall be able to activate a detailed device status window for the selected site by double left clicking on the icon. This action shall cause a circle to be displayed over the icon for as long as the detailed device status window is displayed for that site.

#### HOV End Points

##### An icon shall represent the end point of the HOV lanes (North and South). The icon shall have different shapes to represent that the end point is closed, open Southbound or open Northbound.

##### The end point icon shall be configurable to show the name of the end point associated with the icon.

##### The end point icon shall be configurable to show the state of the end point associated with the icon.

##### The end point icon shall be configurable to show the status of the end point. The color of the icon shall be changed to show the status of the end point.

##### When the operator moves the mouse over an end point icon a text window shall be displayed showing a summary of the end point status. The details of the summary status display will be defined in the GUI design document.

##### The operator shall be able to activate a detailed device status window for the selected end point by double left clicking on the icon. This action shall cause a circle to be displayed over the icon for as long as the detailed device status window is displayed for that end point.

#### Incidents

##### An icon shall be selected during detailed design to represent active incidents.

##### The incident icon shall be configurable to display the state of the incident.

##### When the operator moves the mouse over an incident icon a text window shall be displayed showing a summary of the incident state. The details of the summary state display will be defined in the GUI design document.

##### The operator shall be able to activate a detailed incident state window for the selected incident by double left clicking on the icon. This action shall cause a circle to be displayed over the incident icon for as long as the detailed device status window is displayed for that incident.

##### The operator shall be able to activate an edit window for the selected incident by right clicking on the icon. This action shall cause a circle to be displayed over the incident icon for as long as the edit window is displayed for that incident.

## Windows

Information on the screen of the user's monitor shall be presented in a
window. Various windows shall display maps information, menus, text and
graphic information and forms. Windows shall be adjustable in size and
location, but shall have a default size and location.

### Map Window

#### The map window shall display the HOV lanes, the adjacent lanes of I-15 and SR 163, crossing streets and their interchange, if any, and icons.

#### Three map windows shall be provided: one showing the entire length of the HOV lanes, one showing a detail of the south end of the HOV lanes and one showing a detail of the North end of the HOV lanes.

#### Caltrans shall be able to create new maps using a commercial off the shelf (COTS) software package and place device icons on the map.

### Command Toolbar

#### The Command Toolbar shall allow a user to select a window for display.

#### The Command Toolbar shall always be displayed to the user.

#### The Command Toolbar shall only display valid commands.

### Device Control Window

#### Menu

##### The device control window shall display a three level menu allowing the operator to select the device to be commanded.

###### The first level shall be the device type selection: CMS, draw light, gate, pop-up, etc.

###### The second level shall be a list of specific devices of that type that are available to be commanded.

###### The third level shall be a list of available commands (if any) for the selected device.

##### Once the device type, device and command have been selected via the menu system the operator shall be presented with a form for the completion of any parameters for the command.

##### The device command completion form shall have a button labeled "Perform Action" to allow the operator to execute the command.

###### The "Perform Action" button shall be grayed out and unselectable until the device command form has been filled out.

###### The "Perform Action" button shall log the command submittal.

##### The device command completion form shall have a button labeled "Cancel Command" to allow the operator to stop the completion of the command.

#### Confirmation Dialog

##### Any device control action that involves human safety shall use a confirmation dialog to validate the action.

###### All device actions defined in the detailed design shall be classified as either involving human safety or not involving human safety.

###### The default classification shall be that the device action involves human safety.

##### The required validation method (if any) shall be displayed with the confirmation dialog.

##### The confirmation dialog shall specify the action and prompt the user for a *YES* or *NO* to continue.

##### The confirmation dialog shall default to *NO*.

#### The action and the confirmation shall be displayed in the System Log window.

#### The device control window shall display any returned device status resulting from the device control command.

#### If the requested device control command results in multiple steps at the field control level, the intermediate steps and their status shall be displayed in the device control window.

### Summary Device Status Window

#### The summary device status window shall display a text and graphic summary presentation on the status of the selected device or group of devices.

### Detailed Device Status Window

#### The detailed device status window shall display a text and graphic presentation on the status of the selected device or group of devices.

#### The detailed device status window shall allow a user to select more detailed status information on an individual device.

#### The operator shall be able to call up a device control window for any device shown on the device status window.

#### The summary device status window shall have a menu bar with File and Help as a minimum.

##### The File menu item shall include an option to open a command window for the selected device.

##### The File menu item shall include an option to open a detailed status window for the selected device.

##### The File menu item shall include an option to print the summary device status page.

##### The Help menu item shall activate the on-line help system.

#### The summary device status window shall display a list of all devices along with a miniature icon of the device color coded with the device status. The color-coding shall match the color-coding described above.

#### The summary device status window shall list the full name of each device.

#### The summary device status window shall list the most reason error code and description for the device if the device is failed or experiencing errors.

#### The summary device status window shall list the time and date of the last device status check.

### Incident Entry / Edit Window

This window shall enable the user to enter and edit an incident report
to displayed as an icon on the map window.

#### A user shall be able to enter information on an incident, including, location, description and time period.

#### A user shall be able to edit or close an existing incident.

#### Entry or editing of an incident shall be recorded in the Daily Diary along with the time and the user performing the entry.

#### The Incident Entry / Edit Window shall have a menu bar with File, Edit, Report, and Help.

##### The File menu item shall have an option to create a new incident entry.

##### The File menu item shall have an option to print the Incident Entry / Edit Window.

##### The Edit menu item shall have an option to append information to an incident entry.

##### The Edit menu item shall have an option to update the information on an incident entry.

##### The report menu shall have an option to print a report on all active incidents.

##### The report menu shall have an option to print a report on all entries associated with a specific incident.

##### The Help menu item shall invoke the Help system.

### Daily Diary Window

#### Operator command and confirmation actions shall be recorded in the Daily diary

#### The Daily Diary Window shall show the date and time of the entry.

#### The Daily Diary Window shall show the ID of the operator for each entry.

#### The Daily Diary Window shall provide a button (labeled Diary Entry) to activate a screen (Diary Entry) for the operator to make a Diary entry.

#### The Diary Entry screen shall provide the operator with a form to make an entry in the Daily Diary.

#### The current date, time and operator ID shall be displayed on the form in read-only display fields.

### Problem Work Order Window

#### The Problem Work Order Window shall allow the User to enter, modify and close information about a system failure.

##### The Problem Work Order Window shall have a menu bar with File, Edit, Report and Help.

###### The File menu item shall have an option to create a new system failure entry.

###### The File menu item shall have an option to print the Problem Work Order Window.

###### The File menu item shall have an option to close the Problem Work Order Window.

###### The Edit menu item shall have an option to add an update to an existing system failure.

###### The Report menu item shall include an option to print all entries associated with a specific device.

###### The Report menu item shall include an option to print a summary of all active system failures.

###### The Report menu item shall include an option to print all entries associated with a specific system failure.

### Scheduler Window

#### The Scheduler Window shall allow the user to enter, modify, delete and view information on events that affect the facility.

#### The user shall be able to search for specific events by date and type.

### Paging Contact Window

#### The Paging Contact Window shall allow an authorized user to enter, modify and delete a paging profile for various points of contact.

### Macro Editor Window

The Macro Editor will provide the operators with the ability to create
and modify macros and super-macros. A macro (or super macro) is a
sequence of device actions that are preconfigured by the user. The user
can activate the sequence of actions by invoking a single command. A
basic assumption for the execution of macros and super macros is that
the operator will be required to validate that an action has
successfully completed before the next action is started.

The user interface with the macro editor is to be based on the outline
editing capabilities of Microsoft Word 97.

#### The user shall select an existing macro to be edited or to define a new macro.

#### The operation being implemented shall determine which operations are permissible.

#### The Macro editor shall allow the user to insert a device action into a macro.

#### The Macro editor shall allow the user to delete a device action from a macro.

#### The operator shall be able to modify the order of the actions by selecting an action with the mouse and dragging the action to a new location in the macro.

#### The Macro editor shall allow the user to specify a security level on a macro.

#### The Macro editor shall allow the user to specify a minimum delay time between device actions.

#### The Macro editor shall allow the user to specify that operator confirmation is required prior to starting a device action.

#### The Macro editor shall allow the user to specify a valid time of activation for the macro.

#### The Macro editor shall allow the user to specify the expected amount of time an action will take to complete.

### Macro Control Window

#### The Macro Control Window shall provide a File entry on the menu bar.

#### The Macro Control Window shall provide an Open entry under the File entry on the menu bar.

#### The Macro Control Window shall provide a button (labeled Start) to start the macro.

#### The Macro Control Window shall provide a button (labeled Pause) to pause the macro execution.

#### The Macro Control Window shall provide a button (labeled Stop) to halt execution of the macro execution.

#### The Macro Control Window shall provide a button (labeled Next) to execute the next action in the sequence.

#### The Macro Control Window shall provide a counter showing the elapsed time since the macro execution was started.

### Logon Window

#### The Logon window shall enable a user to enter a user name and password.

#### The Logon Window will indicate to the user if the user name and password were accepted.

#### The Logon window shall allow the user to accept or reject command authority for the system.

### User Identification Window

#### The User Identification Window shall display the name of the user logged at this workstation, the location of the workstation, the name and location of the user with command control (the operator) and the date and time.

#### The User Identification Window shall always be displayed.

### User Administration Window

#### The User Administration Window shall allow a properly authorized operator to enter/modify/delete user names, passwords, user security level and use display preferences.

### Report Windows

#### The Report Windows shall allow the user to select and view reports generated by the system.

#### The Report Window shall allow the user to select the information to be included in a report format, including the time frame the report is to cover.

### Scenario Editor Window

Training users will use the Scenario Editor to create training scripts
for the simulator. These training scripts can be used to train new
operators in basic I-15 reversible lane operation. The training scripts
can also be used to train all staff in how to handle unusual situations.

#### The Scenario Editor shall provide the operator with the ability to create new scenarios.

#### The Scenario Editor shall provide the operator with the ability to modify existing scenarios.

#### The Scenario Editor shall provide the operator with the ability to define the state of all devices: operational, failed, unknown.

#### The Scenario Editor shall provide the operator with the ability to define equipment malfunctions by an offset time from the start of the scenario.

### Scenario Control Window

The Scenario Control Window shall allow the training user to control the
execution of a scenario. The Scenario Control Window must be versatile
in allowing the training user to start the scenario and then to control
the scenario as the scenario progresses.

#### The Scenario Control Window shall provide the training user the ability to start a scenario.

#### The Scenario Control Window shall provide the training user the ability to pause a scenario.

#### The Scenario Control Window shall provide the training user the ability to restart a scenario.

#### The Scenario Control Window shall provide the training user the ability to correct device malfunctions.

#### The Scenario Control Window shall provide the training user the ability to create device malfunctions.

#### The Scenario Control Window shall provide the training user the ability to see all commands issued by the trainee user.

### Help Window

#### The Help Window shall allow the user to request and display help information.

## Performance Requirements

The system performance requirements are specified in Paragraph 3.2.5 of
the System Requirements Document.

# Graphical User Interface Guidelines

## General Guidelines

### Icons

This section specifies that a set of icons will be defined and used by
the development team.

#### All icons shall be configurable to display a minimum of information as text with the icon.

##### The icons shall be configurable to display the text with relationship to the icon at the top, bottom, left or right.

#### All icons shall be configurable to display four colors: green, yellow, red, or gray

##### For all icons the color gray shall represent no data available, that is, communication with the device is not possible.

##### For all icons except the Loop Detector icon, the other colors shall represent the status of the device, with the color green indicating a working device, red indicating a failed device, and yellow indicating a partially failed device.

##### For the Loop Detector Icon, the meaning of the color of the icon is defined in 5.2.1.7.

### Form Entry

The following requirements shall be followed for all screens that use
defined forms to help the user enter data for the system.

#### The form shall open with the cursor in the top left entry field.

#### The TAB key shall move the cursor in a Z pattern from left to right and top to bottom through the fields of the form.

#### All form screens shall have a button on the screen to clear all user entry from the fields of the form. This button shall be labeled "CLEAR".

#### All form screens shall have a button on the screen to save the data entered into the fields of the form. This button shall be labeled "SAVE".

#### All form screens shall have a button on the screen to exit the form entry process. This button shall be labeled "EXIT".

### Field Validation

#### If a user entry must be one of several defined items, then the system shall present the user with the list of items from which to select the entry.

##### The form window shall be sized to display a minimum of 5 items from the selection list.

### Error Message Window

#### Error messages shall be displayed in a scrollable window.

#### The user shall be able to select the fields available for display in the error window.

#### The user shall be able to select the field for sorting the display in the error window.

#### The user shall be able to select the sort order for the display in the error window.

### Fonts

#### A maximum of 3 fonts shall be used in the user interface. These fonts shall be defined in the interface design.

#### A maximum of 4 font sizes shall be used in the user interface.

### Combination Boxes

#### A window combination box shall display a minimum of 4 items and a maximum of 9 items when it is expanded.

### Hot Keys

#### The *Ctrl-O* key combination shall execute the Open command in any window where Open is a valid action.

#### The *Ctrl-S* key combination shall execute the Save command in any window where Save is a valid action.

#### The *Ctrl-P* key combination shall execute the Print command in any window where Print is a valid action.

#### The *F1* key shall invoke the Help system.

### User Login

#### User login shall be controlled by the operating system.

### Window Configuration

#### When a user logs off of the system, the configuration of open windows shall be saved

#### When a user logs on to the system, the last saved configuration of open windows for that user shall be displayed.