Module 15 - A313b

A313b: Specifying Requirements for ESS Systems Based on NTCIP 1204 v03 Standard

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:

A313b
Specifying Requirements for ESS Systems Based on NTCIP 1204 v03 Standard

 

Slide 4:

Target Audience

 

Slide 5:

Instructor

Slide 5: Instructor.  Headshot of instructor Ken Vaughn, P.E., President, Trevilon Corporation.

Ken Vaughn, P.E.
President
Trevilon Corporation
Herndon, VA, USA

Course Developer: Joerg "Nu" Rosenbohm

 

Slide 6:

Recommended Prerequisites

 

Slide 7:

Curriculum Path (SEP)

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

(Extended Text Description: Slide 7: A graphical illustration indicating the sequence of training modules for the standards related to specifying environmental sensor stations (ESS). 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 and the current module highlighted. The first box is labeled “I101 Using ITS Standards: An Overview.” An arrow from this box connects it to a highlighted box labeled “A101 Introduction to Acquiring Standards-based ITS Systems,” representing this module. An arrow from this box connects it to a box labeled “A102 Introduction to User Needs Identification.” An arrow from this box connects it to a box located at the start of the next line labeled “A201 Details on Acquiring Standards-based ITS Systems.” An arrow from this box connects it to a box labeled “A313a Understanding User Needs for ESS Systems Based on NTCIP 1204 v03 Standard.” Finally, an arrow from this box connects it to a box labeled “A313b Specifying Requirements for NTCIP 1204 v03.”)

 

Slide 8:

Value of ESS Modules Group

 

Slide 9:

Learning Objectives

  1. Discuss the structure of the standard
  2. Use the protocol requirements list (PRL) and requirements traceability matrix (RTM) to specify the standardized structure of requirements
  3. Use the RTM to specify the standardized design. Include the requirements from the PRL and RTM in the specification
  4. Understand how to specify requirements not covered by the standard
  5. Infer the relationship between selecting requirements and testing

 

Slide 10:

Learning Objective #1

NTCIP Family

Slide 10:  NTCIP Family.  Please see the Extended Text Description below.

(Extended Text Description: Relevant descriptive information provided by author for this figure: Slide 10: A graphic of the communication levels of the NTCIP standards. The bottom level is the Plant Level and includes boxes for Dial-up, Fiber, Coax, Wireless, Twisted Pair, and Leased Line. The next higher level is called the Subnetwork Level and includes PPP, Ethernet, and PMPP. The next level is called the Transport Level and includes TCP/IP, UDP/IP, and T2/NULL. The next level is called the Application Level and includes C2C XML, DATEX, FTP, TFTP, SNMP, and STMP. The next level is called the Information Level and includes C2C Messages, Files, Data Objects, and Dynamic Objects. These boxes are connected to an overarching box also in the Information Level labeled Functional Area Data Dictionaries with the left hand side identifying C2C Data Dictionaries and the right hand side labeled NTCIP Data Dictionaries. The NTCIP Data Dictionaries is highlighted with a circle indicating that it is the subject of the NTCIP 1204 v03 standard. The figure shows a multi-level diagram with 5 different layers marked ‘information level’ on the top, ‘application level’ below it, followed by ‘transport level’, ‘subnetwork level’ and ‘plant level’ on the bottom. Each of these levels has several boxes associated with it. Each box contains the abbr of a standard and its NTCIP standard number. A circle around the box named ‘NTCIP Data Dictionaries’ has a callout line stating that the ESS Standard (NTCIP 1204) is an ‘information level’ standard.)

 

Slide 11:

Learning Objective #1

Review of NTCIP 1204 - ESS

 

Slide 12:

Learning Objective #1

Functional Requirements Section

 

Slide 13:

Learning Objective #1

What is a Requirement?

 

Slide 14:

Learning Objective #2

Architectural Requirements

 

Slide 15:

Learning Objective #2

Data Exchange Req's - ESS Manager

 

Slide 16:

Learning Objective #2

Data Exchange Req's - Sensor Manager

 

Slide 17:

Learning Objective #2

Data Exchange Req's - Pavement Treatment System (PTS)

 

Slide 18:

Learning Objective #2

Data Exchange Req's - Backwards Compatibility

 

Slide 19:

Slide 19:  Polling.  A placeholder slide showing hands raised signifying polling activities.

 

Slide 20:

Poll Exercise

Assume the following User Need:

A transportation system operator may need to monitor the temperature at the ESS location.

Which of the listed requirements fulfills this user need?

  1. Retrieve Temperature
  2. Retrieve Humidity
  3. Retrieve Daily Minimum and Maximum Temperatures

 

Slide 21:

Learning Objective #2

Protocol Requirements List (PRL) -Definition

 

Slide 22:

Learning Objective #2

PRL - Columns "User Needs" and "Functional Requirements"

User Need ID

User Need

FR ID

Functional Requirement Conformance

Project Requirement

Additional Project Requirements

2.5

Features

M

Yes

2.5.1

ESS Manager Features

M

Yes

2.5.1.1

Generic Features

M

Yes

(See F.1.2)

2.5.1.2

Monitor Door Status

P

Yes / No

3.5.1.2.1

Retrieve ESS Door Status

M

Yes/NA

2.5.1.3

Monitor Power

O

Yes / No

3.5.1.2.2

Retrieve Battery Status

O.6 (1..*)

Yes/No/ NA

3.5.1.2.3

Retrieve Line Volts

O.6 (1..*)

Yes/No/ NA

(Additional Graphic Details: The following columns are highlighted by a green border: "User Need ID", "User Need", "FR ID", and "Functional Requirement")

 

Slide 23:

Slide 23: Activity. A placeholder graphic with an image of hand over a computer keyboard to show that an activity is taking place.

 

Slide 24:

Learning Objective #2

Knowledge of the PRL

Enter answers in the chat pod

 

Slide 25:

Learning Objective #2

Knowledge of the PRL

Enter answers in the chat pod

 

Slide 26:

Learning Objective #2

Knowledge of the PRL

Enter answers in the chat pod

 

Slide 27:

Learning Objective #2

PRL - Column "Conformance"

User Need ID

User Need

FR ID

Functional Requirement

Conformance

Project Requirement

Additional Project Requirements

2.5

Features

M

Yes

2.5.1

ESS Manager Features

M

Yes

2.5.1.1

Generic Features

M

Yes

(See F.1.2)

2.5.1.2

Monitor Door Status

O

Yes / No

3.5.1.2.1

Retrieve ESS Door Status

M

Yes / NA

2.5.1.3

Monitor Power

O

Yes / No

3.5.1.2.2

Retrieve Battery Status

O.6 (1..*)

Yes/No/ NA

3.5.1.2.3

Retrieve Line Volts

O.6 (1..*)

Yes/No/ NA

(Additional Graphic Details: The "Conformance" column is highlighted with a green border."

 

Slide 28:

Learning Objective #2

PRL - Column "Support / Project Requirement"

User Need ID

User Need

FR ID

Functional Requirement

Conformance

Project Requirement

Additional Project Requirements

2.5

Features

M

Yes

2.5.1

ESS Manager Features

M

Yes

2.5.1.1

Generic Features

M

Yes

(See F.1.2)

2.5.1.2

Monitor Door Status

O

Yes/No

3.5.1.2.1

Retrieve ESS Door Status

M

Yes/NA

2.5.1.3

Monitor Power

O

Yes/No

3.5.1.2.2

Retrieve Battery Status

O.6 (1..*)

Yes/No/NA

3.5.1.2.3

Retrieve Line Volts

0.6 (1..*)

Yes/No/NA

(Additional Graphic Details: The "Project Requirements" column is highlighted with a green border.)

 

Slide 29:

Learning Objective #2

PRL - Column "Additional Project Requirements"

User Need ID

User Need

FR ID

Functional Requirement

Conformance

Project Requirement

Additional Project Requirements

2.5.2.1 (Weather)

Monitor Weather Conditions

O.2 (1..*)

Yes/No/NA

2.5.2.1.1 (Pressure)

Monitor Atmospheric Pressure

O.3 (1..*)

Yes/No /NA

3.5.2.3.2.1

Retrieve

Atmospheric

Pressure

M

Yes/NA

3.6.1

Required Number of Atmospheric Pressure Sensors

M

Yes/NA

The ESS shall support at least      atmospheric pressure sensors.

(Additional Graphic Details: The "Additional Project Requirements" column is highlighted with a green border.)

 

Slide 30:

Learning Objective #2

PRL - Completing the PRL - Review

 

Slide 31:

Learning Objective #2

PRL - Example of PRL usage

User Need ID

User Need

FR ID

Functional Requirement

Conformance

Project Requirement

Additional Project Requirements

2.5

Features

M

Yes

2.5.2

Sensor Manager Features

O.1 (1..*)

Yes / No

2.5.2.1 (Weather)

Monitor Weather Conditions

O.2 (1..*) Yes/No

2.5.2.1.1 (Pressure)

Monitor Atmospheric Pressure

O.3 (1..*)

Yes/No /NA

3.5.2.3.2.1

Retrieve Atmospheric Pressure

M

Yes/NA

3.6.1

Required Number of Atmospheric Pressure Sensors

M

Yes/NA

The ESS shall support at least      atmospheric pressure sensors.

(Additional Graphic Details: Within the "Project Requirement" column, "Yes" is circled in red to indicate that the following are "Project Requirements": "Sensor Manager Features", "Monitor Weather Conditions", "Monitor Atmospheric Pressure", "Retrieve Atmospheric Pressure", and "Required Number of Atmospheric Pressure Sensors".)

 

Slide 32:

Learning Objective #3

Requirements Traceability Matrix (RTM) - Definition

 

Slide 33:

Learning Objective #3

RTM - Definition (Cont.)

 

Slide 34:

Learning Objective #3

RTM Table - Overview

Req ID

Dialog

Requirement

Object ID

Add'l Requirements/Object

3.5.1

ESS Manager Requirements

3.5.1.1

ESS Configuration Requirements

3.5.1.1.1

F.3.1

Retrieve ESS Characteristics

5.2.1

essNtcipCategory

5.2.2

essNtcipSiteDescription

5.3.1

essTypeofStation

5.4.1

essLatitude

5.4.2

essLongitude

5.5.1

essReferenceHeight

 

Slide 35:

Learning Objective #3

RTM - Columns "Object ID" and "Additional Requirements"

Req ID

Dialog

Requirement

Object ID

Add'l Requirements/Object

3.5.1

ESS Manager Requirements

3.5.1.1

ESS Configuration Requirements

3.5.1.1.1

F.3.1

Retrieve ESS Characteristics

5.2.1

essNtcipCategory

5.2.2

essNtcipSiteDescription

5.3.1

essTypeofStation

5.4.1

essLatitude

5.4.2

essLongitude

5.5.1

essReferenceHeight

 

Slide 36:

Learning Objective #3

RTM - Example

Req ID

Dialog

Requirement

Object ID

Add'l Requirements/Object

3.5.1

ESS Manager Requirements

3.5.1.1

ESS Configuration Requirements

3.5.1.1.1

F.3.1

Retrieve ESS Characteristics

5.2.1

essNtcipCategory

5.2.2

essNtcipSiteDescription

5.3.1

essTypeofStation

5.4.1

essLatitude

5.4.2

essLongitude

5.5.1

essReferenceHeight

The requirement 3.5.1.1.1 (Retrieve ESS Characteristics) is fulfilled by using standardized dialog F.3.1 (Generic SNMP Get Interface ) and it relates to the objects: essNtcipCategory (5.2.1), essNtcipSiteDescription (5.2.2), essTypeofStation (5.3.1), essLatitude (5.4.1), essLongitude (5.4.2), and essReferenceHeight (5.5.1)

 

Slide 37:

Learning Objective #3

RTM - Example - Dialog details

F.3.1 Generic SNMP Get Interface

SNMP defines a generic process by which a management station can retrieve data from a device. This process consists of a Get request (GET) and a Get Response as depicted in Figure 22. Both the Get request and the Get Response messages contain a list of objects as defined by the varBindingList structure (see Annex C.4.1.4).

The RTM (Annex a) customizes this generic process by calling out the appropriate objects to meet specific requirements as defined in Section 3.

Slide 37:  RTM - Example - Dialog details.  Please see the Extended Text Description below.

(Extended Text Description: Relevant descriptive information provided by author for this figure: Slide 37: There is a figure on this slide showing a UML sequence diagram. This sequence shows the sequence of events to perform a GET operation, with a stick figure representing the Management Station that issues the GET command. A box to the right represents the controller, which receives the command, processes it, assembles the response package, and sends it back to the requesting management station.)

Figure 22 SNMP Get Interface

 

Slide 38:

Learning Objective #3

RTM - Dialogs and Interoperability

 

Slide 39:

Slide 39:  Polling.  A placeholder slide showing hands raised signifying polling activities.

 

Slide 40:

Poll Exercise

Which of the following elements are not part of the RTM?

  1. User needs supported by the standard
  2. Requirements supported by the standard
  3. Standardized dialogs to fulfill requirements
  4. Objects to fulfill requirements

 

Slide 41:

Learning Objective #2

Project Specifications - Overview

Slide 41:  Project Specifications - Overview.  Please see the Extended Test Description below.

(Extended Text Description: Slide 41: This is a table entitled "Contract Documents" contains two large rectangular sections stacked one on top of another. The upper sections is titled "Product Specifications". A three-column table is embedded in the "Product Specifications" section. The columns of the embedded chart are "Hardware Specifications", "Software Specifications", and "Communication Interface Specifications". Under "Hardware Specifications" are the following: "Functional Reqts.", "Performance Reqts.", "Structural Reqts.", "Mechanical Reqts.", "Electrical Reqts.", and "Environmental Reqts". Under "Software Specifications" are "Functional Reqts." and "Performance Reqts". Under"Communication Interface Specifications" are "Functional Reqts.", which is highlighted in red, "Performance Reqts.", and Protocol Reqts.". The lower section of the main "Contract Documents" table is titled "Contract Requirements". Under this section are the following bullet points: "Contractual requirements during system development", "Contractual requirements during testing", "Contractual requirements during deployment/integration", and "Contractual requirements during operations/maintenance".)

 

Slide 42:

Learning Objective #2

Project Specifications - Contents

 

Slide 43:

Learning Objective #2

Project Specifications - Considerations

 

Slide 44:

Learning Objective #2

Project Specifications - Performance Requirements

3.6.21 Maximum Response Time for Requests

The ESS shall process all requests in accordance with all of the rules of the relevant base standards (i.e., NTCIP 1103 v01 and NTCIP 2303:2001), including updating the value in the database and initiating the transmission of the appropriate response (assuming that the ESS has permission to transmit) within the Maximum Response Time. If the agency specification does not indicate the Maximum Response Time, the Maximum Response Time shall be 100 milliseconds. The Maximum Response Time is measured as the time between the receipt of the last byte of the request and the transmission of the first byte of the response.

 

Slide 45:

Learning Objective #2

Project Specifications - Coordination of Requirements

 

Slide 46:

Learning Objective #4

Specifying Requirements NOT Covered by the Standard = Extensions

 

Slide 47:

Slide 47: Activity. A placeholder graphic with an image of hand over a computer keyboard to show that an activity is taking place.

 

Slide 48:

Learning Objective #4

Extensions - Activity about Benefits/Drawbacks

What do you think are the benefits and drawbacks associated with extensions (allowing and creating them) to the NTCIP standards?

Enter answers in the chat pod

 

Slide 49:

Learning Objective #4

Extensions - Benefits

 

Slide 50:

Learning Objective #4

Extensions - Example of Benefits

Let us pretend that Agency A wants to add an over-height sensor to an ESS installed at a tunnel. Such a sensor is not currently covered by any NTCIP standard. This requirement is therefore not supported by NTCIP 1204 v03. Agency A could define a new object and could start to monitor the over-height sensor using an existing dialog (F.3.1 - Generic SNMP GET Interface).

 

Slide 51:

Learning Objective #4

Extensions - Drawbacks

 

Slide 52:

Learning Objective #5

User Needs <—>Validation and
Requirements <--->Verification

Slide 52:  User Needs/Validation and Requirements/Verification.  Please see the Extended Text Description below.

(Extended Text Description: Slide 52: 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 links of Subsystem Verification Plan, System Verification Plan, and System Validation Plan are circled for emphasis. The left side of the “V” has a descending arrow running parallel to the side. "Agency Requirements & Specification Development" appear on the upper half of the left arrow next to "System Requirements". "Test Documentation Preparation" appears on the lower half of the left arrow, near the "High-Level Design" and "Detailed Design" sections. The bottom is labeled “Implementation”. There is an ascending arrow running parallel to the right side of the "V". Beside the right arrow are six items listed from the bottom of the arrow to the top: "1. Prototype Test", "2. Design Approval Test", "3. Factory Acceptance Test", are next to the "Unit/Device Testing" Segment; "4. Incoming Device Test", and "5. Site Acceptance Test" are placed next to the "Subsystem Verification" segment; and "6. Burn-in and Observation Test" is next to the "System Verification & Deployment" section. At the bottom, a rightward facing arrow is labeled “Time Line".)

 

Slide 53:

Learning Objective #5

Relationship between Selecting Requirements and Testing

Requirement

Test Case

ID

Title

ID

Title

3.5

Data Exchange Requirements

3.5.1

ESS Manager Requirements

3.5.1.1

ESS Configuration Requirements

3.5.1.1.1

Retrieve ESS Characteristics

C.2.3.1.1

ESS Characteristics

Additional Notes from the Author: Slide 53: A table that maps each requirement to one or more test procedures. Each requirement is identified by the clause number and title of the requirement and each test procedure is identified by its clause number and title.)

 

Slide 54:

Learning Objective #5

Test Case Definition in NTCIP 1204 v03

Example

Test

Case: 1.1

Title:

ESS Characteristics

Description:

This test case verifies that the ESS accurately reports its type, category and location and allows a management station to edit the site description.

Variables:

 

Pass/Fail Criteria:

The device under test (DUT) shall pass every verification step included within the Test Case to pass the Test Case.

Step

Test Procedure

Device

1

GET the following object(s):
»essNtcipCategory.0
»essNtcipSiteDescription.0
»essTypeofStation.0
»essLatitude.0
»essLongitude.0
»essReferenceHeight.0

Pass / Fail
(Sec. 3.5.1.1.1)

2

VERIFY that the RESPONSE VALUE for essNtcipCategory.0 is APPROPRIATE.

NOTE—See NTCIP 1204 v03 Sec. 5.2.1 for valid enumerated values.

Pass / Fail
(Sec. 5.2.1)

ETC

ETC

ETC

Test Case Results

Tested By:

Date Tested:

Pass / Fail

Test Case Notes:

(Additional Notes from the Author: Slide 54: The standard form used to document a test procedure. It includes a header that shows the title, description, test variables, and pass fail criteria; the body that lists each step of the procedure; and a footer that can be used to record the name of the tester, the test date, and any notes from testing.)

 

Slide 55:

Learning Objective #5

Testing in Project Specifications

 

Slide 56:

Summary

 

Slide 57:

What Did We Learn Today?

  1. A protocol requirements list (PRL) is used to link the user needs to the functional requirements
  2. Tracing of selected functional requirements to dialogs and objects is standardized within the requirements traceability matrix Table.
  3. Interoperability is achieved via the use of PRL and RTM as well as standardized test procedures.
  4. Extensions may be used to specify non-standardized functions but are sources for interoperability problems.
  5. A completed PRL and a reference to the RTM should be integrated into the project specifications as part of the plan, specification, and estimate package.

 

Slide 58:

Resources

 

Slide 59:

Next Steps

 

Slide 60:

Slide 60:  Questions.  A placeholder graphic image with word "Questions? at the top, and an image of a lit light bulb on the lower right side.