sunguide sm software development project test readiness review (trr) meeting november 1, 2005

SunGuideSunGuideSMSM Software Development Project Software Development Project

Test Readiness Review (TRR) MeetingTest Readiness Review (TRR) MeetingNovember 1, 2005November 1, 2005

November 1, 2005SunGuide TRR Meeting 2

AgendaAgenda

Time Item Lead

1:30 – 1:35 Introductions Liang Hsia

1:35 – 1:40 Logistics Steve Dellenback

1:40 – 1:55 Testing ProcessTest Procedures

Steve Dellenback /Robert Heller

1:55 – 2:00 Hot Wash-up Meeting Steve Dellenback

2:00 – 2:15 Questions / Comments All


Introductions


AgendaAgenda

Time Item Lead








LogisticsLogistics

Test location:

– FDOT Lab Meetings:

– Conf Room: B block Break:

– C2C Lab Lunch

– SwRI Cafeteria Internet:

– Available in the lobby (100baseT connection)


Document StatusDocument 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)


AgendaAgenda

Time Item Lead








Purpose of TRRPurpose 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”.


Schedule for TestingSchedule for Testing

Date / Time Item Lead

November 11:30 – 2:00

Test Readiness Review (TRR) Meeting:Discuss testing processReview test procedures

Steve Dellenback

November 12:00 – 6:00

Testing using the Software Integration Case Procedures document (“rolling” breaks) SwRI Team

November 28:30 – 5:00

Testing using the Software Integration Case Procedures document (1 hour lunch and “rolling” breaks) SwRI Team

November 38:30 – 2:00

Testing using the Software Integration Case Procedures document(1 hour lunch and “rolling” breaks)

SwRI Team

November 32:00 – 3:30

Retest of any previously identified test failures SwRI Team

November 33:30 – 4:30

Hot Wash-up Meeting (to discuss testing results)Steve Dellenback / Robert Heller

“Free Play” in the lab if we are done early


Test Case ExampleTest Case Example


Release 1.1 Integration CasesRelease 1.1 Integration Cases

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 2.0 Integration CasesRelease 2.0 Integration Cases

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)


Questions About Test Cases?


Computer LayoutComputer Layout


Documents Available in the LabDocuments 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


Environment NoteEnvironment 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.


Next Steps… (after this week)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)


Test PreparationTest 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


Project FactoidProject 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)


AgendaAgenda

Time Item Lead








Hot Wash-Up MeetingHot 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


AgendaAgenda

Time Item Lead








Bonus Material:Bonus Material:Comments received on SICP on 11/1 at 9:20Comments 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)


Bonus Material:Bonus Material:TemplatesTemplates

During testing you will see sign and response plans with a variety of message formats

These are “template” driven and configurable by the administrator.


Bonus Material:Bonus Material:Issue Tracking / Knowledge BaseIssue 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


Questions / Answers

sunguide sm software development project test readiness review (trr) meeting november 1, 2005

Documents

sunguide trr meetingschedule

integration casesic

introductionsliang hsia1

logisticssteve dellenback1

test cases

subsystem updates

fdot labmeetings

maintenance subsystem