1 / 38

Agenda

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

navid
Download Presentation

Agenda

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 3.1April 21, 2008

  2. Agenda SunGuide TRR Meeting

  3. Introductions SunGuide TRR Meeting

  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 TRR Meeting

  5. Current Project Status • Release 3.1 Development Complete • 172 Requirements • SwRI has been running in the lab for 4 weeks • SwRI has exercised the system • Unit testing • Ad hoc testing • Dry runs of the SICP SunGuide TRR Meeting

  6. Architecture: What Changed? SunGuide TRR Meeting

  7. Discuss Lab Configuration SunGuide TRR Meeting

  8. 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 TRR Meeting

  9. Test Hardware Layout Note: the details of the connection between D6 and FTE are not important for FAT SunGuide TRR Meeting

  10. Equipment for TestingUtilize NTCIP “simulators” SunGuide TRR Meeting

  11. 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 TRR Meeting

  12. Verify Turnpike Connectivity • Test cases require connectivity to the FTE middleware • Test for connectivity to FTE middleware through use of status logger • Sample of no connectivity • Sample of connectivity SunGuide TRR Meeting

  13. 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 TRR Meeting

  14. 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 TRR Meeting

  15. Test Case Example SunGuide TRR Meeting

  16. Review Test Procedures • IC-1: GUI (GUI) • IC-2: General Pricing (GP) • IC-3: Pricing Configuration (PC) • IC-4: Express Lanes Event Management (ELEM) • IC-5: Operational Scenarios (OPS) • IC-6: Toll Viewer (TV) • IC-7: Reporting (REP) SunGuide TRR Meeting

  17. General Discussion Questions About Test Cases? SunGuide TRR Meeting

  18. Quick Overview of Software • The following slides are provided to provide a very quick overview of the software, areas included are: • Administrative Editor (excerpts from Administrator Training) • Operator GUI • Before testing each integration case, general functionality of the “area under test” will be reviewed SunGuide TRR Meeting

  19. Express Lanes Configuration:System Wide Settings • Enter messages displayed during overrides • Set parameters used when activating an override SunGuide TRR Meeting

  20. Express Lanes ConfigurationHolidays / Special Events • Set days to be considered as holidays • Add single dates, or recurring dates • Recurring is a convenience for entry only: Dates are edited individually after creation SunGuide TRR Meeting

  21. Express Lanes Configuration:Segments • Create and manage segments for Express Lanes • Associate Toll Rate Signs with Segments • Displays can be marked as a Toll Gantry for this Segment SunGuide TRR Meeting

  22. Express Lanes Configuration:Daily Rate Schedule • Create and edit a Daily Rate Schedule • Schedule must always have at least a value starting at midnight • Given rates will go into effect at the start time when this schedule is used SunGuide TRR Meeting

  23. Express Lanes Configuration:Segment Rate Schedule • Create and edit a full Segment Rate Schedule • A Daily Rate Schedule must be selected for each day type • Schedule is applied to Segments; multiple Schedules can apply to a Segment • Segment will use the Schedule with the most recent start date SunGuide TRR Meeting

  24. Express Lanes Configuration:Toll Rate Signs • Create and edit Toll Rate Signs • Select DMSs to be used for this Sign • Set Static Text to be displayed in the GUI for each line • Set Segments used to calculate displayed rate SunGuide TRR Meeting

  25. Express Lanes Configuration:System Configuration File • In the configuration file (see the VDD for specifics) the following should be setup: • Toll Agency /Middleware: • Toll Agency Web Service URL • Toll Agency Response Alert Interval – time in between sending Middleware failure alerts • Toll Agency Heartbeat Interval – time in between SunGuide sending heartbeat (i.e. GetRate) requests to Middleware • Toll Agency Retry Count – maximum number of attempts to send SetRate requests to Middleware • Toll Agency Notify Delay – maximum time after the effective time of a rate change SunGuide can communicate a rate change to Middleware • Operational: • Non Time of Day (TOD) Alert Interval – time in between sending alert messages when segment is in override • DMS Resend Rate – time in between DMS resend attempts • DMS Max Resend – maximum number of attempts to resend a DMS message SunGuide TRR Meeting

  26. Express Lanes Tab SunGuide TRR Meeting

  27. Override Mode Dialog SunGuide TRR Meeting

  28. Alert Acknowledge Dialog SunGuide TRR Meeting

  29. Agenda SunGuide TRR Meeting

  30. Open Discussion SunGuide TRR Meeting

  31. Supplemental Slides: Will be used before each IC SunGuide TRR Meeting

  32. IC-1: GUI (GUI) • Purpose: verify the required functionality of the Express Lanes GUIs (tabbed, override and alerts). • Tests: • The overall tabbed GUI will be examined to verify all required data is present. • The override GUI will be examined to verify that all required controls are available and that all conditional fields are available/restricted as appropriate. • Integraiton with DMS will be verified. • Integration with Event Management will be verified. • Alerts generated by the Pricing Subsystem will be verified. SunGuide TRR Meeting

  33. IC-2: General Pricing (GP) • Purpose: verify required overall design of the Pricing Subsystem. • Tests: • Demonstrate the startup/restart mode of the Express Lanes module • Demonstrate the Express Lanes module communicates directly with the DMS subsystem bypassing MAS. • Demonstrate Express Lanes module is designed to accommodate growth and expansion of the Express Lanes project. SunGuide TRR Meeting

  34. IC-3: Pricing Configuration (PC) • Purpose: verify required functionality of the Administrative Editor with respect to configuring the behavior of the PS. • Tests: • Demonstrate the toll rate change delay parameters can be set using the Administrative Editor • Demonstrate the Administrative Editor can be used to set the Daily Rate Schedules. • Demonstrate the Administrative Editor can associate rate tables with segments. • Demonstrate Administrative Editor can edit types of days. • Demonstrate Administrative Editor can configure DMS associated with Express Lanes segments. • Demonstrate SunGuide Express Lanes module can manage rate schedules and coordinate Toll Rate DMS rate display and rate selection. • Demonstrate the Administrative Editor can change Operator Map parameters and permissions. • Demonstrate configuration of various Middleware Interface parameters. • Demonstrate Administrative Editor can be used to set the beginning and ending latitude and longitude of an Express Lanes segment. SunGuide TRR Meeting

  35. IC-4: Express Lanes Event Management (ELEM) • Purpose: verify the required functionality of special Express Lanes DMS w.r.t. EM response plans. • Tests: • Demonstrate that Toll Rate and Toll Gantry DMS do not behave as general DMSs with regards to Event Management. • Demonstrate the inclusion or exclusion of Lane Status DMS in EM response plans. SunGuide TRR Meeting

  36. IC-5: Operational Scenarios (OPS) • Purpose: verify the required functionality of the PS with respect to posting of toll rates to signs and the FTE middleware. • Tests: • Demonstrate the Express Lanes module posts messages to DMS correctly. • Demonstrate general behavior of the Express Lanes module with respect to rate posting. • Demonstrate Express Lanes module selects the correct toll rate when in Open/Normal Rate mode. • Demonstrate Express Lanes module behavior when in Closed or Open/Zero override mode. • Demonstrate Express Lanes module behavior when in Open/Manual Rate override mode. • Demonstrate Express Lanes module behavior when entering, operating, or leaving Open/Congested override mode. • Demonstrate Express Lanes communication with the FTE Middleware. SunGuide TRR Meeting

  37. IC-6: Toll Viewer (TV) • Purpose: verify the required functionality of the Toll Viewer. • Tests: • Demonstrate that the summary view of the Toll Viewer application. • Demonstrate the display of events in the Toll Viewer application. • Demonstrate the detail display mode in the Toll Viewer application. • Demonstrate the Toll Viewer displays data in chronological order. • Demonstrate the deployment configuration of the Toll Viewer application through a firewall. SunGuide TRR Meeting

  38. IC-7: Reporting (REP) • Purpose: verify the required functionality of the DA with respect to storage of PS actions. • Tests: • Demonstrate the Express Lanes module tracks changes to configuration parameters and stores operational data. • Dummy reports will be generated SunGuide TRR Meeting

More Related