Module 13 - T202

T202: Overview of Test Design Specifications Test Cases, and Test Procedures

HTML of the PowerPoint Presentation

(Note: This document has been converted from a PowerPoint presentation to 508-compliant HTML. The formatting has been adjusted for 508 compliance, but all the original text content is included, plus additional text descriptions for the images, photos and/or diagrams have been provided below.)

 

Slide 1:

Slide 1: ITS Welcome - see the extended text description below.

(Extended Text Description: Slide 1: Welcome - Graphic image of introductory slide. A large dark blue rectangle with a wide, light grid pattern at the top half and bands of dark and lighter blue bands below. There is a white square ITS logo box with words “Standards ITS Training” in green and blue on the middle left side. The word “Welcome” in white is to the right of the logo. Under the logo box are the words “RITA Intelligent Transportation Systems Joint Program Office.”)

 

Slide 2:

Welcome

Head shot photo of Shelley Row, P.E., PTOE - Director - ITS Joint Program Office

Shelley Row, P.E., PTOE

Director

ITS Joint Program Office

Shelley.Row@dot.gov

Screen capture snapshot of RITA website - for illustration only - see the extended text description below.

(Extended Text Description: Slide 2: Screen capture snapshot of RITA website - for illustration only. Below this image is a link to the current website: http://www.pcb.its.dot.gov - this screen capture snapshot shows an example from the RITA website from June 3, 2011. At the top of the page it shows the RITA logo with the text Research and Innovative Technology Administration - Intelligent Transportation Systems. Below the main site banner, it shows the main navigation menu with the following items: About RITA, Communities of Interest, Contact Us, Press Room, RITA Offices, Site Map, and a Search button. Below the main navigation menu, it shows a sub-navigation menu with the following items: About Us, T3 Webinars, ITS Peer-to-Peer, Resources, Local ITS PCB and Testimonials. Beneath the sub-navigation menu, the page is sub-titled "ITS Professional Capacity Building Program" and is divided into sub-sections such as "Welcome to ITS Professional Building", "News", "ITS Technical Assistance" and "Scheduled T3 Webinars". Again, this image serves for illustration only. The current website link is: http://www.pcb.its.dot.gov)

WWW.PCB.ITS.DOT.GOV

(Note: There is additional text attached to this slide that includes the following introductory information from Shelley Row):

"ITS Standards can make your life easier. Your procurements will go more smoothly and you’ll encourage competition, but only if you know how to write them into your specifications and test them. This module is one in a series that covers practical applications for acquiring and testing standards-based ITS systems.

I am Shelley Row the director of the ITS Joint Program Office for USDOT and I want to welcome you to our newly redesigned ITS standards training program of which this module is a part. We are pleased to be working with our partner, the Institute of Transportation Engineers, to deliver this new approach to training that combines web based modules with instructor interaction to bring the latest in ITS learning to busy professionals like you.

This combined approach allows interested professionals to schedule training at your convenience, without the need to travel. After you complete this training, we hope that you will tell colleagues and customers about the latest ITS standards and encourage them to take advantage of the archived version of the webinars.

ITS Standards training is one of the first offerings of our updated Professional Capacity Training Program. Through the PCB program we prepare professionals to adopt proven and emerging  ITS technologies that will make surface transportation safer, smarter and greener which improves livability for us all. You can find information on additional modules and training programs on our web site www.pcb.its.dot.gov.

Please help us make even more improvements to our training modules through the evaluation process. We look forward to hearing your comments. Thank you for participating and we hope you find this module helpful."

 

Slide 3:

T202
Overview of Test Design Specifications, Test Cases, and Test Procedures

 

Slide 4:

Target Audience

 

Slide 5:

Instructor

Slide 5:  Headshot of Instructor, Russ Brookshire, Product Manager, Intelligent Devices.

Russ Brookshire
Product Manager Intelligent Devices
Suwanee,GA
USA

 

Slide 6:

Recommended Prerequisites

 

Slide 7:

Curriculum Path (Testing)

Slide 7: Curriculum Path (Testing). Please see the Extended Text Description below.

(Extended Text Description: Slide 7: Curriculum Path (Testing): A graphical illustration indicating the sequence of training modules for the standards that include Testing content. Each module is represented by a box with the name of the module in it and an arrow showing the logical flow of the modules. The current module is highlighted. The first box is labeled “T101 Introduction to ITS Standards Testing.” An arrow from this box connects it to a box labeled “T201 How to Write a Test Plan”. An arrow from this box connects it to a highlighted box labeled “T202 Overview of Test Design Specifications, Test Cases, and Test Procedures”, representing this module. Three arrows from this box connect to three additional boxes labeled “T311 Applying Your Test Plan to the NTCIP 1203 v03 DMS Standard”, “T313 Applying Your Test Plan to the NTCIP 1204 v03 ESS Standard”, and “T3XX Applying Your Test Plan to NTCIP/TMDD/ATC Standards”. )

 

Slide 8:

Learning Objectives

1. Describe, within the context of the testing lifecycle, the role of Test Plans, Test Design Specifications, Test Cases and Test Procedures

2. Describe the purpose and content of Test Design Specifications, Test Cases, and Test Procedures

 

Slide 9:

Learning Objectives (Cont'd)

3. For standards using the Systems Engineering Process (SEP), detail the manner that Protocol Requirements Lists (PRLs) and Requirements to Test Cases Traceability Matrices (RTCTMs) can be used to create Test Specifications

4. For standards that do not use SEP, detail the manner that Conformance Groups can be used to create Test Specifications

 

Slide 10:

Learning Objective #1

Testing and the Project Life Cycle

Slide 10:  Testing and the Project Life Cycle.  Please see the Extended Text Description below.

Pages 7 and 8 in the Supplement

(Extended Text Description: Slide 10: A graphic of the FHWA “V” diagram of the Project Life Cycle is shown. The main graphic is a V-shaped diagram with some additional horizontal “wings” on the left and right side of the top of the V. Starting from the left “wing” the steps are Regional Architecture(s) and Feasibility Study / Concept Exploration. At this point the steps begin to descend the left side of the V with: Concept of Operations; System Requirements; High-Level Design; and Detailed Design. The base of the V shows Software / Hardware Development & Field Installation. At this point the steps begin to ascend the right side of the V with: Unit / Device Testing; Subsystem Verification; System Verification & Deployment; and System Validation. Finally, the right “wing” includes steps that occur past the testing phases: Operations and Maintenance; Changes and Upgrades; and Retirement / Replacement. Each phase on the left of the “V” is associated by means of a dashed arrow with a phase on the right “V” (from the bottom): Detailed Design is associated with Unit / Device Testing by the Unit / Device Test Plan; High-Level Design is associated with Subsystem Verification by the Subsystem Verification Plan (Subsystem Acceptance); System Requirements is associated with System Verification & Deployment by the System Verification Plan (System Acceptance); and Concept of Operations is associated with System Validation by the System Validation Plan. The left side of the “V” is labeled “Decomposition and Definition”, the bottom is labeled “Implementation”, and the right side of the “V” is labeled “Integration and Recomposition”. At the bottom, a rightward facing arrow is labeled “Time Line".)

 

Slide 11:

Learning Objective #1

Why Test?

 

Slide 12:

Learning Objective #1

Testing Methods

 

Slide 13:

Slide 13: Activity.  A placeholder graphic of a hand typing on a computer keyboard indicating an activity follows

 

Slide 14:

What are some of the benefits of NTCIP Conformance Testing?

Enter response in the chat box

 

Slide 15:

Learning Objective #1

Benefits of Conformance Testing

 

Slide 16:

Learning Objective #1

Test Plans

 

Slide 17:

Learning Objective #1

What Item is to be Tested, and When is it to be Tested

 

Slide 18:

Learning Objective #1

In What Detail is the Item to be Tested

 

Slide 19:

Learning Objective #1

How is the Item to be Tested?

 

Slide 20:

Learning Objective #1

Who is to Design and Perform the Testing

 

Slide 21:

Learning Objective #1

Additional Considerations for Test Plans

 

Slide 22:

Learning Objective #2

Test Specifications

Definitions per IEEE 829

 

Slide 23:

Learning Objective #2

Test Documentation Components

Slide 23:  Test Documentation Components.  Please see the Extended Text Description below.

(Extended Text Description: Slide 23: To the left of the text is a graphic showing the relationship of Test Plans and Test Specifications. At the top is a block labeled “Test Plan”, which has a single arrow downward to a block labeled “Test Design Specification”. This block has three arrows pointing to three blocks labeled “Test Case 1”, “Test Case 2”, and “Test Case 3”. Below these three blocks are three blocks labeled “Test Procedure 1”, “Test Procedure 2”, and “Test Procedure 3”. Test Cases 1 and 2 have arrows pointing to Test Procedure 1. Test Case 3 has two arrows: the first points to Test Procedure 2; the second points to Test Procedure 3.)

 

Slide 24:

Learning Objective #2

Example of Test Specifications

Test Item: Calculator

Slide 24:  Example of Test Specifications.  Please see the Extended Text Description below.

(Extended Text Description: Slide 24: A graphic shows an example of test specification that uses a calculator for the test item. Four text boxes are shown. The top box has the header “Test Design Specification” along with the test “Feature to be Tested: Addition”. This box has two arrows, each leading to a box labeled respectively “Test Case 1” and “Test Case 2”. The Test Case 1 box has the text “Add two position numbers”, with Input 1 being 7, Input 2 being 12, Operation shows a “plus” sign for addition, and Result being “Displays 19”. The Test Case 2 box has the text “Sum too large”, with Input 1 being 500, Input 2 being 500, Operation shows a “plus” sign for addition, and Result being “Displays “Err””. The Test Case 1 and Test Case 2 boxes each have an arrow leading to the final box at the bottom of the slide. This box has a Header “Test Procedure 1: Arithmetic”, followed by the steps: 1. Enter Input 1; 2. Enter operation; 3. Enter input 2; 4. Press the “=” key; 5. Verify result.)

 

Slide 25:

Slide 25: Polling.  A placeholder graphic of multiple raised hands indicating that a Poll follows.

 

Slide 26:

Which of the following are included in NTCIP standards?

  1. Test Design Specifications (TDS)
  2. Test Case Specifications (TCS)
  3. Test Procedure Specifications (TPS)
  4. All three
  5. It depends

 

Slide 27:

Learning Objectives #1, 2

Summary of Test Documents

 

Slide 28:

Slide 28: Case Study. A placeholder graphic showing a Traffic Management Center indicating that a Case Study follows.

 

Slide 29:

Learning Objective #3

Case Study: NTCIP 1203 v03 - DMS

 

Slide 30:

Learning Objective #3

Case Study: NTCIP 1203 v03 - DMS

DMS Configuration:

Slide 30:  Case Study: NTCIP 1203 v03-DMS.  Please see the Extended Text Description below.

Courtesy: Intelligent Devices, Inc.

(Extended Text Description: Slide 30: To the right of the text a picture shows a large sign with a black background and amber characters. The top line begins with a blank character, after which “HOV LANE CLOSED” is followed by two blank characters. The middle line shows “ACROSS NARROWS BRG”. The bottom line has three blank characters followed by “USE CAUTION”, which is followed by four blank characters.)

 

Slide 31:

Learning Objective #3

Content of Test Design Specifications

Not included in NTCIP standards

Page 6 in the Supplement

 

Slide 32:

Learning Objective #3

Case Study: TDS for DMS

Selecting Features using PRL

NTCIP 1203 Protocol Requirements List (PRL)

USER NEED SECTION NUMBER

USER NEED

FR SECTION NUMBER

FUNCTIONAL REQUIREMENT

CONFORMANCE

SUPPORT/ PROJECT REQUIREMENT

ADDITIONAL PROJECT REQUIREMENTS

2.3.2.3

DMS Display Matrix Configuration

M

Yes

The DMS shall be 9,000 millimeters wide (0..65535) and 2,700 millimeters high (0..65535), inclusive of borders.

The Sign's Border shall be at least 400 millimeters wide (0..65535) and 400 millimeters high (0..65535).

2.3.2.3.1

Non-Matrix

0.2 (1)

Yes/No

2.3.2.3.2 (Matrix)

Matrix

0.2 (1)

Yes/No

The pitch between pixels shall be at least 66 millimeters (0..255).

2.3.2.3.2.1

Full Matrix

0.3 (1)

Yes/No

The sign shall be    pixels wide (0..65535) and    pixels high (0..65535).

2.3.2.3.2.2

Line Matrix

0.3 (1)

Yes/No

The sign shall have     lines with each line being    pixels wide and    pixels high.

2.3.2.3.2.3

Character Matrix

0.3(1)

Yes/No

The sign shall be 18 characters wide and 3 characters high with each character being 5 pixels wide (0..255), 7 pixels high (0..255).

(Additional Notes from the Author: Below the text, an excerpt from the NTCIP 1203 Protocol Requirements List (PRL) shows a table with the following columns: user Need Section Number, User Need, FR Section Number, Functional Requirement, Conformance, Support / Project Requirement and Additional Project Requirements. Entries for User Need 2.3.2.3 through 2.3.2.3.2.3 are shown. Under the Support / Project Requirement column, individual entries indicating “Yes/No” have had either Yes or No highlighted.)

 

Slide 33:

Learning Objective #3

Case Study: TDS for DMS

Selecting Features using PRL (Cont'd)

NTCIP 1203 Protocol Requirements List (PRL)

USER NEED SECTION NUMBER

USER NEED

FR SECTION NUMBER

FUNCTIONAL REQUIREMENT

CONFORMANCE

SUPPORT/ PROJECT REQUIREMENT

ADDITIONAL PROJECT REQUIREMENTS

2.3.2.3

DMS Display Matrix Configuration

M

Yes

The DMS shall be 9,000 millimeters wide (0..65535) and 2,700 millimeters high (0..65535), inclusive of borders.

The Sign's Border shall be at least 400 millimeters wide (0..65535) and 400 millimeters high (0..65535).

2.3.2.3.1

Non-Matrix

0.2 (1)

Yes/No

2.3.2.3.2 (Matrix)

Matrix

0.2 (1)

Yes/No

The pitch between pixels shall be at least 66 millimeters (0..255).

2.3.2.3.2.1

Full Matrix

0.3 (1)

Yes/No

The sign shall be    pixels wide (0..65535) and    pixels high (0..65535).

2.3.2.3.2.2

Line Matrix

0.3 (1)

Yes/No

The sign shall have     lines with each line being    pixels wide and    pixels high.

2.3.2.3.2.3

Character Matrix

0.3(1)

Yes/No

The sign shall be 18 characters wide and 3 characters high with each character being 5 pixels wide (0..255), 7 pixels high (0..255).

(Additional Notes from the Author: Slide 33: Above, the PRL excerpt from slide 32 has been repeated.)

 

Slide 34:

Learning Objective #3

Case Study: TDS for DMS

Selecting Features using PRL (Cont'd)

NTCIP 1203 Protocol Requirements List (PRL)

USER NEED SECTION NUMBER

USER NEED

FR SECTION NUMBER

FUNCTIONAL REQUIREMENT

CONFORMANCE

SUPPORT/ PROJECT REQUIREMENT

ADDITIONAL PROJECT REQUIREMENTS

2.5.1.2

Determine Sign Display Capabilities

O

Yes/No

3.5.1.2.1.1

Determine the Size of the Sign Face

M

Yes

3.5.1.2.1.2

Determine the Size of the Sign Border

M

Yes

3.5.1.2.1.3

Determine Beacon Type

M

Yes

3.5.1.2.1.4

Determine Sign Access and Legend

M

Yes

3.5.1.2.2.1

Determine Sign Face Size in Pixels

Matrix:M

Yes/NA

3.5.1.2.2.2

Determine Character Size in Pixels

Matrix:M

Yes/NA

3.5.1.2.2.3

Determine Pixel Spacing

Matrix:M

Yes/NA

(Additional Notes fror the Author: Above an excerpt from the NTCIP 1203 PRL shows a table with the same column headings as described in slide 32. The Entry for User Need Section Number 2.5.1.2, with FR Section Numbers 3.2.1.2.1.1 through 3.5.1.2.2.3, is shown. The first entry shows User Need Section Number 2.5.1.2, User Need “Determine Sign Display Capabilities”, Conformance “O”, and Support / Project Requirement “Yes / No”, with Yes highlighted. For the three requirements at the bottom of the table the Conformance column indicates “Matrix: M”, and the Support / Project Requirement column shows “Yes / NA”, with Yes highlighted.)

 

Slide 35:

Learning Objective #3

Test Design - Features to be Tested

Requirements Traceability Matrix (RTM)

Requirements Traceability Matrix (RTM)

FRID

Functional Requirement

Dialog ID

Object ID

Object Name

Additional Specifications

3.5.1.2.2

Determine Matrix Capabilities

3.5.1.2.2.1

Determine Sign Face Size in Pixels

G.1

5.3.3

vmsSignHeightPixels

5.3.4

vmsSignWidthPixels

3.5.1.2.2.2

Determine Character Size in Pixels

G.1

5.3.1

vmsCharacterHeightPixels

5.3.2

vmsCharacterWidth Pixels

3.5.1.2.2.3

Determine Pixel Spacing

G.1

5.3.5

vmsHorizontalPitch

5.3.6

vmsVertical Pitch

(Additional Notes from the Author: Slide 35: This is an excerpt from the NTCIP 1203 Requirements Traceability Matrix shows a table with the following column headings: FR ID, Functional Requirement, Dialog ID, Object ID, Object Name, and Additional Specifications.)

 

Slide 36:

Learning Objective #3

Test Design - Test Identification

Using RTCTM to Select Test Cases

Table 1. Requirements to Test Case Traceability Table

Requirement

Test Case

ID

Title

ID

Title

3.5.1.2.2

Determine Matrix Capabilities

3.5.1.2.2.1

Determine Sign Face Size in Pixels

C.3.1.6

Determine Sign Face Size in Pixels

3.5.1.2.2.2

Determine Character Size in Pixels

C.3.1.7

Determine Character Size in Pixels

3.5.1.2.2.3

Determine Pixel Spacing

C.3.1.8

Determine Pixel Spacing

(Additional Notes from the Author: Slide 376: This is an excerpt from the NTCIP 1203 Requirements to Test Case Traceability Matrix shows a table with the following top level column headings: Requirement and Test Case. Below Requirement are two column subheadings: ID and Title. Below Test Case are two column subheadings: ID and Title. The Requirement ID 3.5.1.2.2.1 is highlighted, which has the title “Determine Sign Face Size in Pixels”.)

 

Slide 37:

Learning Objective #3

Test Case Specifications (TCS)

TCS - A document specifying inputs, predicted results, and a set of execution conditions for a test item.

Pages 7-9 in the Supplement

 

Slide 38:

Learning Objective #3

Test Case Specifications

Inputs from PRL

NTCIP 1203 Test Case / Test Procedure ID

Test Case / Test Procedure

Selected

Variable

Reference

Value

1.6

Determine Sign Face Size in Pixels

X

Required_Sign_Pixel_Height

PRL 2.3.2.3.2.1 - 2.3.2.3.2.3.

21

Required_Sign_Pixel_Width

PRL 2.3.2.3.2.1-2.3.2.3.2.3

90

1.7

Determine Character Size in Pixels

X

Required_Character_Pixel_Height

PRL 2.3.2.3.2.3

7

Required_Character_Pixel_Width

PRL 2.3.2.3.2.3

5

1.3

Determine Pixel Spacing

X

Required_Horizontal_Pitch

PRL 2.3.2.3.2

66 (mm)

Required_Vertical_Pitch

PRL 2.3.2.3.2

66 (mm)

(Additional Notes from the Author: Slide 38: Below the text, an excerpt from the Student Supplement of the Test Case Specifications created for this webinar shows a table with the following top level column headings: NTCIP 1203 Test Case / Test Procedure ID; Test Case / Test Procedure; Selected; Variable; Reference; and Value. The first entry is highlighted, showing that Test Case / Test Procedure ID 1.6, Determine Sign Face Size in Pixels, was selected (has an X in column “Selected”), and has two variables: Required_Sign_Pixel_Height and Required_Sign_Pixel_Width. References to the PRL are shown for each variable, and the values 21 and 90, respectively, are assigned.)

 

Slide 39:

Learning Objective #3

Test Case Specifications

Example NTCIP Test Case/Test Procedure

C.3.1.6 Determine Sign Face Size in Pixels

Test

Title:

Determine Sign Face Size in Pixels

Case: 1.6

Description:

This test case verifies that the DMS indicates that it has a height and width in pixels that meet the requirements of the specifications.

Variables:

Required_Sign_Pixel_Height

PRL 2.3.2.3.2.1-2.3.2.3.2.3

Required_Sign_Pixel_Width

PRL 2.3.2.3.2.1-2.3.2.3.2.3

Pass/Fail Criteria:

The DUT shall pass every verification step included within the Test Case to pass the Test Case.

 

Step

Test Procedure

Results Additional References

1

CONFIGURE: Determine the sign height in pixels as required by the specification (PRL 2.3.2.3.2.1-2.3.2.3.2.3). RECORD this information as:
»Required_Sign_Pixel_Height

 

Slide 40:

Learning Objective #3

Test Procedure Specification (TPS)

See Supplement

 

Slide 41:

Learning Objective #3

Test Procedures

Per the IEEE 829 definition, the Test Procedure only defines the steps necessary to test the feature.

Step

Test Procedure

Results

Additional References

1

CONFIGURE: Determine ttie sign height in pixels as required by the specification (PRL2.3.2.3.2.1-2.3.2.32.3}. RECORD this information as:

»Required_Sign_Pixel_Height

2

CONFIGURE: D etermin e tti e s ign width in pixels as required by Die specification (PRL2.3.2.3.2.1-2.3.2.32.3}. RECORD this information as:

»Required_Sign_Pixel_Width

3

SET-UP: Determine the actual sign height in pixels. RECORD this information as:

»Actual_Pixel_Height

4

SET-UP: Determine the actual sign width in pixels. RECORD this information as:

»Actual_Pixel_Width

5

GET the following objects): »vmsSignHeightPixels .0 »vmsSignWidthPixels .0

Pass /Fail (Section 3.5.1.2.2.1}

6

VERIFY tti at tti e RESPONSE VALUE for vmsSignHeightPixels. 0 is equal to Required_Sign_Pixel_Height.

Pass IFail (PRL 2.3.2.3.2.12.3.2.3.2.3}

7

VERIFY that the RESPONSE VALUE for vmsSignWidthPixels.0 is equal to Required_Sign_Pixel_Width.

Pass iFail (PRL 2.3.2.3.2.12.3.2.3.2.3}

8

VERIFY that the RESPONSE VALUE for vmsSignHeightPixels.O is equal to Actual_Pixel_Height.

Pass 1 Fail (Section 3.5.1.2.2.1}

9

VERIFYthat the RESPONSE VALUE for vmsSignWidthPixels.0 is equal to Actual_Pixel_Width.

Pass 1 Fail (Section 3.5.1.2.2.1}

Page 10 in the Supplement

(Additional Notes from the Author: Slide 41: To the right of the text, an excerpt from NTCIP 1203 Test Case / Test Procedure 1.6 shows a table with the steps to be performed, with the following column headings: Step; Test Procedure; Results; and Additional References.)

 

Slide 42:

Slide 42: Case Study. A placeholder graphic showing a Traffic Management Center indicating that a Case Study follows.

 

Slide 43:

Learning Objective #3

Case Study: NTCIP 1209 v02 - TSS

Pages 11-12 in the Supplement

 

Slide 44:

Learning Objective #3

TSS Case Study: PRL and RTM

3.2.8 Protocol Requirements List (PRL) Table

User Need Section Number

User Need

FR Section Number

Functional Requirement

Conformance

Support / Project Requirement

Additional Specifications

2.5.2.1

Reset the TSS

3.4.1.3.1

Restart the TSS

M

Yes

3.4.1.3.2

Reinitialize User Settings

M

Yes

3.4.1.3.3

Restore Factory Defaults

M

Yes

3.4.1.3.4

Retune

M

Yes

3.4.1.3.8

Execute Pending Configuration

O.1

Yes/No

3.4.1.3.9

Abort Pending Configuration

O.1

Yes/No

3.4.1.3.10

Validate Pending Configuration

O.1

Yes/No

REQUIREMENTS TRACEABILITY MATRIX (RTM)

Requirement ID

Requirement

Dialog ID

Dialog

Object ID

Object

3.4.1.3

Control the TSS

3.4.1.3.1

Restart the TSS

4.3.1.1

Reset and Synchronize the TSS

5.2.1

sensorSystem Reset

5.2.2

sensorSystemStatus

Pages 11-12 in the Supplement

(Additonal Notes from the Author: Slide 44: Above, an excerpt from NTCIP 1209 Protocol Requirements List a table is shown with the same column headings as described for slide 32. The first row shows User Need Section Number “2.5.2.1” with User Need “Reset the TSS”. The second row shows FR Section Number “3.4.1.3.1” with Functional Requirement “Restart the TSS”, Conformance “M” and Support / Project Requirement “Yes”.

Below the PRL excerpt is an excerpt from the NTCIP 1209 Requirements Traceability Matrix, with column headings Requirement ID, Requirement, Dialog ID, Dialog, Object ID, and Object, and showing Requirement ID 3.4.1.3 and 3.4.1.3.1 – Restart the TSS.)

 

Slide 45:

Learning Objective #3

TSS Case Study - Dialog

4.3.1.1 Reset and Synchronize the TSS

The standardized dialog for a management station to restart, reinitialize, restore, retune, re-sync, run short diagnostics or long diagnostics of a TSS shall be as follows:

  1. (Precondition) None
  2. The management station shall GET the sensorSystemStatus.x state. If the state of sensorSystemStatus is 'initializing', 'pendingConfigurationChange', or ValidatingPendingConfiguration', then the management station shall abort the process
  3. The management station shall SET the sensorSystemReset.y state to 'restart', 'reinitializeUserSettings', 'restoreFactoryDefaults', 'retune', 'resyncSamplingPeriods', 'shortDiagnostics', or 'fullDiagnostics'
  4. The management station shall GET the sensorSystemStatus.x state
  5. If the management station gets no response, then repeat Step d up to maximum TSS initialization time
  6. If the sensorSystemStatus.x state is 'initializing', then repeat Step d
  7. If sensorSystemStatus.x state is 'oK', then the TSS reset is complete
  8. If sensorSystemStatus.x state NOT 'oK', then the reset may not have completed, did not complete normally, or an error was encountered during the process. The management station shall abort the process

Pages 11-12 in the Supplement

(Additional Notes from the Author: Slide 45: This is an excerpt from NTCIP 1209 Dialogs shows the dialog for 4.3.1.1 – Reset and Synchronize the TSS.)

 

Slide 46:

Learning Objective #3

TSS Case Study - Test Case Specification

Test Case Number

Test Case Name

Test

Procedure

Object(s) Under Test Variables

Result

TC1205-001

Restart TSS

TP1205-001

sensorSystemStatus.0, Reset_Command = sensorSystemReset.O 'restart'

sensorSystemStatus. 0 = oK

Pages 11-12 in the Supplement

(Additional Notes from the Author: Above, an excerpt from the Student Supplement of the Test Case Specification created for this webinar shows a table with a single entry, where Test Case Number is TC1205-001, Test Case Name is Restart TSS, Test Procedure is TP1205-001, Object(s) Under Test are sensorSystemStatus.0 and sensorSystemReset.0, variables are Reset_Command = ‘restart’, and Result is sensorSystemStatus.0 = oK.)

 

Slide 47:

Learning Objective #3

TSS Case Study - Test Procedure

Test Procedure: TP1209-001

Title: Reset the TSS

Description: This Test Case verifies that the operator can correctly reset the TSS.

Pass/Fail Criteria: The DUT shall pass every verification step included within the Test Case in order to pass the Test Case

Variables: Reset_Command Command to be implemented

Test Step Number

Test Step

Results

1

GET sensorSystemStatus G

Pass / Fail

2.

IF the RESPONSE VALUE to sensorSystemStatus 0 is Initializing', pending Configuration Change', or validatingPendingConfiguration' EXIT the Test Procedure, and correct the deficiency before restarting the test

3

SET sensorSystemReset.0 to ResetCommand

Pass / Fail

4.

GET sensorSystemStatus.0

Pass / Fail

5.

IF the RESPONSE VALUE for sensorSystemStatus 0 equals 'initializing', then GOTO Step 4

NOTE-If the RESPONSE VALUE remains at Initializing'for more than the maximum TSS initialization time, this test fails

Pass / Fail

6.

VERIFY that the RESPONSE VALUE for sensorSystemStatus.0 equals oK'

Pass / Fail

Page 13 in the Supplement

(Additional Notes from the Author: Slide 47: This is an excerpt from the Student Supplement of the Test Procedure Specification created for this webinar shows Test Procedure ID TP1209-001 as captured from the Student Supplement.)

 

Slide 48:

Slide 48: Poll:  A placeholder graphic of multiple raised hands indicating that a Poll follows.

 

Slide 49:

Learning Objective #3

According to IEEE 829, which of the following are included in Test Procedures?

  1. Inputs
  2. Execution conditions
  3. Steps to execute
  4. Expected results
  5. All of the above

 

Slide 50:

Learning Objective #4

Standards developed without SEP

 

Slide 51:

Learning Objective #4

Conformance Groups

Purpose

 

Slide 52:

Slide 52: Case Study:  A placeholder graphic showing a Traffic Management Center indicating that a Case Study follows.

 

Slide 53:

Learning Objective #4

NTCIP 1205 CCTV Example

Slide 53: NTCIP 1205 CCTV Example.  Please see the Extended Text Description below.

Photo by Kent Flemmer, Flemmer Photography

(Extended Text Description: Slide 53: To the right of the text is a picture. In the background is a city skyline. A freeway leads from the city out of frame lower-right. A pan-tilt-zoom camera is shown on the left aimed at the freeway.)

 

Slide 54:

Learning Objective #4

Conformance Groups

Mandatory and Optional Groups

Table 4-2: Conformance Statement Table

Conformance Group

Reference

Conformance Requirement

Configuration

NTCIP 1201:1996

mandatory

Database Management

NTCIP 1201:1996, Amendment 1

optional

Time Management

NTCIP 1201:1996, Amendment 1

optional

CCTV Configuration

NTCIP 1205

mandatory

Extended Functions

NTCIP 1205

optional

Motion Control

NTCIP 1205

optional

On-Screen Menu Control

NTCIP 1205

optional

(Additional Notes from the Author: Slide 54: Above, an excerpt from NTCIP 1205 showing Table 4-2: Conformance Statement Table.)

 

Slide 55:

Learning Objective #4

NTCIP 1205 CCTV Example

Test Design Specification

4.1.1 CCTV Configuration Conformance Group

Object or Table Name

Reference

Conformance Requirement Within the group

rangeZoom Limit

NTCIP 1205

mandatory

timeoutZoom

NTCIP 1205

mandatory

4.1.3 Motion Control Conformance Group

Object or Table Name

Reference

Conformance Requirement Within the group

positionZoomLens

NTCIP 1205

mandatory

(Additional Notes from the Author: Slide 55: These are two excerpts from NTCIP 1205. The first, from table 4.1.1 – CCTV Configuration Conformance Group, shows the objects rangeZoomLimit and timeoutZoom. The second from table 4.1.3 – Motion Control Conformance Group, shows the object positionZoomLens.)

 

Slide 56:

Learning Objective #4

NTCIP 1205 CCTV Example

Test Design Specification

 

Slide 57:

Learning Objective #4

NTCIP 1205 CCTV Example

Test Cases

Appendix A:

Test Case Number

Test Case Name

Test Procedure Steps

Object(s) Under Test

Variables

Result

TC1205-001

Zoom absolute - maximum telephoto

TP1205-003 Steps 4-10

positionZoomLens.0

Mode = 2 (absolute) Speed_Tele_Fast = 127 Offset =

rangeZoomLimit.0

Camera should zoom to its maximum setting at its maximum speed

TC1205-007

Zoom past rangeZoomLimit.O

TP1205-003 Steps 39-41

positionZoomLens.0; rangeZoomLimit.0

Mode = 1 (absolute) Speed_Tele_Fast = 127 Offset = 65535

Response Error is badValue

TC1205-008

Zoom for greater duration than timeoutZoom.0

TP1205-003 Steps 40-46

positionZoomLens.0; timeoutZoom.0

Mode = 3 (continuous) Speed Tele Slow = 10 Offset =

rangeZoomLimit.0

Camera begins zooming toward its maximum telephoto setting, but stops after

Zoom_Timeout seconds

Pages 14-16 in the Supplement

(Additonal Notes from the Author: Slide 57: This is an excerpt from the Student Supplement Appendix A showing TC1205-001, TC1205-007 and TC1205-008.)

 

Slide 58:

Learning Objective #4

NTCIP 1205 CCTV Example

Test Procedures

Test Procedure: TP1205-003

Title: Zoom Camera

Description: This Test Case verifies that 1lie operator can correctly zoom the camera in and out
Pass/Fail Criteria: The DUT shall pass every verification step included within the Test Case in order to pass the Test Case. Variables: Speed Tele Fast [85.. 127] Speed Wide Fast [-85..-128] Speed Tele Mid [42..84] Speed_Wide_Slow [-1-41] Speed_Tele_Slow [1..41] Zoom_TimeoLit [0. 65535] (in milliseconds)

Test Step Number

Test Step

Results

1.

Get rangeZoomLimit .O

Pass / Fail

2.

RECORD this integer value and its two-byte hex value as:

» ZoomLimit

» ZoomJJmrMHex

3.

Set timeoutZoom.0 to 0: turning off this feature.

Pass / Fail

4.

Set positionZoomLens.0 to
Mode: 2 (absolute)
Speed: Speed_Tele_Fast
Position or Offset: Zoom_Limit

Pass / Fail

5.

Delay for 10 seconds

6.

Verify that the camera zoomed to its absolute telephoto position.

Pass / Fail

7.

Get positionZoomLens.O

Pass / Fail

8.

Verify that the Response Value equals Mode: 02

Speed: Speed_Tele_Fast Position or Offset: Zoom_Limit_Hex

Pass / Fail

9.

Get positionQueryZoom.O

Pass / Fail

10.

Verify that the Response Value equals ZoomLimit. A Response Error of noSuchName indicates that positionQueryZoom.0 is unsupported.

Pass / Fail / Pass

Unsupported

Pages 17-19 in the Supplement

(Additional Notes from the Author: Slide 58: This table is an excerpt from the Student Supplement showing TP1205-003, a Test Procedure created for this webinar.)

 

Slide 59:

Learning Objective #4

Additional Test Documents

These are used in addition to the Test Plan and Test Specifications.

 

Slide 60:

Learning Objectives

1. Describe, within the context of the testing lifecycle, the role of Test Plans, Test Design Specifications, Test Cases, and Test Procedures

2. Describe the purpose and content of Test Design Specifications, Test Cases, and Test Procedures

 

Slide 61:

Learning Objectives (Cont'd)

3. For standards using Systems Engineering Process (SEP), detail the manner that Protocol Requirements Lists (PRLs) and Requirements to Test Cases Traceability Matrices (RTCTMs) can be used to create Test Specifications

4. For standards that do not use SEP, detail the manner that Conformance Groups can be used to create Test Specifications

 

Slide 62:

Slide 62: Activity.  A placeholder graphic of a hand typing on a computer keyboard indicating an activity follows.

 

Slide 63:

What Did We Learn Today?

  1. The Test Plan is created early in the Project Life Cycle, and defines the testing to be performed from a management-level perspective.
  2. Test Design Specifications detail the testing to be performed.
  3. Test Cases define the inputs , expected results, and test conditions.
  4. Test Procedures define the steps to be performed to execute the tests.
  5. PRL and RTM are two items found in standards created using SEP.
  6. Conformance Groups are found in standards created without using SEP.

 

Slide 64:

For More Information

 

Slide 65:

Curriculum Path (Testing)

Slide 65:  Curriculum Path (Testing).  Please see the Extended Text Description below.

(Extended Text Description: Slide 65: Curriculum Path (Testing): A graphical illustration indicating the sequence of training modules for the standards that include Testing content. Each module is represented by a box with the name of the module in it and an arrow showing the logical flow of the modules. The first box is labeled “T101 Introduction to ITS Standards Testing.” An arrow from this box connects it to a box labeled “T201 How to Write a Test Plan”. An arrow from this box connects it to a box labeled “T202 Overview of Test Design Specifications, Test Cases, and Test Procedures”. Three arrows from this box connect to three additional boxes labeled “T311 Applying Your Test Plan to the NTCIP 1203 v03 DMS Standard”, “T313 Applying Your Test Plan to the NTCIP 1204 v03 ESS Standard”, and “T3XX Applying Your Test Plan to NTCIP/TMDD/ATC Standards”.)

 

Slide 66:

Slide 66: Questions. A placeholder graphic of a light bulb indicating questions are to be entertained.