1 / 39

Introductions

SunGuide TM Software Development Project Test Readiness Review (TRR) Meeting for SunGuide Release 4.0 August 18, 2008. Introductions. Agenda. Logistics. Test location: ITS Demo Lab Breaks: Rolling Lunch SwRI Cafeteria Internet: Available in the lobby (100baseT connection). Restrooms.

jaegar
Download Presentation

Introductions

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SunGuideTM Software Development ProjectTest Readiness Review (TRR) Meeting for SunGuide Release 4.0August 18, 2008

  2. Introductions SunGuide 4.0 TRR

  3. Agenda SunGuide 4.0 TRR

  4. Logistics • Test location: • ITS Demo Lab • Breaks: • Rolling • Lunch • SwRI Cafeteria • Internet: • Available in the lobby (100baseT connection) Restrooms Restrooms Demo Lab Lobby Restrooms SunGuide 4.0 TRR

  5. Current 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 SunGuide 4.0 TRR

  6. Architecture: What Changed? 511 Removed SunGuide 4.0 TRR

  7. Test Hardware Layout SunGuide 4.0 TRR

  8. Discuss Lab Configuration SunGuide 4.0 TRR

  9. Discuss Lab Configuration :SwRI Server Farm • SAN: • Two drive bays • 6 fiber connected hosts • FAT: • Two DL380s: • Laplace • Pythagoras • Development: • Six DL380s • Eight DL370s SunGuide 4.0 TRR

  10. Environment 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 SunGuide 4.0 TRR

  11. Discuss 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” SunGuide 4.0 TRR

  12. How 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 SunGuide 4.0 TRR

  13. Test Case Example SunGuide 4.0 TRR

  14. Review 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) SunGuide 4.0 TRR

  15. General Discussion Questions About Test Cases? SunGuide 4.0 TRR

  16. Open Discussion SunGuide 4.0 TRR

  17. Agenda SunGuide 4.0 TRR

  18. Florida Statewide 511 System ConceptFrom FDOT Data Fusion Requirements Document SunGuide 4.0 TRR

  19. FLATIS Functional SubsystemsFrom FDOT Data Fusion Requirements Document • DFS provides data to IDS via C2C • SunGuide data and other local and district sources SunGuide 4.0 TRR

  20. Release 4.0 and FL-ATIS Responsibilities • 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 SunGuide 4.0 TRR

  21. C2C Infrastructure Concept:Deploying a C2C “Cloud” SunGuide 4.0 TRR

  22. How SunGuide Data gets to 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 SunGuide 4.0 TRR

  23. R4.0 Conceptual Data Flow SunGuide 4.0 TRR

  24. Providing Data to Other “Consumers” (3rd 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 4.0 TRR

  25. SunGuide Event Processing SunGuide 4.0 TRR

  26. Weather Processing SunGuide 4.0 TRR

  27. External Events Note: “nearby” distance is configurable SunGuide 4.0 TRR

  28. Restricting Publishing of Events • Operator can determine if an event is published to FL-ATIS: SunGuide 4.0 TRR

  29. Floodgate 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 SunGuide 4.0 TRR

  30. Floodgate - continued • Each floodgate: two audio recordings, two text entries • Each banner: two text entries SunGuide 4.0 TRR

  31. Floodgate - 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 SunGuide 4.0 TRR

  32. DMS Processing SunGuide 4.0 TRR

  33. CCTV Processing SunGuide 4.0 TRR

  34. Travel 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) SunGuide 4.0 TRR

  35. SAE Code Interpretation • SAE Description is updated whenever Event is “Saved”. SunGuide 4.0 TRR

  36. Event Management:Configuration Screens – 4.0 Changes • View the Configuration of (note these are view only as of Release 4.0 due to FLATIS): • Event type SunGuide 4.0 TRR

  37. Event Management:Configuration 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 SunGuide 4.0 TRR

  38. Test Data Sources • Two sources of data: • SwRI Test Data feed (FULL feed available since May 16) • XML Tester (a ‘controlled’ tool) SunGuide 4.0 TRR

  39. Agenda SunGuide 4.0 TRR

More Related