sunguide tm software development project test readiness review (trr) meeting october 1, 2007

SunGuideSunGuideTMTM Software Development Project Software Development Project

Test Readiness Review (TRR) MeetingTest Readiness Review (TRR) MeetingOctober 1, 2007October 1, 2007

October 1, 2007SunGuide TRR Meeting 2

AgendaAgenda

Time Item Lead

8:30 – 8:35 Introductions

8:35 – 8:40 Logistics Steve Dellenback

8:40 – 9:00 Discuss Project Status Steve Dellenback /Robert Heller /John Boguslawski

9:00 – 9:15 Hardware / Lab ConfigurationTesting ProcessTest ProceduresDeferred Test CasesBuild Tool

Steve Dellenback /Robert Heller

9:15 – 9: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








Development CycleDevelopment Cycle

Design => Unit Test => Integration Test => FAT

Some subsystems create a “chicken and egg” problem:– EM is one of “those”– Other subsystems rely on EM and cannot be completed until

EM is “solid”

EM Development schedule:– Initially due to SwRI 4 weeks prior to FAT-1 (4 weeks would

allow SwRI to integrate all SwRI developed subsystems)– Revised schedule (established during FAT-1):

• Code drop due Sep 17 to SwRI• Final code drop due Sep 24 to SwRI• Running EM (database and subsystem) did not occur until

Sep 27• As of Sep 30th (noon) we have yet to get a script to

upgrade the EM database (script for other subsystems exists)


Current Project Status:Current Project Status:From a Development PerspectiveFrom a Development Perspective

Solid:– 511– VSL– CE– AD CCTV Driver– EV– Web Server– General

Testing completed, needs final integration testing:– AVL/RR– IDS– RPG– ODS (Reports testing, generating via RS is new)– RS

Basic integration testing completed but additional development and testing needed:– EM


Current Project Status:Current Project Status:From a Development Perspective - continuedFrom a Development Perspective - continued

Why was the install not working in TERL and D4:– Installer was current and worked fine– Database upgrade script (EM components) did NOT

work and significant manual work was/is required

What is not ready:– Responder Audit Requirements (see next slide)– Database upgrade scripts for EM– SUM (EM and RS sections)– Final integration of EM related components


Responder Audit RequirementsResponder Audit RequirementsWill not be tested this weekWill not be tested this week

SunGuide Req. ID Requirement

EM011The responder audit function shall provide the capability to add, delete, or edit responder

agency timeline, vehicle response timeline, and responder activity data in the SunGuide database.

EM001UAll operator changes shall be logged in the database for traceability, including the new

value, previous value, the user who made the change, and the time the change was made.

EM002UAll operator changes shall be displayed in the chronology report with an indication that

specific information has been changed.

EM003UThe operator shall be able to run a report using the SunGuide report function to review

changes made and logged by the audit function.

EM004UThe operator shall have at least three ways to select an event: (1) by typing in the event

number directly; or (2) selecting from the list of active events, or (3) selecting from a filtered list of all events.

EM004U1The operator shall be able to filter events by month, location, type, blockage, or responding

agency involved.

EM020GA Responder Audit screen shall be incorporated into the existing audit feature of the

SunGuide GUI, using the existing permissions scheme and user authentication methods of the SunGuide GUI.

EM020G1The operator shall be able to add, delete, or edit agency notification, on-scene, and

departure times.

EM020G2The operator shall be able to leave any of the fields blank in case that information is not

available, except that a record must have at least one timestamp entered.

EM020G3The operator shall be able to add, delete, or edit vehicle response records for agencies with

responding vehicles (Road Ranger, SIRV, etc.).


Responder Audit RequirementsResponder Audit RequirementsWill not be tested this week - continuedWill not be tested this week - continued

SunGuide Req. ID Requirement

EM020G4The operator shall be required to provide the notification time and either the arrival and

departure times or the cancellation time.

EM020G5The operator shall be able to add, edit, and delete activity records associated with vehicle

response records.

EM020G6The software shall require the operator to enter the time that an activity was performed,

however the software shall also require the timestamp to fall within the arrival and departure timestamps for the vehicle record.

EM020G7The GUI shall warn the user when a timestamp is entered which is earlier than the event

start time or later than the event closed time.

EM020G8The operator shall have the option to enter a quantity associated with an activity, such as

gas, when the activity is configured as "quantifiable".

EM020G9The GUI shall display a summary of all the agency response times, the detailed vehicle

response time records, and all the activities performed.

EM020G10 The GUI shall display the event location, event number, and blockage history for an event.

EM020G11The GUI shall provide an event chronology summary window with the ability to generate a

report.

EM021G A comments field shall be provided for the operator to enter free-text data.

EM012 Activities shall be classified in the software as quantifiable or not.


Forward Looking ScheduleForward Looking Schedule(dates from currently published schedule)(dates from currently published schedule)

IV&V – TERL (FDOT/PBS&J led activity):– Dry Run: Oct 10-16– Actual Test: Oct 16-19

Operating Training Material: Oct 3, 2007

Installs:– Sep 25-28:

• D4• TERL

– Oct 15-16: D2– Oct 22-25: D5– Oct 22-25: D6– Oct 29-30: D7


Project StatusProject Status

Still waiting from IBI:– Dates for:

• When SUM input will be provided• When Responder Audit will be completed• When EM database scripts will be completed

SwRI activities:– Final integration testing once final products are

received

Timeframe objective: to have completed by IV&V

Discussion / comments ???


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): NO EM ON THIS SETUP

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 2 LimitationsFAT 2 Limitations

Testing activities that require Event Management (EM) are not 100% integration tested (e.g. AVL/RR, IDS, RPG “may” have issues)

Comment: D5 has an install (and using operationally) the following R3.0 components:

– 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

Monday IC-8: Event Management IBI

Tuesday

IC-8: Event Management

IC-11: Event Viewer (EV)

IC-9: Response Plan Generation

IC-6: AVL/RR (partial)

IC-10: Reporting Subsystem

IBI / SwRI

Wednesday

IC-10: Reporting Subsystem (continued)

IC-7: Incident Detection

IC-12: Operational Data Store (ODS)

Start partial testing:

IC-2: Variable Speed Limit (VSL)

IC-4: 511 (511)

IC-5: Web Server (WS)

IC-13: General Subsystem Updates (GEN)

IBI / SwRI

ThursdayComplete partial testing

SICP TestingSwRI


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


Tests for FootPrints IssuesTests for FootPrints Issues

On the last days test for the following FootPrints issues will be performed (not in the SICP):

– #134: Ability to convert non-TSS link to TSS link

– #225: SAS subsystem requires restart

– #254: Refresh geometry button on Video Wall Control

Dialog not working

– #258: preferences lost

– #295: TvT needs to be restarted for new template


Automated Build Tool:Automated Build Tool:Recommendation from last PCA – “push a button”Recommendation from last PCA – “push a button”


AgendaAgenda

Time Item Lead








Open Discussion

sunguide tm software development project test readiness review (trr) meeting october 1, 2007

Documents