Introductions

SunGuideSunGuideTMTM Software Development Project Software Development Project

Test Readiness Review (TRR) Meeting for Test Readiness Review (TRR) Meeting for SunGuide Release 4.0SunGuide Release 4.0

August 18, 2008August 18, 2008

August 18, 2008 1

August 18, 2008SunGuide 4.0 TRR 2

Introductions


AgendaAgendaDate / Time Item Lead

August 18

8:30 – 9:30

Test Readiness Review (TRR) Meeting:Discuss project statusDiscuss testing processReview test proceduresDiscuss lab configurationOpen discussion

Dellenback

Robert Heller

August 18

9:30 – 10:30

Detailed Discussion of Center-to-Center:How it worksHow is being used in Release 4.0

Steve Dellenback

August 18

10:30 – 11:30

IC-1: Admin Editor (AE)

IC-2: Configuration (CFG)SwRI Team

August 18

1:00 – 5:00

IC-3: Events (EV)

IC-4: SAE Codes (SAE)

IC-5: Alternate Roads (ALT)

IC-6: Video (VID)

SwRI Team

August 19

8:30 – 12:00

IC-7: Floodgates (FG)

IC-8: Center-to-Center (C2C)SwRI Team

August 19

1:00 – 5:00

IC-9: Reporting (REP)

IC-10: Database (DBASE)

IC-11: Miscellaneous (MISC)

SwRI Team

August 20

8:00 – 9:00Retest / revisit open issues SwRI Team

August 20

9:00 – 11:00

Wrap up discussions:FL-ATIS FAT and IV&VDeployment activities planned

John Bonds

All

August 20

11:00 – 11:30Preview of Release 4.1 (Travel Time) GUIs SwRI Team


LogisticsLogistics

Test location:– ITS Demo Lab

Breaks:– Rolling

Lunch– SwRI Cafeteria

Internet:– Available in the lobby

(100baseT connection)

Restrooms

Restrooms

Restrooms

Lobby

Demo Lab


Current Project StatusCurrent Project Status

Release 4.0 Development Complete

115 Requirements

SwRI has been running:

– Data stream to the FL-ATIS team for over 12 weeks

– In the lab for 3 weeks

SwRI has exercised the system

– Unit testing

– Ad hoc testing

– Dry runs of the SICP


Architecture: What Changed?Architecture: What Changed?

511 Removed


Test Hardware LayoutTest Hardware Layout


Discuss Lab ConfigurationDiscuss Lab Configuration


Discuss Lab Configuration :Discuss Lab Configuration :SwRI Server FarmSwRI Server Farm

SAN:– Two drive bays– 6 fiber connected

hosts

FAT:– Two DL380s:

• Laplace• Pythagoras

Development:– Six DL380s– Eight DL370s


Environment NoteEnvironment Note

Note that SwRI has both “real” equipment and simulators in the lab

There are times that the simulators “mis-behave” and we find ourselves “re-testing” to achieve the results

The “re-tests” do NOT require software modifications

For example, one time a drunk driver took out the power (actually causing a short on the power lines and toasted a number of devices such as voice mail) to SwRI and the Cortec Codecs have never been the same.

SwRI has other project’s that will occasionally (accidentally) “hit” our development devices


Discuss Testing ProcessDiscuss Testing Process

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”


How Testing Will OccurHow Testing Will Occur

For each Integration Case (IC):

– SwRI will explain the objective of the IC

– Requirements will be reviewed

– A “reader” will walk through each test case (see next slide for an ‘example’ test case)

– An “operator” will perform the GUI actions

– Results will be captured

– Note: Enhancements will be captured for future review by FDOT


Test Case ExampleTest Case Example


Review Test ProceduresReview Test Procedures

IC-1: Admin Editor (AE) IC-2: Configuration (CFG) IC-3: Events (EV) IC-4: SAE Codes (SAE) IC-5: Alternate Roads (ALT) IC-6: Video (VID) IC-7: Floodgates (FG) IC-8: Center-to-Center (C2C) IC-9: Reporting (REP) IC-10: Database (DBASE) IC-11: Miscellaneous (MISC)


General DiscussionGeneral Discussion

Questions About Test Cases?


Open Discussion



August 18

8:30 – 9:30


Dellenback

Robert Heller

August 18

9:30 – 10:30


Steve Dellenback

August 18

10:30 – 11:30



August 18

1:00 – 5:00

IC-3: Events (EV)



IC-6: Video (VID)

SwRI Team

August 19

8:30 – 12:00



August 19

1:00 – 5:00




SwRI Team

August 20


August 20

9:00 – 11:00


John Bonds

All

August 20



Florida Statewide 511 System ConceptFlorida Statewide 511 System ConceptFrom FDOT Data Fusion Requirements DocumentFrom FDOT Data Fusion Requirements Document


FLATIS Functional SubsystemsFLATIS Functional SubsystemsFrom FDOT Data Fusion Requirements DocumentFrom FDOT Data Fusion Requirements Document

DFS provides data to IDS via C2C

SunGuide data and other local and district sources


Release 4.0 and FL-ATIS Release 4.0 and FL-ATIS ResponsibilitiesResponsibilities

SunGuide C2C is the “transport mechanism” If other agencies (e.g. OOCEA) wish to provide data it

MUST comply with the SunGuide C2C interface requirements


C2C Infrastructure Concept:C2C Infrastructure Concept:Deploying a C2C “Cloud”Deploying a C2C “Cloud”

How SunGuide Data gets to How SunGuide Data gets to FL-ATIS…FL-ATIS…

Data:– In general, as SunGuide updates data it is immediately transmitted to

the C2C– C2C pushes data to a receiver’s plugin, from there, the processing of

the data is the burden of the receiver Data Format:

– Specified in the SunGuide Center-to-Center Interface Control Document (ICD), last published on July 25, 2008


R4.0 Conceptual Data FlowR4.0 Conceptual Data Flow


Providing Data to Other Providing Data to Other “Consumers” (3“Consumers” (3rdrd Parties) Parties)

C2C:

– Is the “method” SunGuide uses to transmit data outside the “domain” of a SunGuide deployment.

– Was built using the available ITS Standards produced by NEMA, AASHTO, and ITE.

The 3rd party feed identified in FDOT DFS document will be a “C2C feed”. C2C ICD:

– Has been published (this describes how to access the data).

– To access the data feed a program has to be developed that access the web service that provides data in XML format (see the C2C ICD).

– Suggestion to develop an application that simply deposits the data every ‘x’ minutes onto a FTP server has been made.

Note: the www.fl511.com developed for Release 3.0 used C2C as the source for data.


SunGuide Event ProcessingSunGuide Event Processing


Weather ProcessingWeather Processing


External EventsExternal Events


Note: “nearby” distance is configurable

Restricting Publishing of EventsRestricting Publishing of Events

Operator can determine if an event is published to FL-ATIS:


Floodgate ProcessingFloodgate Processing


FDOT provided an Excel spreadsheet with all possible Floodgate combinations

Converted to XML file by FDOT SunGuide uses XML file which allows a “soft” configuration

– any changes to the file need to be SIMULTANEOUSLY coordinated across SG deployments and FL-ATIS

Floodgate - continuedFloodgate - continued

Each floodgate: two audio recordings, two text entries Each banner: two text entries


Floodgate - continuedFloodgate - continued

Status:– Retrieved from the FL-ATIS C2C plugin database (THIS IS THE SOURCE

FOR FLOODGATE STATUS)– Sent to C2C for distribution– Transmitted to each deployment “subscribed” for Floodgate status data– Selecting banner/message takes operator back to “entry” screen so edits

can easily performed


DMS ProcessingDMS Processing


CCTV ProcessingCCTV Processing


Travel Time / Traffic ConditionsTravel Time / Traffic Conditions

TSS generated “link” data published as available (e.g. a lot of detectors implies a lot of C2C data)

TvT (Travel Time) data published at the rate of a “tunable” TvT parameter (e.g. C2C publishes as it arrives)


SAE Code InterpretationSAE Code Interpretation

SAE Description is updated whenever Event is “Saved”.


SunGuide 4.0 TRR 36

Event Management:Event Management:Configuration Screens – 4.0 ChangesConfiguration Screens – 4.0 Changes

View the Configuration of (note these are view only as of Release 4.0 due to FLATIS):

– Event type

August 18, 2008

SunGuide 4.0 TRR 37

Event Management:Event Management:Configuration Screens – 4.0 ChangesConfiguration Screens – 4.0 Changes

View the Configuration of (note these are view only as of Release 4.0 due to FLATIS):

– Vehicle tracking: vehicle types

August 18, 2008

Test Data SourcesTest Data Sources

Two sources of data:– SwRI Test Data feed (FULL feed available since May 16)

– XML Tester (a ‘controlled’ tool)




August 18

8:30 – 9:30


Dellenback

Robert Heller

August 18

9:30 – 10:30


Steve Dellenback

August 18

10:30 – 11:30



August 18

1:00 – 5:00

IC-3: Events (EV)



IC-6: Video (VID)

SwRI Team

August 19

8:30 – 12:00



August 19

1:00 – 5:00




SwRI Team

August 20


August 20

9:00 – 11:00


John Bonds

All

August 20


Date post:	07-Jan-2016
Category:	Documents
Upload:	jaegar
View:	20 times
Download:	0 times

Introductions

Documents