SunGuide TM Software Development Project Test Readiness Review (TRR) Meeting October 1, 2007

1. SunGuideTM Software Development ProjectTest Readiness Review (TRR) MeetingOctober 1, 2007

2. Agenda SunGuide TRR Meeting

3. Introductions SunGuide TRR Meeting

4. Agenda SunGuide TRR Meeting

5. 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

6. Agenda SunGuide TRR Meeting

7. Development Cycle • Design => Unit Test => Integration Test => FAT • Some subsystems create a “chicken and egg” problem: • EM is one of “those” • Other subsystems rely on EM and cannot be completed until EM is “solid” • EM Development schedule: • Initially due to SwRI 4 weeks prior to FAT-1 (4 weeks would allow SwRI to integrate all SwRI developed subsystems) • Revised schedule (established during FAT-1): • Code drop due Sep 17 to SwRI • Final code drop due Sep 24 to SwRI • Running EM (database and subsystem) did not occur until Sep 27 • As of Sep 30th (noon) we have yet to get a script to upgrade the EM database (script for other subsystems exists) SunGuide TRR Meeting

8. Current Project Status:From a Development Perspective • Solid: • 511 • VSL • CE • AD CCTV Driver • EV • Web Server • General • Testing completed, needs final integration testing: • AVL/RR • IDS • RPG • ODS (Reports testing, generating via RS is new) • RS • Basic integration testing completed but additional development and testing needed: • EM SunGuide TRR Meeting

9. Current Project Status:From a Development Perspective - continued • Why was the install not working in TERL and D4: • Installer was current and worked fine • Database upgrade script (EM components) did NOT work and significant manual work was/is required • What is not ready: • Responder Audit Requirements (see next slide) • Database upgrade scripts for EM • SUM (EM and RS sections) • Final integration of EM related components SunGuide TRR Meeting

10. Responder Audit RequirementsWill not be tested this week SunGuide TRR Meeting

11. Responder Audit RequirementsWill not be tested this week - continued SunGuide TRR Meeting

12. Forward Looking Schedule(dates from currently published schedule) • IV&V – TERL (FDOT/PBS&J led activity): • Dry Run: Oct 10-16 • Actual Test: Oct 16-19 • Operating Training Material: Oct 3, 2007 • Installs: • Sep 25-28: • D4 • TERL • Oct 15-16: D2 • Oct 22-25: D5 • Oct 22-25: D6 • Oct 29-30: D7 SunGuide TRR Meeting

13. Project Status • Still waiting from IBI: • Dates for: • When SUM input will be provided • When Responder Audit will be completed • When EM database scripts will be completed • SwRI activities: • Final integration testing once final products are received • Timeframe objective: to have completed by IV&V • Discussion / comments ??? SunGuide TRR Meeting

14. Agenda SunGuide TRR Meeting

15. Purpose 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” SunGuide TRR Meeting

16. SunGuide TRR Meeting

17. SwRI Server Farm • SAN: • Two drive bays • 6 fiber connected hosts • FAT: • Four DL380s • Development: • Six DL380s • Eight DL370s SunGuide TRR Meeting

18. Hardware Configuration SunGuide TRR Meeting

19. 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) Release 3.0 Integration Cases SunGuide TRR Meeting

20. FAT 2 Limitations • Testing activities that require Event Management (EM) are not 100% integration tested (e.g. AVL/RR, IDS, RPG “may” have issues) • 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) SunGuide TRR Meeting

21. Schedule for Testing SunGuide TRR Meeting

22. Test Case Example SunGuide TRR Meeting

23. Questions About Test Cases? SunGuide TRR Meeting

24. 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, 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

25. Tests for FootPrints Issues • On the last days test for the following FootPrints issues will be performed (not in the SICP): • #134: Ability to convert non-TSS link to TSS link • #225: SAS subsystem requires restart • #254: Refresh geometry button on Video Wall Control Dialog not working • #258: preferences lost • #295: TvT needs to be restarted for new template SunGuide TRR Meeting

26. Automated Build Tool:Recommendation from last PCA – “push a button” SunGuide TRR Meeting

27. Agenda SunGuide TRR Meeting

28. Open Discussion SunGuide TRR Meeting