Sun Guide Software Development Project Test Readiness Review
- Slides: 17
Sun. Guide® Software Development Project Test Readiness Review (TRR) Meeting for Sun. Guide Release 4. 2 April 14, 2009 Sun. Guide 4. 2 TRR 1
Introductions Sun. Guide 4. 2 TRR April 14, 2009 2
Agenda Date / Time April 14 : 9: 15 – 10: 00 Item Discussions with new Sun. Guide PM General project discussion Sun. Guide Overview Test Readiness Review (TRR) Meeting: Discuss project status Discuss testing process Review test procedures Discuss lab configuration Discuss regression testing Open discussion Training on new functionality (FHP/CAD and Visio. Pad related) April 14: 10: 30 – 12: 00 Regression Testing: AVL/RR Sw. RI Team April 14: 1: 00 – 2: 30 Regression Testing: AVL/RR Sw. RI Team April 13 1: 00 – 5: 00 April 14 8: 30 – 9: 15 April 14 3: 00 – 5: 00 April 15 8: 30 – 12: 00 April 15 1: 00 – 5: 00 April 16 8: 30 – 11: 00 Sun. Guide 4. 2 TRR IC-1: FHP/CAD Interface Requirements (INT) IC-2: FHP/CAD Data Requirements (DATA) IC-3: General FHP/CAD Requirements (GEN) The following require remote support from Vanus (these tests have all passed at D 7 during March 2009): o IC-4: AVL/RR GUI Requirements (GUI) o IC-5: AVL/RR Interface Requirements (INF) IC-6: Various Requirements (VAR) IC-7: Travel Time Performance Measures Report Enhancement (Tv. T) IC-8: Visio. Pa. D Requirements (VP) Wrap up discussions: Discuss any outstanding issues IV&V Deployment activities planned April 14, 2009 Lead All Dellenback Robert Heller Roger Strain Sw. RI Team All FDOT CO All 3
Logistics l Please limit access to development labs, staff assignments have changed Test location: – ITS Demo Lab l Breaks: – Rolling l Lunch – Sw. RI Cafeteria Restrooms l Restrooms Demo Lab Lobby l Restrooms Internet: – Available in the lobby (100 base. T connection) Sun. Guide 4. 2 TRR April 14, 2009 4
Current Project Status l Release 4. 2 Development Complete l 79 Requirements, two funding sources: – FDOT (AVL/RR and FHP/CAD enhancements): • Note that Sw. RI has exercised the AVL/RR enhancements with D 7 personnel and noted no issues or failures – this will be re-executed this week – Fortran (funded Visio. Pa. D enhancement, they have reviewed the SICP and concur its adequate to test the enhancement) l Sw. RI has exercised the system – Unit testing – Ad hoc testing – Dry runs of the SICP Sun. Guide 4. 2 TRR April 14, 2009 5
Architecture: What Changed? Sun. Guide 4. 2 TRR April 14, 2009 6
Test Hardware Layout Sun. Guide 4. 2 TRR April 14, 2009 7
Discuss Lab Configuration Sun. Guide 4. 2 TRR April 14, 2009 8
Discuss Lab Configuration : Sw. RI Server Farm SAN: – Two drive bays – 6 fiber connected hosts l FAT: – DL 380 s: • Fermat/Fourier • Pythagoras • Laplace • Pascal • L 4 l Development: – Six DL 380 s – Eight DL 370 s l Sun. Guide 4. 2 TRR April 14, 2009 9
Environment Note l Note that Sw. RI has both “real” equipment and simulators in the lab l There are times that the simulators “mis-behave” and we find ourselves “re-testing” to achieve the results l The “re-tests” do NOT require software modifications l Sw. RI has other project’s that will occasionally (accidentally) “hit” our development devices l Access to FHP data sources will at times become unavailable Sun. Guide 4. 2 TRR April 14, 2009 10
Discuss Testing Process l Purpose: – Review preparations for testing – Walk through the test procedures at a very high level and determine if anyone has any comments l 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 l Approvals: – FDOT/Sw. RI 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” Sun. Guide 4. 2 TRR April 14, 2009 11
How Testing Will Occur l For each Integration Case (IC): – Sw. RI 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 Sun. Guide 4. 2 TRR April 14, 2009 12
Test Case Example Sun. Guide 4. 2 TRR April 14, 2009 13
Review Test Procedures l IC-1: FHP/CAD Interface Requirements (INT) l IC-2: FHP/CAD Data Requirements (DATA) l IC-3: General FHP/CAD Requirements (GEN) l IC-4: AVL/RR GUI Requirements (GUI) l IC-5: AVL/RR Interface Requirements (INF) l IC-6: Various Requirements (VAR) l IC-7: Travel Time Performance Measures Report Enhancement (Tv. T) l IC-8: Visio. Pa. D Requirements (VP) Sun. Guide 4. 2 TRR April 14, 2009 14
General Discussion Questions About Test Cases? Sun. Guide 4. 2 TRR April 14, 2009 15
Open Discussion Sun. Guide 4. 2 TRR April 14, 2009 16
Agenda Date / Time April 14 : 9: 15 – 10: 00 Item Discussions with new Sun. Guide PM General project discussion Sun. Guide Overview Test Readiness Review (TRR) Meeting: Discuss project status Discuss testing process Review test procedures Discuss lab configuration Discuss regression testing Open discussion Training on new functionality (FHP/CAD and Visio. Pad related) April 14: 10: 30 – 12: 00 Regression Testing: AVL/RR Sw. RI Team April 14: 1: 00 – 2: 30 Regression Testing: AVL/RR Sw. RI Team April 13 1: 00 – 5: 00 April 14 8: 30 – 9: 15 April 14 3: 00 – 5: 00 April 15 8: 30 – 12: 00 April 15 1: 00 – 5: 00 April 16 8: 30 – 11: 00 Sun. Guide 4. 2 TRR IC-1: FHP/CAD Interface Requirements (INT) IC-2: FHP/CAD Data Requirements (DATA) IC-3: General FHP/CAD Requirements (GEN) The following require remote support from Vanus (these tests have all passed at D 7 during March 2009): o IC-4: AVL/RR GUI Requirements (GUI) o IC-5: AVL/RR Interface Requirements (INF) IC-6: Various Requirements (VAR) IC-7: Travel Time Performance Measures Report Enhancement (Tv. T) IC-8: Visio. Pa. D Requirements (VP) Wrap up discussions: Discuss any outstanding issues IV&V Deployment activities planned April 14, 2009 Lead All Dellenback Robert Heller Roger Strain Sw. RI Team All FDOT CO All 17
- Software readiness review
- Test readiness review
- Flight readiness review
- Test readiness review presentation
- Production readiness review
- Chapter 6 career readiness
- Supplier readiness review
- Taacs tamworth
- Launch readiness review
- Launch readiness review
- Production readiness review
- Software project survival guide
- Eic software software review
- Project readiness assessment
- Project planning begins with the melding of
- Project plan presentation
- Software development project transition
- Process discriminants in software project management