SunGuideSunGuideTMTM Software Development Project Software Development Project

Test Readiness Review (TRR) MeetingTest Readiness Review (TRR) MeetingNovember 27, 2007November 27, 2007

November 27, 2007SunGuide TRR Meeting 2

AgendaAgenda

Time Item Lead

8:00 – 8:15 Introductions Tillander

8:15 – 8:25 Logistics District 4

8:25 – 8:45 Discuss Project Status Robert Heller /John Boguslawski

8:45 – 9:00 Hardware / Lab ConfigurationTesting ProcessTest ProceduresDeferred Test Cases

Robert Heller /John Boguslawski

9:00 – 9:15 Open Discussion All

November 27, 2007SunGuide TRR Meeting 3

Introductions

November 27, 2007SunGuide TRR Meeting 4

AgendaAgenda

Time Item Lead

8:00 – 8:15 Introductions Tillander

8:15 – 8:25 Logistics District 4

8:25 – 8:45 Discuss Project Status Robert Heller /John Boguslawski

8:45 – 9:00 Hardware / Lab ConfigurationTesting ProcessTest ProceduresDeferred Test Cases

Robert Heller /John Boguslawski

9:00 – 9:15 Open Discussion All

November 27, 2007SunGuide TRR Meeting 5

LogisticsLogistics

District 4 staff will discuss:– Test area– Resources available

November 27, 2007SunGuide TRR Meeting 6

AgendaAgenda

Time Item Lead

8:00 – 8:15 Introductions Tillander

8:15 – 8:25 Logistics District 4

8:25 – 8:45 Discuss Project Status Robert Heller /John Boguslawski

8:45 – 9:00 Hardware / Lab ConfigurationTesting ProcessTest ProceduresDeferred Test Cases

Robert Heller /John Boguslawski

9:00 – 9:15 Open Discussion All

November 27, 2007SunGuide TRR Meeting 7

Current Project Status:Current Project Status:From a Development PerspectiveFrom a Development Perspective

Solid:– 511– VSL– CE– AD CCTV Driver– EV– Web Server– EM– RS– AVL/RR– IDS– ODS– RPG

What is not ready:– Some Responder Audit screens (2 of 7 are not complete)

November 27, 2007SunGuide TRR Meeting 8

Responder Audit RequirementsResponder Audit RequirementsSome will not be tested this weekSome will not be tested this week

SunGuide Req. ID Requirement

EM011The responder audit function shall provide the capability to add, delete, or edit responder

agency timeline, vehicle response timeline, and responder activity data in the SunGuide database.

EM001UAll operator changes shall be logged in the database for traceability, including the new

value, previous value, the user who made the change, and the time the change was made.

EM002U All operator changes shall be displayed in the chronology report with an indication that specific information has been changed.

EM003U The operator shall be able to run a report using the SunGuide report function to review changes made and logged by the audit function.

EM004UThe operator shall have at least three ways to select an event: (1) by typing in the event

number directly; or (2) selecting from the list of active events, or (3) selecting from a filtered list of all events.

EM004U1 The operator shall be able to filter events by month, location, type, blockage, or responding agency involved.

EM020GA Responder Audit screen shall be incorporated into the existing audit feature of the

SunGuide GUI, using the existing permissions scheme and user authentication methods of the SunGuide GUI.

EM020G1 The operator shall be able to add, delete, or edit agency notification, on-scene, and departure times.

EM020G2 The operator shall be able to leave any of the fields blank in case that information is not available, except that a record must have at least one timestamp entered.

EM020G3 The operator shall be able to add, delete, or edit vehicle response records for agencies with responding vehicles (Road Ranger, SIRV, etc.).

November 27, 2007SunGuide TRR Meeting 9

Responder Audit RequirementsResponder Audit RequirementsSome will not be tested this week - continuedSome will not be tested this week - continued

SunGuide Req. ID Requirement

EM020G4 The operator shall be required to provide the notification time and either the arrival and departure times or the cancellation time.

EM020G5 The operator shall be able to add, edit, and delete activity records associated with vehicle response records.

EM020G6The software shall require the operator to enter the time that an activity was performed,

however the software shall also require the timestamp to fall within the arrival and departure timestamps for the vehicle record.

EM020G7 The GUI shall warn the user when a timestamp is entered which is earlier than the event start time or later than the event closed time.

EM020G8 The operator shall have the option to enter a quantity associated with an activity, such as gas, when the activity is configured as "quantifiable".

EM020G9 The GUI shall display a summary of all the agency response times, the detailed vehicle response time records, and all the activities performed.

EM020G10 The GUI shall display the event location, event number, and blockage history for an event.

EM020G11 The GUI shall provide an event chronology summary window with the ability to generate a report.

EM021G A comments field shall be provided for the operator to enter free-text data.

EM012 Activities shall be classified in the software as quantifiable or not.

November 27, 2007SunGuide TRR Meeting 10

Forward Looking ScheduleForward Looking Schedule

IV&V – TERL (FDOT/PBS&J led activity):– Dry Run: Nov 26 – Nov 30– Actual Test: Dec 3 – Dec 7

Installs:– Nov 26: TERL– Nov 12-26: D4– Dec 3-7 : D5– Dec 3-7 : D6– Dec 10-14: D2 (may start early)– Dec 10-14 : D7 (may start early)

November 27, 2007SunGuide TRR Meeting 11

AgendaAgenda

Time Item Lead

8:00 – 8:15 Introductions Tillander

8:15 – 8:25 Logistics District 4

8:25 – 8:45 Discuss Project Status Robert Heller /John Boguslawski

8:45 – 9:00 Hardware / Lab ConfigurationTesting ProcessTest ProceduresDeferred Test Cases

Robert Heller /John Boguslawski

9:00 – 9:15 Open Discussion All

November 27, 2007SunGuide TRR Meeting 12

Purpose of TRR / FATPurpose of TRR / FAT

Purpose:– Review preparations for testing– Walk through the test procedures at a very high level and

determine if anyone has any comments

Ground Rules:– Testing will not depart from the written procedures– Any requested “ad hoc” testing will occur after the formal testing

process– Re-writing of requirements / scope additions will be captured for

future consideration

Approvals:– FDOT/SwRI will witness each test case (on “Master SICP”)– At the conclusion, FDOT will sign SICP cover page to acknowledge

all tests were executed as written/noted in the “Master SICP”

November 27, 2007SunGuide TRR Meeting 13

Hardware ConfigurationHardware Configuration

District 4 staff to describe hardware environment

November 27, 2007SunGuide TRR Meeting 14

Release 3.0 Integration CasesRelease 3.0 Integration Cases

IC-1: Configuration Editor (CE) IC-2: Variable Speed Limit (VSL) IC-3: American Dynamics Closed Circuit Television (AD CCTV) Driver IC-4: 511 (511) IC-5: Web Server (WS) IC-6: Automatic Vehicle Location (AVL)/Road Ranger (RR) IC-7: Incident Detection Subsystem (IDS) IC-8: Event Management (EM) (includes Responder Audit) IC-9: Response Plan Generation (RPG) IC-10: Reporting Subsystem (RS) IC-11: Event Viewer (EV) IC-12: Operational Data Store (ODS) IC-13: General Subsystem Updates (GEN)

November 27, 2007SunGuide TRR Meeting 15

FAT 3 LimitationsFAT 3 Limitations

Two of the Responder Audit screens have not been completed (5 are available for testing)

Comment: D5 has an install (and using operationally) the following R3.0 components:– 511– AD CCTV Driver– VSL– Web Server– Release 3.0 core components (C2C, GUI, MAS,

Data Bus, TSS)

November 27, 2007SunGuide TRR Meeting 16

Test Case ExampleTest Case Example

November 27, 2007SunGuide TRR Meeting 17

Questions About Test Cases?

November 27, 2007SunGuide TRR Meeting 18

AgendaAgenda

Time Item Lead

8:00 – 8:15 Introductions Tillander

8:15 – 8:25 Logistics District 4

8:25 – 8:45 Discuss Project Status Robert Heller /John Boguslawski

8:45 – 9:00 Hardware / Lab ConfigurationTesting ProcessTest ProceduresDeferred Test Cases

Robert Heller /John Boguslawski

9:00 – 9:15 Open Discussion All

November 27, 2007SunGuide TRR Meeting 19

Open Discussion