Module 50 - T309
T309: Applying Your Test Plan to Ramp Meter Control (RMC) Units Based on NTCIP 1207 Standard v02
HTML of the Student Supplement
(Note: This document has been converted from the Student Supplement 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.)
T309: Applying Your Test Plan to Ramp Meter Control (RMC) Units Based on NTCIP 1207 Standard v02
Table of Contents
Introduction/Purpose - 2
Samples/Examples - 2
Reference to Other Standards - 9
Case Studies - 9
Glossary - 9
References - 10
Study Questions - 10
Module Description
This module assists user agencies in their efforts to create test plans specific to their ramp meter control (RMC) needs based on the NTCIP 1207 Standard v02. Prior to developing such a test plan, the user is expected to be knowledgeable about the NTCIP 1207 Standard v02 and testing methodologies. The agency is also expected to have developed its own user needs and requirements related to the NTCIP 1207 Standard (discussed in modules A309A and A309B).
This module is based on the IEEE 829 formats for test documentation and reviews sample test documentation that should result from performing the tests identified, including test logs, test summary, and test incident reports. It also guides agencies in verifying that delivered products comply with the agency's NTCIP specifications.
This module includes example test cases and test procedures for specific requirements that reflect the four different methods of testing (inspection, analysis, demonstration, and formal test). It discusses how the tests may be selected during various testing phases, such as prototype, factory acceptance, and site acceptance tests. This module also covers the role of verification—ensuring the product was built right—as part of the testing life cycle, and presumes well-developed requirements traceable to user needs as discussed in modules A309a and A309b. The module covers the last step in the test cycle to insure that the product will be contractually accepted by the agency as built.
1. Introduction/Purpose
- Final contract acceptance for Procurement
- Clear, unambiguous quality gate for Designers and Manufacturers
- Ongoing incoming inspection test during deployment for Installers
- Ongoing diagnostic test for deployed equipment for Maintenance
2. Samples/Examples
Within the systems life cycle, Module T309 covers the elements of the Vee model shown:
(Extended Text Description: Author's relevant description: Graphic depicts the standard VEE project workflow model with Testing to be Undertaken Here circled around the four right-hand levels of the VEE. The four levels circled include, from bottom to top, Unit/Device Testing, Subsystem Verification, System Verification & Deployment, and System Validation. Taken with permission from US Department of Transportation, Systems Engineering for Intelligent Transportation Systems, USDOT, January 2007)
RMC units are tested at each level, using level tests as defined in the IEEE 829 Standard:
(Extended Text Description: New graphic created by the author for this course depicting the right side four levels of the VEE model workflow with an arrow directed upwards from the word Levels. The four levels include, from bottom to top, Units/Devices, Subsystems, System Verification and System Validation.)
Each level test of the RMC unit is traceable back to the left of the Vee model as shown:
(Extended Text Description: New graphic created by the author for this course repeating the graphic from Slide 12, with four arrows directed to the right towards the four levels of the left side of the VEE workflow model and the word Traceability above the arrows. The four levels include, from bottom to top, Units/Devices, Subsystems, System Verification and System Validation. On the right, the levels include, from bottom to top, Detailed Design, High-Level Design, Requirements, and Concept of Operations.)
Test workflow is conducted in three steps as Planning, Documentation, and Execution with Reports:
(Extended Text Description: Author's relevant description: Graphic depicts the standard VEE project workflow model with Test Planning and Test Document Preparation identified with the left side of the VEE and Test Execution and Reporting identified with the right side of the VEE. Taken with permission from US Department of Transportation, Systems Engineering for Intelligent Transportation Systems, USDOT, January 2007)
The IEEE 829 Standard describes level test plans and the master test plan. The master test plan is not required:
(Extended Text Description: Graphic depicts hierarchy of Master Test Plan box at top with lines connecting to Unit Test Plan box, Subsystem Integration Test Plan box, and System Acceptance Test Plan box. Graphic is reused from prior modules. The top level (Master Test Plan) has the following items associated with it: Integrity level scheme and choice; Overall test processes, activities, and tasks; Test levels and documents. The bottom level has the following items associated with it: Scope of test level, Resources, Test method(s).)
Test sequence work flows from master test plan if used, then unit, subsystem, and acceptance tests:
(Extended Text Description: Graphic depicts Unit Interim Test Status Report box with a line connecting to Unit Test Logs box. Unit Test Logs box has lines connecting to Unit Test Report box, Subsystem Integration Test Report box and System Acceptance Test Report box. Each of those three boxes have a line connecting to Master Test Report box.)
The IEEE 829 Standard describes test documentation as shown:
(Extended Text Description: Graphic depicts a Master Test Plan box at the top with lines connecting to Unit Test Plan box, Subsystem Integration Test Plan box and System Acceptance Test Plan box. The Unit Test Plan box has a line connecting to Unit Test Design box. Unit Test Design box has a line connecting to Unit Test Cases and another line connecting to Unit Test Procedures box. The top level (Master Test Plan) has the following items associated with it: Integrity level scheme and choice; Overall test processes, activities, and tasks; Test levels and documents. The second level has the following items associated with it: Scope of test level, Resources, Test method(s). The third level has Detail updates for test methods, Features to be tested. And on the bottom level, associated with Unit Test Cases is the text Input, Output; and associated with Unit Test Procedures is the text Test setup, Execution instructions.)
Additional test documentation described by IEEE 829 Standard:
(Extended Text Description: Author's relevant description: Graphic depicts Unit Interim Test Status Report box with a line connecting to Unit Test Logs box. Unit Test Logs box has lines connecting to Unit Test Report box, Subsystem Integration Test Report box and System Acceptance Test Report box. Each of those three boxes have a line connecting to Master Test Report box. )
Example of a ramp meter Requirements Test Case Traceability Matrix:
| Requirement Test Case | |||
| ID | Title | ID | Title |
|---|---|---|---|
| 1. | Metered Lane Main Configuration | ||
| 1.1 | Maximum Number of Metered Lanes | ||
| TC1.1 | Test the Boundaries | ||
| 1.2 | Number of Metered Lanes | ||
| TCI.2 | Test the Combinations | ||
| 1.3 | Metered Lane Configuration Table | ||
| TC2.1 | Test the Min Meter Time | ||
| TC2.2 | Test the Min Red | ||
| TC2.3 | Test the Min Green | ||
Ramp Meter Test Documentation includes one or more Test Cases per Test Procedure:
(Extended Text Description: Author's relevant description: Graphic depicts a Unit Test Plan box at the top with an arrow connecting down to a Unit Test Design box. This box has three arrows pointing down to the next level of boxes: Unit Test Case 1, Unit Test Case 2, and Unit Test Case 3. Unit Test Case 1 points down to a fourth level box, Unit Test Procedure 1. The Unit Test Case 2 box also points down to Unit Test Procedure 1. The Unit Test Case 3 box has two arrows pointing down to the fourth level of boxes, Unit Test Procedure 2 and Unit Test Procedure 3. At the top, Unit Test Plan has three bullets, Scope of test level, Resources, Test method(s). Next to Unit Test Design are two bullets, Detail updates for test methods, Features to be tested. Next to the Unit Test Cases is Input, Output. And next to the Unit Test Procedure boxes is Test setup, Execution instructions.)
Key elements of a ramp meter installed at the roadside:
(Extended Text Description: Author's relevant description: New graphic created by author for this module depicting a roadside electrical cabinet containing Advanced Transportation Controller, input and output load switches. The inputs are shown connected to vehicle detectors. The output load switches are shown connected to a traffic signal head. A double-ended arrow connects the roadside cabinet assembly to a traffic management computer.)
Ramp meter unit level test environment:
(Extended Text Description: Author's relevant description: New graphic created by author for this module depicting an ATC 5201 or ATC 5202 controller with an arrow labeled Signals directed to the right towards an Intersection Simulator and an arrow labeled Detectors directed left from the Intersection Simulator toward the ATC. A cloud graphic is depicted with a double ended arrow labeled NTCIP 1207 located between the cloud and the ATC, plus another double ended arrow labeled NTCIP 1207 located between the cloud and a computer labeled Test Software.)
Examples of ramp meter controller conformance groups, which are sets of managed objects:
| Ref | Areas | Clause of Profile | Status | Support |
|---|---|---|---|---|
| B.5 | Metered Lane Conformance Group | NTCIP 1207-3.3 | M | Yes |
| B.12 | Configuration Conformance Group | NTCIP 1207 2.2 | M | Yes |
| B.10 | Physical I/O Conformance Group | NTCIP 1207 3.7 | O | Yes / No |
| - Metered Lane Output | NTCIP 1207 3.7 | O | Yes / No | |
| - Dependency Group Output | NTCIP 1207 3.7 | O | Yes / No |
Example of ramp meter controller requirements traceability matrix:
| Rq.lD | Requirement | Dialog | | Object Reference and Title |
|---|---|---|---|
| 1. | Metered Lane Configuration | B.5 Metered Lane Conformance Group | |
| 1.1 | Set maximum # of metered lanes | 3.4.1.1 rmcMaxNumMeteredLanes | |
| 1.2 | Set number of metered lanes | 3.4.1.2 rmcNumMeteredLanes | |
| 2. | |||
| 2.1 | |||
Example of ramp meter controller requirements test case traceability matrix:
| Requirement | Test Case | ||
|---|---|---|---|
| ID | Title | ID | Title |
| 1. | Metered Lane Configuration | ||
| 1.1 | Set maximum # of metered lanes | TC1.1 | Test the Boundaries |
| 1.2 | Set number of metered lanes | TCI.2 | Test the Combinations |
Example of ramp meter controller test case:
| Test | Title: | ||
|---|---|---|---|
| Case: TC1.1 | Description | This Test Case verifies the maximum number of metered lanes that can be SET by the Central Station. The test is conducted just below, just above and exactly at the boundary | |
| Variables | Max Lanes | From Project Requirements | |
| Max Lanes - 1 | From the Test Plan | ||
| Max Lanes +1 | From the Test Plan | ||
| Pass/Fail Criteria | 1. The DUT shall accept data at Max Lanes 2. The DUT shall accept data at Max Lanes -1 3. The DUT shall return an error at Max Lanes +1 | ||
Example of ramp meter controller test procedure:
| Step | Test Procedure | Results |
|---|---|---|
| 1 | Configure: SET the Max Lanes = 2, record the DUT response | |
| 2 | SET the number of Metered Lanes = 1, record the DUT response | |
| 3 | SET the number of Metered Lanes = 2, record the DUT response | |
| 4 | SET the number of Metered Lanes = 3, record the DUT response |
3. Reference to Other Standards
- IEEE Std 829-2008 - IEEE Standard for Software and System Test Documentation
- NTCIP 1207 Version v02.06 National Transportation Communications for ITS Protocol, Object Definitions for Ramp Meter Control (RMC), (www.ntcip.org)
- NTCIP 1201 Version v03.13a, National Transportation Communications for ITS Protocol, Global Object Definitions (www.ntcip.org)
- NTCIP 8007 Version 1.21, National Transportation Communications for ITS Protocol, Testing and CA Documentation within NTCIP Standards (www.ntcip.org)
- NTCIP 9001 Version v04, National Transportation Communications for ITS Protocol, The NTCIP Guide (www.ntcip.org)
- Institute of Transportation Engineers, ATC 5201 Advanced Transportation Controller (ATC) Standard Version 06, ATC Joint Committee, 30 July 2012
- Institute of Transportation Engineers, ATC 5202 Model 2070 Controller Standard Version 03, ATC Joint Committee, 28 December 2012
4. Case Studies
- M-0446 Ramp Metering Feasibility Study for Durham and Wake Counties, National Research Final Report, version 6.0, February 15, 2013. Study includes data from Atlanta, GA, Minneapolis/St. Paul, MN, Washington State, Louisiana, Kansas City, MO, Nevada, and the United Kingdom.
- Twin Cities Ramp Meter Evaluation Executive Summary for Minnesota Department of Transportation, February 1, 2001
- Georgia Milepost, "Georgia Activates Ramp Meters", Georgia.gov, Summer - Fall 2008
5. Glossary
| Term | Definition |
|---|---|
| Agency Specification | A document that has been prepared by an agency to define requirements for a subject item or process when procured by the agency. |
| ATC | Advanced Transportation Controller |
| Compliance | A condition that exists when an item meets all of the requirements of an agency specification. |
| Concept of Operations | A document that describes the purpose for a system project, including a description of the current and proposed system, as well as key user needs that the new system is required to address. |
| Conformance | A condition that exists when an item meets all of the mandatory requirements as defined by a standard. It can be measured on the standard as a whole, which means that it meets all mandatory (and applicable conditional) requirements of the standard or on a feature level (e.g., it conforms to feature 3 as defined in section 1.2.3), which means that it meets all mandatory (and applicable conditional) requirements of the feature. |
| CG | Conformance Group |
| DUT | Device Under Test |
| ITS | Intelligent Transportation Systems |
| LTP | Level Test Plan |
| MTP | Master Test Plan |
| PRL | Protocol Requirements List |
| RMC | Ramp Meter Control |
| RTCTM | Requirements Test Case Traceability Matrix |
| RTM | Requirements Traceability Matrix |
| TMC | Traffic Management Center |
6. References
- Systems Engineering Guidebook for Intelligent Transportation Systems Version 3.0 Systems Engineering Model (ops.fhwa.dot.gov/publications/seitsguide/seguide.pdf)
- T202: Overview of Test Design Specifications, Test Cases and Test Procedures
- T203 Part 1 of 2: How to Develop Test Cases for an ITS Standards-based Test Plan, Part 1 of 2
- T203 Part 2 of 2: How to Develop Test Cases for an ITS Standards-based Test Plan, Part 2 of 2
- T204 Part 1 of 2: How to Develop Test Procedures for an ITS Standards-based Test Plan, Part 1 of 2
- T204 Part 2 of 2: How to Develop Test Procedures for an ITS Standards-based Test Plan, Part 2 of 2
7. Study Questions
1. Which of the below is not a reason to test an RMC unit?
- Satisfy system requirements
- Testing is part of the NTCIP 1207 Standard v02
- Solve the right problem
- Satisfy user needs
2. Which is not a testing process within the life cycle?
- Test planning
- Preparation of test documentation
- Test execution and reporting
- Identification of system requirement
3. Which is not a reason to use the IEEE 829 Standard?
- IEEE 829 is part of NTCIP 1207 Standard v02
- Provides familiar documents
- Standard definition of terms
- Reuse in later projects
4. Which is not a part of a Level Test Plan?
- Introduction
- Test details
- Planning for multiple levels of test
- Test management
5. When is the test documentation completed?
- Before the test is executed
- Only during the test execution
- Only after the test is executed
- During and after the test execution
6. What is the primary purpose of the RTCTM?
- Sets the testing workflow sequences
- Correlates User Needs to Requirements
- Describes the Optional Objects needed to fulfill Requirements
- Correlates each RMC Requirement to Test Case