agenda

SunGuideSunGuideTMTM Software Development Project Software Development Project

Test Readiness Review (TRR) Meeting for Test Readiness Review (TRR) Meeting for SunGuide Release 3.1SunGuide Release 3.1

April 21, 2008April 21, 2008

April 21, 2008SunGuide TRR Meeting 2

AgendaAgenda

Date / Time Item Lead

April 218:30 – 10:00

Test Readiness Review (TRR) Meeting:Discuss project statusDiscuss lab configurationVerify Turnpike connectivityDiscuss testing processReview test proceduresSoftware OverviewOpen discussion

Steve DellenbackRobert Heller

April 21: 10:00–12:00 IC-1: General GUI SwRI Team

April 21: 1:00 – 5:00IC-2: General PricingIC-3: Pricing Configuration

SwRI Team

April 22: 8:30 – 12:00 IC-4: Express Lanes Event Management SwRI Team

April 22: 1:00 – 5:00 IC-5: Operational Scenarios SwRI Team

April 23: 8:30 – 12:00IC-6: ReportingIC-7: Toll Viewer

SwRI Team

April 23: 1:00 – 3:00 Retest / revisit open issues SwRI Team

April 233:00 – 5:00

Wrap up discussions:Future releasesDeployment activities plannedReview FAT Summary (include how many requirements passed/failed, troubles encountered during FAT etc…)Master SICP document signed by all partiesCorrective Action Plans (second FAT etc…) (CDRL 3-2.4)

All

April 24: 8:30 – 10:00 Further System Testing: IV&V, etc (on Weds if posible) All


Introductions


LogisticsLogistics

Test location:– ITS Demo Lab

Breaks:– Rolling

Lunch– SwRI Cafeteria

Internet:– Available in the lobby

(100baseT connection)

Restrooms

Restrooms

Restrooms

Lobby

Demo Lab


Current Project StatusCurrent Project Status

Release 3.1 Development Complete

172 Requirements

SwRI has been running in the lab for 4 weeks

SwRI has exercised the system

– Unit testing

– Ad hoc testing

– Dry runs of the SICP


Architecture: What Changed?Architecture: What Changed?


Discuss Lab ConfigurationDiscuss Lab Configuration


Discuss Lab Configuration :Discuss Lab Configuration :SwRI Server FarmSwRI Server Farm

SAN:– Two drive bays– 6 fiber connected

hosts

FAT:– Two DL380s:

• Laplace• Pythagoras

Development:– Six DL380s– Eight DL370s


Test Hardware LayoutTest Hardware Layout

Note: the details of the connection between D6 and FTE are not important for FAT


Equipment for TestingEquipment for TestingUtilize NTCIP “simulators”Utilize NTCIP “simulators”


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, one time 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


Verify Turnpike ConnectivityVerify Turnpike Connectivity

Test cases require connectivity to the FTE middleware

Test for connectivity to FTE middleware through use of status logger

– Sample of no connectivity

– Sample of connectivity


Discuss Testing ProcessDiscuss Testing Process

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”


How Testing Will OccurHow Testing Will Occur

For each Integration Case (IC):

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


Test Case ExampleTest Case Example


Review Test ProceduresReview Test Procedures

IC-1: GUI (GUI) IC-2: General Pricing (GP) IC-3: Pricing Configuration (PC) IC-4: Express Lanes Event Management (ELEM) IC-5: Operational Scenarios (OPS) IC-6: Toll Viewer (TV) IC-7: Reporting (REP)


General DiscussionGeneral Discussion

Questions About Test Cases?


Quick Overview of SoftwareQuick Overview of Software

The following slides are provided to provide a very quick overview of the software, areas included are:

– Administrative Editor (excerpts from Administrator Training)

– Operator GUI

Before testing each integration case, general functionality of the “area under test” will be reviewed


Express Lanes Configuration:Express Lanes Configuration:System Wide SettingsSystem Wide Settings

Enter messages displayed during overrides Set parameters used when activating an override


Express Lanes ConfigurationExpress Lanes ConfigurationHolidays / Special EventsHolidays / Special Events

Set days to be considered as holidays Add single dates, or recurring dates Recurring is a convenience for entry only: Dates are edited

individually after creation


Express Lanes Configuration:Express Lanes Configuration:SegmentsSegments

Create and manage segments for Express Lanes Associate Toll Rate Signs with Segments Displays can be marked as a Toll Gantry for this Segment


Express Lanes Configuration:Express Lanes Configuration:Daily Rate ScheduleDaily Rate Schedule

Create and edit a Daily Rate Schedule Schedule must always have at least a value starting at

midnight Given rates will go into effect at the start time when this

schedule is used


Express Lanes Configuration:Express Lanes Configuration:Segment Rate ScheduleSegment Rate Schedule

Create and edit a full Segment Rate Schedule A Daily Rate Schedule must be selected for each day type Schedule is applied to Segments; multiple Schedules can apply to

a Segment Segment will use the Schedule with the most recent start date


Express Lanes Configuration:Express Lanes Configuration:Toll Rate SignsToll Rate Signs

Create and edit Toll Rate Signs Select DMSs to be used for this Sign Set Static Text to be displayed in the GUI for each line Set Segments used to calculate displayed rate


Express Lanes Configuration:Express Lanes Configuration:System Configuration FileSystem Configuration File

In the configuration file (see the VDD for specifics) the following should be setup:– Toll Agency /Middleware:

• Toll Agency Web Service URL • Toll Agency Response Alert Interval – time in between sending

Middleware failure alerts• Toll Agency Heartbeat Interval – time in between SunGuide sending

heartbeat (i.e. GetRate) requests to Middleware• Toll Agency Retry Count – maximum number of attempts to send

SetRate requests to Middleware• Toll Agency Notify Delay – maximum time after the effective time of a

rate change SunGuide can communicate a rate change to Middleware

– Operational:• Non Time of Day (TOD) Alert Interval – time in between sending alert

messages when segment is in override• DMS Resend Rate – time in between DMS resend attempts• DMS Max Resend – maximum number of attempts to resend a DMS

message


Express Lanes TabExpress Lanes Tab


Override Mode DialogOverride Mode Dialog


Alert Acknowledge DialogAlert Acknowledge Dialog


AgendaAgenda

Date / Time Item Lead

April 218:30 – 10:00

Test Readiness Review (TRR) Meeting:Discuss project statusDiscuss lab configurationVerify Turnpike connectivityDiscuss testing processReview test proceduresSoftware OverviewOpen discussion

Steve DellenbackRobert Heller

April 21: 10:00–12:00 IC-1: General GUI SwRI Team

April 21: 1:00 – 5:00IC-2: General PricingIC-3: Pricing Configuration

SwRI Team

April 22: 8:30 – 12:00 IC-4: Express Lanes Event Management SwRI Team

April 22: 1:00 – 5:00 IC-5: Operational Scenarios SwRI Team

April 23: 8:30 – 12:00IC-6: ReportingIC-7: Toll Viewer

SwRI Team

April 23: 1:00 – 3:00 Retest / revisit open issues SwRI Team

April 233:00 – 5:00

Wrap up discussions:Future releasesDeployment activities plannedReview FAT Summary (include how many requirements passed/failed, troubles encountered during FAT etc…)Master SICP document signed by all partiesCorrective Action Plans (second FAT etc…) (CDRL 3-2.4)

All

April 24: 8:30 – 10:00 Further System Testing: IV&V, etc (on Weds if posible) All


Open Discussion


Supplemental Slides:Will be used before each IC


IC-1: GUI (GUI)IC-1: GUI (GUI)

Purpose: verify the required functionality of the Express Lanes GUIs (tabbed, override and alerts).

Tests:– The overall tabbed GUI will be examined to verify all

required data is present.– The override GUI will be examined to verify that all

required controls are available and that all conditional fields are available/restricted as appropriate.

– Integraiton with DMS will be verified.– Integration with Event Management will be verified.– Alerts generated by the Pricing Subsystem will be

verified.


IC-2: General Pricing (GP)IC-2: General Pricing (GP)

Purpose: verify required overall design of the Pricing Subsystem.

Tests:– Demonstrate the startup/restart mode of the Express

Lanes module– Demonstrate the Express Lanes module communicates

directly with the DMS subsystem bypassing MAS.– Demonstrate Express Lanes module is designed to

accommodate growth and expansion of the Express Lanes project.


IC-3: Pricing Configuration (PC)IC-3: Pricing Configuration (PC)

Purpose: verify required functionality of the Administrative Editor with respect to configuring the behavior of the PS.

Tests:– Demonstrate the toll rate change delay parameters can be set using

the Administrative Editor– Demonstrate the Administrative Editor can be used to set the Daily

Rate Schedules.– Demonstrate the Administrative Editor can associate rate tables with

segments.– Demonstrate Administrative Editor can edit types of days.– Demonstrate Administrative Editor can configure DMS associated with

Express Lanes segments.– Demonstrate SunGuide Express Lanes module can manage rate

schedules and coordinate Toll Rate DMS rate display and rate selection.

– Demonstrate the Administrative Editor can change Operator Map parameters and permissions.

– Demonstrate configuration of various Middleware Interface parameters.

– Demonstrate Administrative Editor can be used to set the beginning and ending latitude and longitude of an Express Lanes segment.


IC-4: Express Lanes Event IC-4: Express Lanes Event Management (ELEM)Management (ELEM)

Purpose: verify the required functionality of special Express Lanes DMS w.r.t. EM response plans.

Tests:– Demonstrate that Toll Rate and Toll Gantry DMS do not

behave as general DMSs with regards to Event Management.

– Demonstrate the inclusion or exclusion of Lane Status DMS in EM response plans.


IC-5: Operational Scenarios (OPS)IC-5: Operational Scenarios (OPS)

Purpose: verify the required functionality of the PS with respect to posting of toll rates to signs and the FTE middleware.

Tests:– Demonstrate the Express Lanes module posts messages to

DMS correctly.– Demonstrate general behavior of the Express Lanes module

with respect to rate posting.– Demonstrate Express Lanes module selects the correct toll

rate when in Open/Normal Rate mode.– Demonstrate Express Lanes module behavior when in Closed

or Open/Zero override mode.– Demonstrate Express Lanes module behavior when in

Open/Manual Rate override mode.– Demonstrate Express Lanes module behavior when entering,

operating, or leaving Open/Congested override mode.– Demonstrate Express Lanes communication with the FTE

Middleware.


IC-6: Toll Viewer (TV)IC-6: Toll Viewer (TV)

Purpose: verify the required functionality of the Toll Viewer.

Tests:– Demonstrate that the summary view of the Toll Viewer

application.– Demonstrate the display of events in the Toll Viewer

application.– Demonstrate the detail display mode in the Toll Viewer

application.– Demonstrate the Toll Viewer displays data in

chronological order.– Demonstrate the deployment configuration of the Toll

Viewer application through a firewall.


IC-7: Reporting (REP)IC-7: Reporting (REP)

Purpose: verify the required functionality of the DA with respect to storage of PS actions.

Tests: Demonstrate the Express Lanes module tracks changes

to configuration parameters and stores operational data. Dummy reports will be generated

agenda

Documents

formal testing processre

sunguide release

future review

swri server farmsan

review preparations

fte middlewaretest

integration case ic

pricing configuration