190 likes | 296 Vues
SunGuide TM Software Development Project Test Readiness Review (TRR) Meeting for SunGuide Release 4.1 October 14, 2008. Introductions. Agenda. Logistics. Test location: ITS Demo Lab Breaks: Rolling Lunch SwRI Cafeteria Internet: Available in the lobby (100baseT connection). Restrooms.
E N D
SunGuideTM Software Development ProjectTest Readiness Review (TRR) Meeting for SunGuide Release 4.1October 14, 2008
Introductions SunGuide 4.1 TRR
Agenda SunGuide 4.1 TRR
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 4.1 TRR
Current Project Status • Release 4.1 Development Complete • 79 Requirements • SwRI has exercised the system • Unit testing • Ad hoc testing • Dry runs of the SICP SunGuide 4.1 TRR
Architecture: What Changed? SunGuide 4.1 TRR
Test Hardware Layout SunGuide 4.1 TRR
Discuss Lab Configuration SunGuide 4.1 TRR
Discuss Lab Configuration :SwRI Server Farm • SAN: • Two drive bays • 6 fiber connected hosts • FAT: • Four DL380s: • Fermat • Pythagoras • Laplace • Kepler • Development: • Six DL380s • Eight DL370s SunGuide 4.1 TRR
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, one time 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 4.1 TRR
Discuss Testing Process • 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 4.1 TRR
How Testing Will Occur • For each Integration Case (IC): • SwRI will explain the objective of the IC • Requirements will be reviewed • A “reader” will walk through each test case (see next slide for an ‘example’ test case) • An “operator” will perform the GUI actions • Results will be captured • Note: Enhancements will be captured for future review by FDOT SunGuide 4.1 TRR
Test Case Example SunGuide 4.1 TRR
Review Test Procedures • IC-1: Admin Editor (AE) • IC-2: Graphical User Interface (GUI) • IC-3: Data Archive (DA) • IC-4: Probe Fusion (PF) • IC-5: Automatic Vehicle Identification/License Plate Reader (AVI/LPR) • IC-6: Alternate Routes (AR) • IC-7: Travel Times (TvT) • IC-8: Miscellaneous (MISC) • IC-9: TvT Computation (TvTC) SunGuide 4.1 TRR
General Discussion Questions About Test Cases? SunGuide 4.1 TRR
Open Discussion SunGuide 4.1 TRR
Agenda SunGuide 4.1 TRR
Agenda SunGuide 4.1 TRR
Agenda SunGuide 4.1 TRR