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

October 1, 2007SunGuide TRR Meeting 2 Agenda TimeItem Lead 8:30 – 8:35Introductions 8:35 – 8:40Logistics Steve Dellenback 8:40 – 9:00Discuss Project Status Steve Dellenback / Robert Heller / John Boguslawski 9:00 – 9:15Hardware / Lab Configuration Testing Process Test Procedures Deferred Test Cases Build Tool Steve Dellenback / Robert Heller 9:15 – 9:30Open Discussion All

October 1, 2007SunGuide TRR Meeting 3 Introductions

October 1, 2007SunGuide TRR Meeting 4 Agenda TimeItem Lead 8:30 – 8:35Introductions 8:35 – 8:40Logistics Steve Dellenback 8:40 – 9:00Discuss Project Status Steve Dellenback / Robert Heller / John Boguslawski 9:00 – 9:15Hardware / Lab Configuration Testing Process Test Procedures Deferred Test Cases Build Tool Steve Dellenback / Robert Heller 9:15 – 9:30Open Discussion All

October 1, 2007SunGuide TRR Meeting 5 Logistics Test location: –ITS Demo Lab Breaks: –Rolling Lunch –SwRI Cafeteria Internet: –Available in the lobby (100baseT connection) Restrooms Lobby Demo Lab

October 1, 2007SunGuide TRR Meeting 6 Agenda TimeItem Lead 8:30 – 8:35Introductions 8:35 – 8:40Logistics Steve Dellenback 8:40 – 9:00Discuss Project Status Steve Dellenback / Robert Heller / John Boguslawski 9:00 – 9:15Hardware / Lab Configuration Testing Process Test Procedures Deferred Test Cases Build Tool Steve Dellenback / Robert Heller 9:15 – 9:30Open Discussion All

October 1, 2007SunGuide 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 30 th (noon) we have yet to get a script to upgrade the EM database (script for other subsystems exists)

October 1, 2007SunGuide 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

October 1, 2007SunGuide 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

October 1, 2007SunGuide TRR Meeting 10 Responder Audit Requirements Will not be tested this week SunGuide Req. IDRequirement EM011 The responder audit function shall provide the capability to add, delete, or edit responder agency timeline, vehicle response timeline, and responder activity data in the SunGuide database. EM001U All operator changes shall be logged in the database for traceability, including the new value, previous value, the user who made the change, and the time the change was made. EM002U All operator changes shall be displayed in the chronology report with an indication that specific information has been changed. EM003U The operator shall be able to run a report using the SunGuide report function to review changes made and logged by the audit function. EM004U The operator shall have at least three ways to select an event: (1) by typing in the event number directly; or (2) selecting from the list of active events, or (3) selecting from a filtered list of all events. EM004U1 The operator shall be able to filter events by month, location, type, blockage, or responding agency involved. EM020G A Responder Audit screen shall be incorporated into the existing audit feature of the SunGuide GUI, using the existing permissions scheme and user authentication methods of the SunGuide GUI. EM020G1 The operator shall be able to add, delete, or edit agency notification, on-scene, and departure times. EM020G2 The operator shall be able to leave any of the fields blank in case that information is not available, except that a record must have at least one timestamp entered. EM020G3 The operator shall be able to add, delete, or edit vehicle response records for agencies with responding vehicles (Road Ranger, SIRV, etc.).

October 1, 2007SunGuide TRR Meeting 11 Responder Audit Requirements Will not be tested this week - continued SunGuide Req. IDRequirement EM020G4 The operator shall be required to provide the notification time and either the arrival and departure times or the cancellation time. EM020G5 The operator shall be able to add, edit, and delete activity records associated with vehicle response records. EM020G6 The software shall require the operator to enter the time that an activity was performed, however the software shall also require the timestamp to fall within the arrival and departure timestamps for the vehicle record. EM020G7 The GUI shall warn the user when a timestamp is entered which is earlier than the event start time or later than the event closed time. EM020G8 The operator shall have the option to enter a quantity associated with an activity, such as gas, when the activity is configured as "quantifiable". EM020G9 The GUI shall display a summary of all the agency response times, the detailed vehicle response time records, and all the activities performed. EM020G10The GUI shall display the event location, event number, and blockage history for an event. EM020G11 The GUI shall provide an event chronology summary window with the ability to generate a report. EM021GA comments field shall be provided for the operator to enter free-text data. EM012Activities shall be classified in the software as quantifiable or not.

October 1, 2007SunGuide TRR Meeting 12 Forward Looking Schedule (dates from currently published schedule) IV&V – TERL (FDOT/PBS&J led activity): –Dry Run: Oct –Actual Test: Oct 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

October 1, 2007SunGuide 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 ???

October 1, 2007SunGuide TRR Meeting 14 Agenda TimeItem Lead 8:30 – 8:35Introductions 8:35 – 8:40Logistics Steve Dellenback 8:40 – 9:00Discuss Project Status Steve Dellenback / Robert Heller / John Boguslawski 9:00 – 9:15Hardware / Lab Configuration Testing Process Test Procedures Deferred Test Cases Build Tool Steve Dellenback / Robert Heller 9:15 – 9:30Open Discussion All

October 1, 2007SunGuide 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”

October 1, 2007SunGuide TRR Meeting 16

October 1, 2007SunGuide TRR Meeting 17 SwRI Server Farm SAN: –Two drive bays –6 fiber connected hosts FAT: –Four DL380s Development: –Six DL380s –Eight DL370s

October 1, 2007SunGuide TRR Meeting 18 Hardware Configuration Kepler / Lieibnitz (District 5 database): NO EM ON THIS SETUP  DMS devices: o Four IDI 2x20 devices:  01-Demo  03-Demo  04-Demo  06-Demo o One IDI 3x18 device:  99-BigSign  VSL devices: o Two IDI 2x20 (1x2) devices:  02-DemoVSL  05-DemoVSL  CCTV devices: o One AD Ultra 7: 100-SwRI_AD_Ultra7 o One AD Ultra 8: 101-SwRI_AD_Ultra8 o One Vicon (NTCIP): SwRI Cohu SR436) o One Cohu (NTCIP) : SwRI Cohu West of 436)  Video Capture (standalone workstation with capture card): o Vbrick decoder: using 1 video feed for multiple “simulated” cameras  TSS devices: o Driven by simulators  RWIS devices: o Driven by simulators Peano (District 4 database):  DMS devices: o Five IDI 2x20 devices:  01-Demo  02-Demo  03-Demo  04-Demo  CCTV devices: o None  TSS devices: o None Taylor (District 6 database):  DMS devices: o None  CCTV devices: o None  TSS devices: o None Pythagoras (hosts C2C / web sites):  Web site (fl511dev.datasys.swri.edu)  Event Viewer (EventViewer.datasys.swri.edu)

October 1, 2007SunGuide TRR Meeting 19 Release 3.0 Integration Cases 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)

October 1, 2007SunGuide 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)

October 1, 2007SunGuide TRR Meeting 21 Schedule for Testing Date / TimeItemLead MondayIC-8: Event ManagementIBI Tuesday IC-8: Event Management IC-11: Event Viewer (EV) IC-9: Response Plan Generation IC-6: AVL/RR (partial) IC-10: Reporting Subsystem IBI / SwRI Wednesday IC-10: Reporting Subsystem (continued) IC-7: Incident Detection IC-12: Operational Data Store (ODS) Start partial testing: IC-2: Variable Speed Limit (VSL) IC-4: 511 (511) IC-5: Web Server (WS) IC-13: General Subsystem Updates (GEN) IBI / SwRI Thursday Complete partial testing SICP Testing SwRI

October 1, 2007SunGuide TRR Meeting 22 Test Case Example

October 1, 2007SunGuide TRR Meeting 23 Questions About Test Cases?

October 1, 2007SunGuide 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

October 1, 2007SunGuide 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

October 1, 2007SunGuide TRR Meeting 26 Automated Build Tool: Recommendation from last PCA – “push a button”

October 1, 2007SunGuide TRR Meeting 27 Agenda TimeItem Lead 8:30 – 8:35Introductions 8:35 – 8:40Logistics Steve Dellenback 8:40 – 9:00Discuss Project Status Steve Dellenback / Robert Heller / John Boguslawski 9:00 – 9:15Hardware / Lab Configuration Testing Process Test Procedures Deferred Test Cases Build Tool Steve Dellenback / Robert Heller 9:15 – 9:30Open Discussion All

October 1, 2007SunGuide TRR Meeting 28 Open Discussion