SunGuide TM Software Development Project Test Readiness Review (TRR) Meeting August 27, 2007

1. SunGuideTM Software Development ProjectTest Readiness Review (TRR) MeetingAugust 27, 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. Project Schedule • Notice to proceed: • March 7, 2007 • Design Reviews: • May 2-3, 2007 (iFlorida) • May 8-9, 2007 (EM / RS / AVL/RR / IDS) • Follow-up Design Reviews: • May 22, 2007 (iFlorida) • May 31, 2007 (EM / RS / AVL/RR / IDS) • FAT schedule: • Initial: week of August 6, 2007 • After design reviews: week of August 27, 2007 • During integration: • Week of August 27, 2007 • Week of September 24, 2007 (EM, RS, AVL/RR, IDS) SunGuide TRR Meeting

8. Forward Looking Schedule(dates tentative until FDOT approved) • FAT 2: • Week of Sep 24th (at SwRI) • IV&V – TERL (FDOT/PBS&J led activity): • Week of October 8th • Installs: • Week of Oct 15: • D4 • Week of Oct 22: • D5 • D6 • Week of Oct 29: • D2 • D7 SunGuide TRR Meeting

9. Why the Schedule Slippage • Remember – its always easy to look backwards and figure out why something “went wrong” • SwRI and IBI have developed a very strong working relationship: • Mutual respect among developers • PMs have learned how “to work together” • Combined team / skills is extremely strong • Number of FDOT provided requirements / schedule: • Release 1.x: 280 16 months • Release 2.x: 278 13 months (some overlay w/R1.x) • Release 3: 607 6 months • The FDOT expressed functionality in the Design Reviews was not captured in the requirements (which is what schedule was based on) SunGuide TRR Meeting

10. Why the Schedule Slippage:Continued • SwRI/IBI significantly underestimated the effort associated with our joint design efforts (especially ICD creation and finalization): • Took many weeks longer than anticipated • We should have had our developers finalize this document much sooner after NTP • IBI significantly underestimated the effort associated with developing architecturally compliant SunGuide GUIs • The EM GUI screens are some of the most complex in SunGuide • The impact of the underestimation was considerable. This will be factored into future estimates • In retrospect, the development team should not have taken on the additional 'responder audit' related requirements without requesting an extension • SwRI/IBI significantly underestimated the effort associated with joint software integration: • Extensive subsystem interdependency (EM, AVL/RR, RS, EV) slowed the pace of integration much more than anticipated. • Schedule was very aggressive from the beginning SunGuide TRR Meeting

11. Agenda SunGuide TRR Meeting

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

13. SunGuide TRR Meeting

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

15. Hardware Configuration SunGuide TRR Meeting

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

17. FAT 1 Limitations • Testing activities that require Event Management (EM) are limited • Test cases pertaining to iFlorida can be mostly passed (other than the EM implications) • Comment: D5 has an “early install” of: • 511 • AD CCTV Driver • VSL • Web Server • Release 3.0 core components (C2C, GUI, MAS, Data Bus, TSS) SunGuide TRR Meeting

18. Schedule for Testing SunGuide TRR Meeting

19. Test Case Example SunGuide TRR Meeting

20. Questions About Test Cases? SunGuide TRR Meeting

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

22. Agenda SunGuide TRR Meeting

23. FCA Results • Performed by Walt Townsend on August 27, 2007 • Activities: • Verify that VDD is correct and accurately describes the release • Verify that configuration management processes have been followed (software is stored correctly in the repository; and software to be tested has been built from the repository) • Verify that the physical setup of the test environment is sufficient to validate the requirements (make sure that I/O test devices are really connected as described, etc.) • Verify that the test environment is correctly described in the test Document SunGuide TRR Meeting

24. Agenda SunGuide TRR Meeting

25. Open Discussion Review Agenda SunGuide TRR Meeting