1. SunGuide SM Software Development Project Test Readiness Review (TRR) Meeting January 11, 2005

2. January 11, 2005SunGuide TRR Meeting 2 Agenda TimeItem Lead 8:30 – 8:35Introductions Liang Hsia 8:35 – 8:45Logistics Steve Dellenback 8:45 – 9:20Test Procedures Steve Dellenback / Robert Heller 9:20 – 9:35Hot Wash-up Meetings Steve Dellenback 9:35 – 9:45Issues Tracking Steve Dellenback / Robert Heller 9:45 – 10:00Questions / Comments All

3. January 11, 2005SunGuide TRR Meeting 3 Introductions

4. January 11, 2005SunGuide TRR Meeting 4 Agenda TimeItem Lead 8:30 – 8:35Introductions Liang Hsia 8:35 – 8:45Logistics Steve Dellenback 8:45 – 9:20Test Procedures Steve Dellenback / Robert Heller 9:20 – 9:35Hot Wash-up Meetings Steve Dellenback 9:35 – 9:45Issues Tracking Steve Dellenback / Robert Heller 9:45 – 10:00Questions / Comments All

5. January 11, 2005SunGuide TRR Meeting 5 Logistics Test location: –FDOT Lab Meetings: –Conf Room A/B Break: –C2C Lab Lunch –SwRI Cafeteria Internet: –Available in the lobby (100baseT connection)

6. January 11, 2005SunGuide TRR Meeting 6

7. January 11, 2005SunGuide TRR Meeting 7 Functional Configuration Audit (FCA) Verified all CDRLs Reviewed Microsoft Visual Source Safe (VSS) Repository Reviewed Rational ClearCase Repository Built Entire System Installed System Limited Ad Hoc Testing Findings: –Recommendation to provide VSS dump as well as ClearCase dump (already accomplished)

8. January 11, 2005SunGuide TRR Meeting 8 Agenda TimeItem Lead 8:30 – 8:35Introductions Liang Hsia 8:35 – 8:45Logistics Steve Dellenback 8:45 – 9:20Test Procedures Steve Dellenback / Robert Heller 9:20 – 9:35Hot Wash-up Meetings Steve Dellenback 9:35 – 9:45Issues Tracking Steve Dellenback / Robert Heller 9:45 – 10:00Questions / Comments All

9. January 11, 2005SunGuide TRR Meeting 9 Purpose of TRR 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 Approvals: –FDOT will approve the SICP prior to execution –FDOT/SwRI will witness each test case

10. January 11, 2005SunGuide TRR Meeting 10 Schedule for Testing Date / TimeItemLead January 10 9:00 – 5:00 Functional Configuration Audit:  Review of contract deliverables  CM repository review  SunGuide SM software Build  Verify installation of SunGuide SM Software Steve Dellenback / Robert Heller / Michael Meadows / John Brisco / Walt Townsend January 11 8:30 – 10:00 Test Readiness Review (TRR) Meeting:  Discuss testing process  Review test procedures  FDOT approval of test procedures Steve Dellenback January 11 10:00 – 4:00 Testing using the Software Integration Case Procedures document (one hour lunch and “rolling” breaks) Robert Heller January 11 4:00 – 5:00 Hot Wash-up Meeting (to discuss testing results) Steve Dellenback / Robert Heller January 12 8:30 – 4:00 Testing using the Software Integration Case Procedures document (one hour lunch and “rolling” breaks) Robert Heller January 12 4:00 – 5:00 Hot Wash-up Meeting (to discuss testing results) Steve Dellenback / Robert Heller January 13 8:30 – 12:00 Testing using the Software Integration Case Procedures document (“rolling” breaks) Robert Heller January 13 1:00 – 4:00 Retest of any previously identified test failuresRobert Heller January 13 4:00 – 5:00 Hot Wash-up Meeting (to discuss testing results) Steve Dellenback / Robert Heller

11. January 11, 2005SunGuide TRR Meeting 11 Test Case Example

12. January 11, 2005SunGuide TRR Meeting 12 Tests: Core Process IC-1: Core Processes (67 requirements tested) –User Administration (AS-1) –Device Administration (AS-2) –User and Device Database Tables (AS-3) –Log Configurability (SL-1) –Message Fields Logged (SL-2) –Log Viewer Capabilities (SL-3) –Status Logger ASCII Export (SL-4) –Display Software Version / System Health (SL-5) –Starting and Stopping SunGuideSM Services (EH-1) –Executive Handler Configurability (EH-2) –SunGuideSM Auto Restart (EH-3) –Data Abstraction and XML Support (DD-1) –Data Distribution (DD-2) –Data Subscriptions (DD-3) –Data Bus Updates (DD-4) –Snapshots in the Data Bus (DD-6)

13. January 11, 2005SunGuide TRR Meeting 13 Tests: Dynamic Message Signs IC-2: Dynamic Message Sign (32 requirements tested) –Map Access to DMS (DMS-1) –Send DMS Message (DMS-2) –Support NTCIP and Mark IV (DMS-3) –Support Message Libraries (DMS-4) –High Level DMS Status Support (DMS-5) –Amber Alert Support (DMS-6) –Internal DMS Operating Parameters (DMS-7) –DMS Sequences (DMS-8) –Support Portable DMS (DMS-9)

14. January 11, 2005SunGuide TRR Meeting 14 Tests: Video and TSS IC-3: Video (43 requirements tested) –Map Access to Cameras (CCTV-1) –CCTV GUI High Level Status (CCTV-3) –NTCIP Driver Support (CCTV-4) –Portable CCTV (CCTV-5) –DMS Video Verification (CCTV-6) –Supported Technology (CCTV-7) IC-4: Transportation Sensor Subsystem (32 requirements tested) –Map Display of TSS Data (TSS-1) –TSS Data Updates (TSS-2) –TSS Device Drivers (TSS-3) –TSS Generated Alarms (TSS-4) –Configuration of TSS Devices (TSS-5) –TSS Error Logging (TSS-6) –TSS Data Elements (TSS-7) –Travel Time and Delay Display (TSS-8) –SVG and ESRI Support (TSS-9)

15. January 11, 2005SunGuide TRR Meeting 15 Tests: IM and General IC-5: Incident Management (37 requirements tested) –Event Creation (IM-1) –Event Management (IM-2) –Recording Event Notifications (IM-3) –Diversion Route Maintenance (IM-4) –Response Plan Implementation (IM-5) –Associate Events (IM-6) –Response Plan Generation (IM-7) General (31 requirements tested) –Documentation Review (DR-1) –System General (SYS-1) –Conflicting Direction (SYS-2)

16. January 11, 2005SunGuide TRR Meeting 16 Questions About Test Cases?

17. January 11, 2005SunGuide TRR Meeting 17 Computer Layout Note: Database administrative testing will occur on a separate machine to minimize test database modification

18. January 11, 2005SunGuide TRR Meeting 18 Documents Available in the Lab Paper: –Concept of Operations (ConOps) –Software Requirements Specification (SRS) –Software User’s Manual (SUM) –Functional Configuration Audit (FCA) –Software Integration Plan (SIP) –Software Acceptance Test Plan (SATP) –Software Integration Case Procedures (SICP): master copy and individual copies for all participants –Contractual Documents (Scope of Services, Requirements, ECO #1) Electronic: –All

19. January 11, 2005SunGuide TRR Meeting 19 Next Steps… (after this week) Deployment to District 4 –Scheduled for the week of January 24 th –Two weeks available but SwRI is confident that if the hardware is ready it will take 1 week or less Documents: –Implementation Plan specific to D4 has been provided to FDOT –Software Test Procedures (STP) which are a generic set of SICP procedures will be provided for site testing

20. January 11, 2005SunGuide TRR Meeting 20 Test Preparation Document cleanup –Published final versions of Release 1 documents Prepared Clear Case repository of Release 1 software and documentation Test director led several dry runs through the SICP –Anomalies within the SICP corrected –Anomalies within the Release 1 software corrected

21. January 11, 2005SunGuide TRR Meeting 21 Agenda TimeItem Lead 8:30 – 8:35Introductions Liang Hsia 8:35 – 8:45Logistics Steve Dellenback 8:45 – 9:20Test Procedures Steve Dellenback / Robert Heller 9:20 – 9:35Hot Wash-up Meetings Steve Dellenback 9:35 – 9:45Issues Tracking Steve Dellenback / Robert Heller 9:45 – 10:00Questions / Comments All

22. January 11, 2005SunGuide TRR Meeting 22 Hot Wash-Up Meetings Purpose: –Anomalies identified during testing are discussed and everybody agrees on what happened –Results are captured in a Hot Wash-Up minutes (one set of minutes for the entire week of testing) After the testing period, SwRI will develop a Software Test Reports which contains: Summary narratives of the test results Identification of problems or failures Recommended resolutions of anomalies observed Copies of witnessed data sheets

23. January 11, 2005SunGuide TRR Meeting 23 Agenda TimeItem Lead 8:30 – 8:35Introductions Liang Hsia 8:35 – 8:45Logistics Steve Dellenback 8:45 – 9:20Test Procedures Steve Dellenback / Robert Heller 9:20 – 9:35Hot Wash-up Meetings Steve Dellenback 9:35 – 9:45Issues Tracking Steve Dellenback / Robert Heller 9:45 – 10:00Questions / Comments All

24. January 11, 2005SunGuide TRR Meeting 24 Issue Tracking Contact requires: –Rational ClearQuest to track issues Web Site –URL: itsweb.datasys.swri.edu/ClearQuestWeb –Usernames and Passwords: District4 District6 MDX LiangHsia DavidChang JohnBonds WaltTownsend –ClearQuest Administrator: Lynne Randolph

25. January 11, 2005SunGuide TRR Meeting 25 Issue Tracking - continued The Web site is available 24 hours a day. Assistance is available during normal business hours by calling SwRI. The user interface of the product takes some time to become familiar with it. For example, most of the text IS a hyperlink to something, even though they are not underlined. Remember to log out from the system when it is not in use as the number of licenses is limited and once you log in a license is used and unavailable for another user.

26. January 11, 2005SunGuide TRR Meeting 26 Logging In Enter your username and password Select the “FDOTI” database. You may need to press the RefreshDbList button. Click the “Logon” button

27. January 11, 2005SunGuide TRR Meeting 27 Submitting Issues Login to ClearQuest Select “Defect” from the dropdown list For the Project select “SunGuide Release 1” Fill in as much information as possible Assign the problem to Robert Heller Click on “OK” to submit

28. January 11, 2005SunGuide TRR Meeting 28 Queries Database queries can be used to search the issues database. The “All Defects” query is supplied to all users and returns a list of all issues in chronological order. You can enter record numbers in the input box next to Find in the menu bar at the top of the page. The application will search for the corresponding record(s) and return those defects containing the search terms.

29. January 11, 2005SunGuide TRR Meeting 29 ClearQuest: How Will it be Used Issues will be submitted: –FDOT –SwRI Issues will be reviewed and categorized by the SwRI SPM: –Bugs: will be evaluated and FDOT provided with an estimate to address –Enhancements: at FDOT’s request the enhancements will be estimated and a cost and schedule to be implemented will be provided

30. January 11, 2005SunGuide TRR Meeting 30 Agenda TimeItem Lead 8:30 – 8:35Introductions Liang Hsia 8:35 – 8:45Logistics Steve Dellenback 8:45 – 9:20Test Procedures Steve Dellenback / Robert Heller 9:20 – 9:35Hot Wash-up Meetings Steve Dellenback 9:35 – 9:45Issues Tracking Steve Dellenback / Robert Heller 9:45 – 10:00Questions / Comments All

31. January 11, 2005SunGuide TRR Meeting 31 Questions / Answers