1 / 27

SunGuide SM Software Development Project Test Readiness Review (TRR) Meeting November 1, 2005

SunGuide SM Software Development Project Test Readiness Review (TRR) Meeting November 1, 2005. Agenda. Introductions. Agenda. Logistics. Test location: FDOT Lab Meetings: Conf Room: B block Break: C2C Lab Lunch SwRI Cafeteria Internet: Available in the lobby (100baseT connection).

giselle-barrera
Download Presentation

SunGuide SM Software Development Project Test Readiness Review (TRR) Meeting November 1, 2005

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SunGuideSM Software Development ProjectTest Readiness Review (TRR) MeetingNovember 1, 2005

  2. Agenda SunGuide TRR Meeting

  3. Introductions SunGuide TRR Meeting

  4. Agenda SunGuide TRR Meeting

  5. Logistics • Test location: • FDOT Lab • Meetings: • Conf Room: B block • Break: • C2C Lab • Lunch • SwRI Cafeteria • Internet: • Available in the lobby (100baseT connection) SunGuide TRR Meeting

  6. SunGuide TRR Meeting

  7. Document Status • Documents delivered to FDOT over the last month: • Software Requirements Specification (SRS) • Software Integration Plan (SIP) • Software Integration Case Procedures (SICP) • Database Design Document (DBDD) • Software User’s Manual (SUM) • Version Description Document (VDD) • Training Plan (TP) • Other deliverables: • Rational RequisitePro database • Source CDs • Installation CDs • Outstanding Deliverable: • Software Design Document (SDD) SunGuide TRR Meeting

  8. Agenda SunGuide 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/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

  10. Schedule for Testing “Free Play” in the lab if we are done early SunGuide TRR Meeting

  11. Test Case Example SunGuide TRR Meeting

  12. IC-1: Core Processes: User (AS) Status Logger (SL) Executive Handler (EH) Data Distribution (DD) Operator Map (OM) IC-2: Dynamic Message Sign (DMS) IC-3: Video (CCTV) IC-4: Transportation Sensor Subsystem (TSS) IC-5: Incident Management (IM) General Requirements Release 1.1 Integration Cases SunGuide TRR Meeting

  13. IC-6: Subsystem Updates: Graphical User Interface (GUI) Closed Circuit Television (CCTV) IM IC-7: Trailblazer IC-8: Safety Barrier (SB) IC-9: Roadway Weather Information System (RWIS) IC-10: Highway Advisory Radio (HAR) IC-11: Ramp Metering Subsystem (RMS) IC-12: Center-to-Center (C2C) IC-13: Web Server (WS) IC-14: Emergency Evacuation (EE) IC-15: Inventory and Maintenance Subsystem (IMS) IC-16: Data Archiving (DA) IC-17: Travel Times (TvT) General Requirements (not attributed to any one IC) Release 2.0 Integration Cases SunGuide TRR Meeting

  14. Questions About Test Cases? SunGuide TRR Meeting

  15. Computer Layout SunGuide TRR Meeting

  16. 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

  17. 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 causes a short on the power lines and toasted a number of devices such as voice mail) to SwRI last week and the Cortec Codecs have never been the same. SunGuide TRR Meeting

  18. Next Steps… (after this week) • Deployment to District 6 • Scheduled to start the week of Nov 7th • Training during the week of Nov 15th and/or 21st based on D6 staff availability • Factors to simplify installation: • Recent milestone demonstration overcame a number of communication issues • SunGuideSM D6 database is fairly mature • Future development • Based on FDOT approval • Planned enhancements will be 2.x (no formal FAT) SunGuide TRR Meeting

  19. Test Preparation • Document cleanup • Published final versions of Release 2.0 documents • Prepared VSS and Clear Case repository of Release 2.0 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 2.0 software corrected SunGuide TRR Meeting

  20. Project Factoid • Development activities (25 months): • Began October 7, 2003 • Ended November 3, 2005 • Initial project schedule requested by FDOT: 25 months • Staff time: 48,577 hours • Costs: • Release 1: $4,335,554 (spent $4,321,459) • Release 2: $2,732,303 (projected $2,307,432) • Development under-run: $225K • Lines of code: 925K SLOC (generic framework saved SLOCs) SunGuide TRR Meeting

  21. Agenda SunGuide TRR Meeting

  22. Hot Wash-Up Meeting • 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

  23. Agenda SunGuide TRR Meeting

  24. Bonus Material:Comments received on SICP on 11/1 at 9:20 • Comments in “need to look at XML” category: • SwRI was told emphatically by FDOT to not show XML (using client tester) during FAT 1.0 • SwRI wrote tests that “did not show XML” based on FDOT’s direction - SwRI is happy to show XML • Changes: • Several “pen and ink” changes are being made: SwRI will distribute color coded changes as single sheets during the testing • No changes needed: • Some comments were already “corrected” by the most recent version of the SICP • Editorial: • Several comments editorial in nature (no response needed) SunGuide TRR Meeting

  25. Bonus Material:Templates • During testing you will see sign and response plans with a variety of message formats • These are “template” driven and configurable by the administrator. SunGuide TRR Meeting

  26. Bonus Material:Issue Tracking / Knowledge Base • During July meetings SwRI was asked for a better FAQ / Knowledge base solution • SwRI evaluated a number of products, have procured “FootPrints” (web based) • Will demo on Thurs afternoon SunGuide TRR Meeting

  27. Questions / Answers SunGuide TRR Meeting

More Related