SunGuide TM Software Development Project Test Readiness Review (TRR) Meeting August 27, 2007

SunGuideSunGuideTMTM Software Development Project Software Development Project

Test Readiness Review (TRR) MeetingTest Readiness Review (TRR) MeetingAugust 27, 2007August 27, 2007

August 27, 2007SunGuide TRR Meeting 2

AgendaAgenda

Time Item Lead

1:00 – 1:05 Introductions

1:05 – 1:10 Logistics Steve Dellenback

1:10 – 1:40 Discuss Project Status Steve Dellenback /Robert Heller /James Barbosa

1:40 – 1:55 Hardware / Lab ConfigurationTesting ProcessTest ProceduresDeferred Test Cases

Steve Dellenback /Robert Heller

1:55 – 2:10 FCA (Functional Configuration Audit) Results Walt Townsend

2:10 – 2:30 Open Discussion All


Introductions


AgendaAgenda

Time Item Lead









LogisticsLogistics

Test location:– ITS Demo Lab

Breaks:– Rolling

Lunch– SwRI Cafeteria

Internet:– Available in the lobby

(100baseT connection)

Restrooms

Restrooms

Restrooms

Lobby

Demo Lab


AgendaAgenda

Time Item Lead









Project ScheduleProject Schedule

Notice to proceed: – March 7, 2007

Design Reviews:– May 2-3, 2007 (iFlorida)– May 8-9, 2007 (EM / RS / AVL/RR / IDS)

Follow-up Design Reviews:– May 22, 2007 (iFlorida)– May 31, 2007 (EM / RS / AVL/RR / IDS)

FAT schedule:– Initial: week of August 6, 2007– After design reviews: week of August 27, 2007– During integration:

• Week of August 27, 2007• Week of September 24, 2007 (EM, RS, AVL/RR, IDS)


Forward Looking ScheduleForward Looking Schedule(dates tentative until FDOT approved)(dates tentative until FDOT approved)

FAT 2:– Week of Sep 24th (at SwRI)

IV&V – TERL (FDOT/PBS&J led activity):– Week of October 8th

Installs:– Week of Oct 15:

• D4– Week of Oct 22:

• D5• D6

– Week of Oct 29:• D2• D7


Why the Schedule SlippageWhy the Schedule Slippage

Remember – its always easy to look backwards and figure out why something “went wrong”

SwRI and IBI have developed a very strong working relationship:– Mutual respect among developers– PMs have learned how “to work together”– Combined team / skills is extremely strong

Number of FDOT provided requirements / schedule:– Release 1.x: 280 16 months– Release 2.x: 278 13 months (some overlay w/R1.x)– Release 3: 607 6 months

The FDOT expressed functionality in the Design Reviews was not captured in the requirements (which is what schedule was based on)


Why the Schedule Slippage:Why the Schedule Slippage:ContinuedContinued

SwRI/IBI significantly underestimated the effort associated with our joint design efforts (especially ICD creation and finalization):– Took many weeks longer than anticipated– We should have had our developers finalize this document much

sooner after NTP

IBI significantly underestimated the effort associated with developing architecturally compliant SunGuide GUIs– The EM GUI screens are some of the most complex in SunGuide– The impact of the underestimation was considerable. This will be

factored into future estimates

In retrospect, the development team should not have taken on the additional 'responder audit' related requirements without requesting an extension

SwRI/IBI significantly underestimated the effort associated with joint software integration:– Extensive subsystem interdependency (EM, AVL/RR, RS, EV) slowed

the pace of integration much more than anticipated.

Schedule was very aggressive from the beginning


AgendaAgenda

Time Item Lead









Purpose of TRR / FATPurpose of TRR / FAT

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”



SwRI Server FarmSwRI Server Farm

SAN:

– Two drive bays

– 6 fiber connected hosts

FAT:

– Four DL380s

Development:

– Six DL380s

– Eight DL370s


Hardware ConfigurationHardware Configuration

Kepler / Lieibnitz (District 5 database):

DMS devices:oFour IDI 2x20 devices:

01-Demo03-Demo04-Demo06-Demo

oOne IDI 3x18 device:99-BigSign

VSL devices:oTwo IDI 2x20 (1x2) devices:

02-DemoVSL05-DemoVSL

CCTV devices:oOne AD Ultra 7: 100-SwRI_AD_Ultra7oOne AD Ultra 8: 101-SwRI_AD_Ultra8oOne Vicon (NTCIP): SwRI Cohu (I-4 @ SR436)oOne Cohu (NTCIP) : SwRI Cohu (I-4 @ West of 436)

Video Capture (standalone workstation with capture card):oVbrick decoder: using 1 video feed for multiple “simulated” cameras

TSS devices:oDriven by simulators

RWIS devices:oDriven by simulators

Peano (District 4 database):

DMS devices:oFive IDI 2x20 devices:

01-Demo02-Demo03-Demo04-Demo

CCTV devices:oNone

TSS devices:oNone

Taylor (District 6 database):DMS devices:

oNoneCCTV devices:

oNoneTSS devices:

oNone

Pythagoras (hosts C2C / web sites):Web site (fl511dev.datasys.swri.edu)Event Viewer (EventViewer.datasys.swri.edu)


Release 3.0 Integration CasesRelease 3.0 Integration Cases

IC-1: Configuration Editor (CE) IC-2: Variable Speed Limit (VSL) IC-3: American Dynamics Closed Circuit Television (AD CCTV) Driver IC-4: 511 (511) IC-5: Web Server (WS) IC-6: Automatic Vehicle Location (AVL)/Road Ranger (RR) IC-7: Incident Detection Subsystem (IDS) IC-8: Event Management (EM) (includes Responder Audit) IC-9: Response Plan Generation (RPG) IC-10: Reporting Subsystem (RS) IC-11: Event Viewer (EV) IC-12: Operational Data Store (ODS) IC-13: General Subsystem Updates (GEN)


FAT 1 LimitationsFAT 1 Limitations

Testing activities that require Event Management (EM) are limited

Test cases pertaining to iFlorida can be mostly passed (other than the EM implications)

Comment: D5 has an “early install” of:– 511– AD CCTV Driver– VSL– Web Server– Release 3.0 core components (C2C, GUI, MAS,

Data Bus, TSS)


Schedule for TestingSchedule for Testing

Date / Time Item Lead

Tuesday

IC-1: Configuration Editor (CE)

IC-2: Variable Speed Limit (VSL)

IC-3: American Dynamics CCTV (AD CCTV) Driver

IC-4: 511 (511)

IC-5: Web Server (WS)

SwRI Team

Wednesday Morning

IC-11: Event Viewer (EV)

IC-12: Operational Data Store (ODS)

IC-13: General Subsystem Updates (GEN)

SwRI Team

Weds Afternoon

Thursday Morning

Execution of partial test cases:

IC-6: AVL/RR (partial)

IC-7: Incident Detection (partial)

IC-9: Response Plan Generation (partial)

IC-10: Reporting Subsystem (partial)

SwRI and IBI


Test Case ExampleTest Case Example


Questions About Test Cases?


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


AgendaAgenda

Time Item Lead









FCA ResultsFCA Results

Performed by Walt Townsend on August 27, 2007

Activities:– Verify that VDD is correct and accurately describes the

release– Verify that configuration management processes have

been followed (software is stored correctly in the repository; and software to be tested has been built from the repository)

– Verify that the physical setup of the test environment is sufficient to validate the requirements (make sure that I/O test devices are really connected as described, etc.)

– Verify that the test environment is correctly described in the test Document


AgendaAgenda

Time Item Lead









Open Discussion

Review Agenda

Documents

SunGuide TM Software Development Project Test Readiness Review (TRR) Meeting August 27, 2007