Presentation is loading. Please wait.

Presentation is loading. Please wait.

Agenda Time Item Lead 8:30 – 8:35 Introductions Liang Hsia 8:35 – 8:45

Similar presentations


Presentation on theme: "Agenda Time Item Lead 8:30 – 8:35 Introductions Liang Hsia 8:35 – 8:45"— Presentation transcript:

1 SunGuideSM Software Development Project Test Readiness Review (TRR) Meeting June 1, 2005

2 Agenda Time Item Lead 8:30 – 8:35 Introductions Liang Hsia 8:35 – 8:45
Logistics Steve Dellenback 8:45 – 9:20 Test Procedures Steve Dellenback / Robert Heller 9:20 – 9:35 Hot Wash-up Meetings 9:35 – 10:00 Questions / Comments All SunGuide TRR Meeting June 1, 2005

3 Introductions SunGuide TRR Meeting June 1, 2005

4 Agenda Time Item Lead 8:30 – 8:35 Introductions Liang Hsia 8:35 – 8:45
Logistics Steve Dellenback 8:45 – 9:20 Test Procedures Steve Dellenback / Robert Heller 9:20 – 9:35 Hot Wash-up Meetings 9:35 – 10:00 Questions / Comments All SunGuide TRR Meeting June 1, 2005

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

6 SunGuide TRR Meeting June 1, 2005

7 Functional Configuration Audit (FCA)
Formal FCA occurred during January 2005: Verified all CDRLs Reviewed Microsoft Visual Source Safe (VSS) Repository Reviewed Rational ClearCase Repository Built Entire System Installed System Findings: Recommendation to provide VSS dump as well as ClearCase dump May 2005, FDOT attended SwRI “internal” testing: Witnessed dry run of test procedures being executed Limited Ad Hoc Testing SunGuide TRR Meeting June 1, 2005

8 Agenda Time Item Lead 8:30 – 8:35 Introductions Liang Hsia 8:35 – 8:45
Logistics Steve Dellenback 8:45 – 9:20 Test Procedures Steve Dellenback / Robert Heller 9:20 – 9:35 Hot Wash-up Meetings 9:35 – 10:00 Questions / Comments All SunGuide TRR Meeting June 1, 2005

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/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 June 1, 2005

10 Formal Testing Should be Completed Unless Major Problems Arise
Schedule for Testing Date / Time Item Lead June 1 8:30 – 10:00 Test Readiness Review (TRR) Meeting: Discuss testing process Review test procedures Steve Dellenback 10:00 – 10:30 Software Familiarization 10:30 – 5:00 Testing using the Software Integration Case Procedures document (1 hour lunch and “rolling” breaks) June 2 8:30 – 3:30 3:30 – 4:15 Hot Wash-up Meeting (to discuss testing results) Steve Dellenback / Robert Heller 4:15 – 5:00 Discuss Deployment Plans All Formal Testing Should be Completed Unless Major Problems Arise June 3 8:30 – 12:00 Retest of any previously identified test failures Ad hoc testing SunGuide TRR Meeting June 1, 2005

11 Test Case Example SunGuide TRR Meeting June 1, 2005

12 Tests: Core Process IC-1: Core Processes: User Administration (AS-1)
Device Administration (AS-2) User and Device Database Tables (AS-3) Single User Login (AS-4) 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) Status Logger Multiple Files and File Management (SL-6) Starting and Stopping SunGuideSM Services (EH-1) Executive Handler Configurability (EH-2) SunGuideSM Auto Restart (EH-3) Executive Handler Retry Count and Privileges (EH-4) Data Abstraction and XML Support (DB-1) Data Distribution (DB-2) Data Bus Updates (DB-3) Data Bus Updates (DB-4) Operator Map Color Preferences (OM-1) SunGuide TRR Meeting June 1, 2005

13 Tests: Dynamic Message Signs
IC-2: Dynamic Message Sign: 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 and Misc. (DMS-6) Internal DMS Operating Parameters (DMS-7) DMS Sequences (DMS-8) Support Portable DMS (DMS-9) Message Priority Queue (DMS-10) Alphabetized Message Library Management (DMS-11) DMS Polling Requirements (DMS-12) Multi Page Message Timing (DMS-13) Device Failure & Device Status Reporting (DMS-14) Approved Word List Checking in Sequences (DMS-15) SunGuide TRR Meeting June 1, 2005

14 Tests: Video IC-3: Video: Map Access to Cameras (CCTV-1)
Barco Wall and IP Video Switching Support (CCTV-2) 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) CCTV Auto Lock Request (CCTV-8) AD M300 MCP (CCTV-9) Device Failure and Device Status Reporting (CCTV-10) SunGuide TRR Meeting June 1, 2005

15 Tests: TSS IC-4: Transportation Sensor Subsystem:
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) Audible Notification of Congestion Alerts (TSS-10) Detector Station Icons (TSS-11) Device Failure & Device Status Reporting (TSS-12) SunGuide TRR Meeting June 1, 2005

16 Tests: IM and General IC-5: Incident Management: 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) Incident Auto Completion, Response Plan Generation (IM-8) Movement of Incidents (IM-9) Decreasing IM Message Priority with Distance (IM-10) Incident Closure and Response Plan Cancellation (IM-11) Incident Ownership (IM-12) General: Documentation Review (DR-1) System General (SYS-1) Conflicting Direction (SYS-2) SunGuide TRR Meeting June 1, 2005

17 Questions About Test Cases?
SunGuide TRR Meeting June 1, 2005

18 Note: Oracle 10g will be used
Computer Layout Note: Oracle 10g will be used SunGuide TRR Meeting June 1, 2005

19 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, draft ECO #1.1) Electronic: All SunGuide TRR Meeting June 1, 2005

20 Next Steps… (after this week)
Deployment to District 4 Scheduled to start the week of June 13th Hardware and inventory information MUST be ready SwRI proposes the following Week 1: installation / debug (need hardware) Week 2: Training, IV&V Procedures After end of week 2: software goes operational at FDOT’s discretion Operational Need “some” hardware throughout install and testing SunGuide TRR Meeting June 1, 2005

21 Next Steps… (after this week): Continued
Documents: Deployment Plan specific to D4 has been provided to FDOT Software Test Procedures (STP) which are a generic set of SICP procedures: Draft has been provided to FDOT Final will be provided by June 13, 2005 SunGuide TRR Meeting June 1, 2005

22 Test Preparation Document cleanup
Published final versions of Release 1.1 documents Prepared VSS and Clear Case repository of Release 1.1 software (source code and installer) to the FDOT Central Office Test director led several dry runs through the SICP Anomalies within the SICP corrected Anomalies within the Release 1.1 software corrected SunGuide TRR Meeting June 1, 2005

23 Agenda Time Item Lead 8:30 – 8:35 Introductions Liang Hsia 8:35 – 8:45
Logistics Steve Dellenback 8:45 – 9:20 Test Procedures Steve Dellenback / Robert Heller 9:20 – 9:35 Hot Wash-up Meetings 9:35 – 10:00 Questions / Comments All SunGuide TRR Meeting June 1, 2005

24 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 SunGuide TRR Meeting June 1, 2005

25 Agenda Time Item Lead 8:30 – 8:35 Introductions Liang Hsia 8:35 – 8:45
Logistics Steve Dellenback 8:45 – 9:20 Test Procedures Steve Dellenback / Robert Heller 9:20 – 9:35 Hot Wash-up Meetings 9:35 – 10:00 Questions / Comments All SunGuide TRR Meeting June 1, 2005

26 Questions / Answers SunGuide TRR Meeting June 1, 2005


Download ppt "Agenda Time Item Lead 8:30 – 8:35 Introductions Liang Hsia 8:35 – 8:45"

Similar presentations


Ads by Google