Module 53 - T251

T251: Center-to-Center (C2C) Reference Implementation (RI) Introduction

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:

(Extended Text Description: 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 - Transit" 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 is the logo for the U.S. Department of Transportation, Office of the Assistant Secretary for Research and Technology.)

Slide 2:

(Extended Text Description: This slide, entitled "Welcome" has a photo of Ken Leonard, Director, ITS Joint Program Office, on the left hand side, with his email address, Ken.Leonard@dot.gov. A screen capture snapshot of the home webpage is found on the right hand side - for illustration only - from August 2014. Below this image is a link to the current website: www.its.dot.gov/pcb - this screen capture snapshot shows an example from the Office of the Assistant Secretary for Research and Development - Intelligent Transportation Systems Joint Program Office - ITS Professional Capacity Building Program/Advanced ITS Education. Below the main site banner, it shows the main navigation menu with the following items: About, ITS Training, Knowledge Exchange, Technology Transfer, ITS in Academics, and Media Library. Below the main navigation menu, the page shows various content of the website, including a graphic image of professionals seated in a room during a training program. A text overlay has the text Welcome to ITS Professional Capacity Building. Additional content on the page includes a box entitled What's New and a section labeled Free Training. Again, this image serves for illustration only. The current website link is: https://www.its.dot.gov/pcb.)

Slide 3:

T251: Center-to-Center (C2C) Reference Implementation (RI) Introduction

(Extended Text Description: Title slide: This slide displays the title of the course, "Center-to-Center (C2C) Reference Implementation (RI) Introduction" with the logo of the C2C RI version 2 software underneath.)

Slide 4:

Instructor

Kenneth Vaughn, P.E.

President Trevilon LLC

Magnolia, TX, USA

Slide 5:

Learning Objectives

• Recognize purpose of C2C Reference Implementation
• Acknowledge key capabilities and limitations of the C2C RI
• Follow process for producing test documentation that relies upon the C2C RI
• Recognize results a tester might produce after using the C2C RI

Slide 6:

Learning Objective 1

• Recognize purpose of C2C Reference Implementation

Slide 7:

Understand C2C Communications

ITS: A complex network that needs proper analysis

(Extended Text Description: Author's relevant description: ITS: A complex network that needs proper analysis: This slide depicts an overview of an ITS network. On the left, it shows the real-time data capture and management functions of ITS. This is depicted with a circle, representing the ITS data environment, being fed by a variety of sources infrastructure data, vehicle data, weather data, truck data, transit data, and data from mobile devices. On the right, the figure shows how the ITS data environment circle that collected all of this information offers other services, which include: weather applications, transit signal priority, real-time traveler information, fleet management/dynamic route guidance, real-time signal phase and timing optimization, and safety alert and advisories.)

Slide 8:

Understand C2C Communications

National ITS Architecture is the result of the analysis

(Extended Text Description: National ITS Architecture is the result of analysis: This slide depicts what is known as the "Sausage Diagram" of the National ITS Architecture. It depicts different types of subsystems arranged into four major classifications: Travelers, Centers, Vehicles, and Field. The Travelers class includes Remote Traveler Support and Personal Information Access. The Centers class includes Traffic Management, Emergency Management, Payment Administration, Commercial Vehicle Administration, Maintenance and Construction Management, Information Service Provider, Emissions Management, Transit Management, Fleet and Freight Management, and Archived Data Management. The Vehicles class includes Vehicle, Emergency Vehicle, Commercial Vehicle, Transit Vehicle, and Maintenance and Construction Vehicle. The Field class includes Roadway, Security Monitoring, Roadway Payment, Parking Management, and Commercial Vehicle Check. The four classes are connected through "sausages" that represent communication technologies labeled Vehicle-to-Vehicle communications, Wide Area Wireless (Mobile) Communications, Fixed Point – Fixed Point Communications, and Field – Vehicle Communications. Each Traveler type is connected to the Wide Area Wireless and Fixed Point – Fixed Point Communications. Each Vehicle type is connected to Vehicle-Vehicle Communications, Wide Area Wireless, and Field-Vehicle Communications. Each Center type is connected to Fixed Point – Fixed Point Communications. Each Field type is connected to Fixed Point – Fixed Point Communications and Field – Vehicle Communications. This slide includes the information icon in the lower right corner.)

Slide 9:

Understand C2C Communications

This module focuses on center-to-center only

(Extended Text Description: Author's relevant description: This module focuses on center-to-center only: This slide zooms in on the Center class from the previously described "Sausage Diagram" and shows how centers are connected to each other via Fixed Point – Fixed Point Communications.)

Slide 10:

Understand C2C Communications

National ITS Architecture service packages (sample)

(Extended Text Description: Author's relevant description: National ITS Architecture service packages (Sample): This slide depicts a two-column table showing a portion of the service packages included in the National ITS Architecture. The left-hand column, shows three "groups" of service packages labeled: Traffic Signals, Transit, and Traveler Information. The right-hand column identifies specific service packages. The Traffic Signals group includes Emergency Vehicle Preemption, Freight Signal Priority, Intelligent Traffic Signal System, and Transit Signal Priority. The Transit group includes Dynamic Ridesharing, Dynamic Transit Operations, Integrated Multi-Modal Electronic Payment, Intermittent Bus Lanes, Smart Park and Ride System, Transit Connection Protection, and Transit Stop Request. The Traveler information group includes Advanced Traveler Information Systems and Traveler Information – Smart Parking. The Advanced Traveler Information Systems service package is highlighted to show that we will select that one for further investigation.)

Slide 11:

Understand C2C Communications

Service packages depict information flows

(Extended Text Description: Author's relevant description: Service packages depict information flows: This slide depicts the service package diagram for Advanced Traveler Information Systems. It depicts the various subsystems involved in the operation of the service package and the information flows that are exchanged by these subsystems. The upper left-hand portion of the diagram is highlighted to indicate that it is the portion of the diagram that will be discussed.)

Slide 12:

Understand C2C Communications

C2C RI focuses on Traffic Management flows

(Extended Text Description: Author's relevant description: C2C RI focuses on Traffic Management flows: This slide depicts the upper left-hand portion of the Advanced Traveler Information Systems service package diagram. It shows the Traffic Management Center sending four information flows to the Transportation Information Center including: incident information, road network conditions, traffic control information, and traffic images. At the end, an arrow appears at the bottom of the screen to indicate that we are now going to look further down the diagram.)

Slide 13:

Understand C2C Communications

Same flows may be provided by other centers

(Extended Text Description: Author's relevant description: Same flows may be provided by other centers: This slide depicts the center left-hand portion of the Advanced Traveler Information Systems service package diagram, which shows various center subsystems and flows. Specifically, the diagram highlights the Emergency Management Center sending incident information to the Transportation Information Center as well as the Maintenance and Construction Management Center sending work zone information, roadway maintenance status, and maintenance and construction work plans to the Transportation Information Center. These flows are covered by the TMDD and are therefore supported by the C2C RI, even though these are not defined as traffic management centers.)

Slide 14:

Understand C2C Communications

Complex systems require proper testing

• Service packages use multiple flows
• Every information flow has to work correctly
• Deployments use multiple services
• Complexity requires proper testing

Slide 15:

Purpose of the C2C RI

Testing verifies interoperability

Interoperability is the main purpose of ITS Standards

The ability of two or more systems or components to exchange information and use the information that has been exchanged -- IEEE 610.12

To realize interoperability, we need:

• User needs (Module A321a)
• Requirements (Module A321b)
• Design (TMDD Standard)
• Verification (Module T321)
• Validation (Module T321)

Slide 16:

Purpose of the C2C RI

Verification is a key step in Systems Engineering

(Extended Text Description: Verification is a key step in Systems Engineering: This slide depicts the version 1 and version 2 logo of the C2C RI. The version 1 logo is the systems engineering V diagram overlaid with the text "Center to Center Reference Implementation." The version 2 logo has a stylized blue arc on the left side with green text that states "ITS Standards" at top with a large, green "C2C RI" as the main focus of the figure. Underneath this text in blue the "C2C RI" is explained as "Center-to-Center Reference Implementation".)

Slide 17:

Purpose of the C2C RI

Subsystem verification is midway through right side

(Extended Text Description: Author's relevant description: Subsystem verification is midway through right side: This slide depicts the Systems Engineering V diagram with overlays on the left side showing that test planning should occur during concept of operations and system requirements; test documentation preparation should occur during High-level design, Detailed design, and Software/Hardware Development and Field Installation. On the right side an overlay shows that this side is the focus of test execution and reporting. Across the center there is an oval showing that the C2C RI assists in the subsystem verification of the high-level design.)

Slide 18:

Purpose of the C2C RI

C2C RI is customizable to your project

Three operational modes of the RI

• Configure: Define which flows are implemented, etc.
• Test: Verify that the flows are properly implemented
• Report: Tests performed and errors discovered

Slide 19:

C2C RI Communications Stack

Architecture, standards, and C2C RI work together

(Extended Text Description: Author's relevant description: Architecture, standards, and C2C RI work together: This slide shows the definition tab of the incident information flow between the Traffic Management Center to the Transportation Information Center as defined in the National ITS Architecture. This screen is displayed by the National ITS Architecture when clicking on this flow in the service package diagram. The definition of the flow is highlighted and we then highlight the communication diagram tab near the top of the figure to show that we will click this tab to get to the next screen. Definitions are shown, such as incident information (Information Flow), Traffic Management Center (Source Physical Object), and Transportation Information Center (Destination Physical Object).)

Slide 20:

C2C RI Communications Stack

Architecture identifies the standards in the stack

(Extended Text Description: Author's relevant description: Architecture identifies the standards in the stack: This slide shows a communication stack that can be used to implement the incident information flow defined on the previous slide; it is a part of the webpage that is displayed after clicking on the communication diagram tab of the Architecture. The stack shows how the Traffic Management Center communicates with the Transportation Information Center using the Open Systems Interconnect (OSI) 7-layer stack with an ITS Application Information Layer on top. The figure also shows how this stack relates to the layer terminology used in ITS where the ITS Application Information Layer is called the Information Level, the top three OSI layers are called the Application Level, the Transport and Network Layers are called the Transport Level, and the lowest two layers are called the Subnetwork Level. The Information and Application Levels are highlighted to shown in bold to indicate that these are the subject of the C2C RI effort. The diagram shows that the stack for this flow includes: ITS Application Information Layer: ITE TMDD Application Layer: IETF HTTP, IETF FTP, NTCIP 2306 Presentation Layer: W3C XML, IETF GZIP Session Layer: Undefined Transport Layer: IETF TCP Network Layer: IETF IPv6 Data Link Layer: LLC and MAC compatible with Physical and Network Physical Layer: Backhaul PHY.)

Slide 21:

C2C RI Communications Stack

Detailed view of the layers tested by C2C RI

(Extended Text Description: Author's relevant description: Detailed View of the layers tested by C2C RI: This slide provides greater detail for the Information and Application Levels of the diagram and shows how they relate to the ITE TMDD and NTCIP 2306 standards. The upper-right of the diagram is in blue and is labeled TMDD Messages, indicating that this standard defines various messages to perform TMC-related operations. Below this are two options shown in green: on the left is SOAP, which is the preferred solution for exchanges with error handling and it includes support for publish/subscribe; on the right is Direct XML, which is a simple solution for one-way exchanges and request-reply without error handling. Below these boxes are two more side-by-side boxes in green. On the left and spanning all of the SOAP box and half of the Direct XML box is HTTP/S, which supports bi-directional exchanges with optional security. On the far right, under only a portion of the Direct XML box, is FTP, which can be used for one-way information flows. Finally, on the far left of the stack and spanning all three layers is a green box labeled WSDL, which allows an owner center to advertise which services are available. The blue boxes represent information the TMDD while the green boxes represent information defined in NTCIP 2306.)

Slide 22:

C2C RI Communications Stack

What does the C2C RI support?

C2C RI is able to verify:

• TMDD v3.03c
• NTCIP 2306 v1.69
• Over standard Internet stack

Others with user-customized test procedures

Slide 23:

C2C RI Communications Stack

How do I obtain the C2C RI?

Download at:

https://www.standards.its.dot.gov/DeploymentResources/Tools

User Manual is included in installation files

Technical support via e-mail at: c2crisupport@transcore.com

Slide 24:

Slide 25:

Question

Which standard is not supported by the C2C RI (without customization)?

Answer Choices

1. Internet Protocol (v4)
2. XML Center-to-Center Profile (NTCIP 2306 v1.69)
3. Transit Communications Interface Profiles (TCIP v5.0)
4. Traffic Management Data Dictionary (TMDD v3.03c)

Slide 26:

Review of Answers

a) Internet Protocol
Incorrect. The C2C RI uses IP for all communications and allows the user to configure the IP address.

b) XML Center-to-Center Profile (NTCIP 2306)
Incorrect. The C2C RI includes a suite of tests to verify that a test system conforms to NTCIP 2306.

c) Transit Communications Interface Profiles (TCIP)
Correct! The C2C RI does not include a test suite for transit data; however, a custom test suite could be developed.

d) Traffic Management Data Dictionary
Incorrect. The C2C RI includes a suite of tests to verify that a test system conforms to the TMDD.

Slide 27:

Learning Objectives

• Recognize purpose of C2CReference Implementation
• Acknowledge key capabilities and limitations of the C2C RI

Slide 28:

Learning Objective 2

• Acknowledge key capabilities and limitations of the C2C RI

Slide 29:

Operational Environment Required

Recommended Minimum System Requirements

• Windows 7 or 8
  • 64-bit Professional
• 2 GHz processor
• 4 GB RAM
• 1 GB Storage
• 1 Gbps Ethernet interface
• Java SE Runtime Environment (JRE) V7.17

Slide 30:

Capabilities and Limitations

What are current limitations? User needs extensive skillset

Information Layer limited to TMDD

Application Layer limited to NTCIP 2306

Slide 31:

Skills Required to Use C2C RI

Skills Needed

(Extended Text Description: Author's relevant description: Skills Needed: This slide provides a list of skills that an operator needs to have to use the C2C RI with each item shown in a box with a blue background and a related image on the left-hand side. The images and text for each item is as follows: 1. The text "*.xml" on an orange background for the item "Encoding languages" 2. An electronic-looking stream of zeros and ones for the item "Protocols" 3. A MS Windows "Settings" icon for the item "Windows networking" 4. Four connected vehicles driving through an intersection for the item "ITS Standards" 5. A hand holding a transparent ball with words on it, with the text "experience" highlighted for the item "Testing experience" 6. The text "<script>" on a reddish background for the item "Scripting language" 7. A clipboard with a sheet of paper with checkboxes and text with a hand hovering over it for the item "System under test".)

Slide 32:

Skills Required to Use C2C RI

Necessary encoding language skills

Basic understanding of:

• XML
  • eXtensible Markup Language
• XSD
  • XML Schema Definition
• WSDL
  • Web Services Description Language

Basic understanding means:

• Familiar with basic structures defined by standards
• Capable of developing and inspecting packets and/or documents, as needed

Slide 33:

Skills Required to Use C2C RI

Necessary protocol skills

Basic understanding of:

• SOAP (if used)
  • Simple Object Access Protocol
• HTTP and/or FTP (as used)
  • Hypertext Transfer Protocol
  • File Transfer Protocol
• TCP/IP networking
  • Transport Control Protocol
  • Internet Protocol

Slide 34:

Skills Required to Use C2C RI

Necessary IT networking skills

Basic understanding and permissions for configuring Windows:

• Internet security

Slide 35:

Skills Required to Use C2C RI

Necessary ITS standards skills

Thorough understanding of:

• Information Layer standards (e.g., TMDD v3.03c)
• Application Layer standards (e.g., NTCIP 2306 v1.69)

Thorough understanding means:

• Familiar with basic structure of standards
• Understand conformance
• Understand compliance (options)
• Understand traceability (NRTM and RTM)
• Capable of quickly referencing all details

Slide 36:

Skills Required to Use C2C RI

Necessary systems engineering skills

Experience in:

• Preparing and understanding test documentation
• Using a Needs to Requirements Traceability Matrix (NRTM)
• Using a Requirements (to design) Traceability Matrix (RTM)
• Using a Requirements to Test Case Traceability Matrix (RTCTM)

Slide 37:

Skills Required to Use C2C RI

Necessary programming skills

To create custom test suites, you also need to know how to:

• Define your custom user needs
• Define your custom requirements
• Write C2C test script files
• Combine this information into a test suite package

Detailed process will be included in the User Manual

Slide 38:

Skills Required to Use C2C RI

Other necessary knowledge of System Under Test (SUT)

• Custom configuration for each system
• Based on supported user needs and requirements

Permissions to operate the SUT

(Extended Text Description: The bottom of the slide also depicts a laptop, labeled C2C RI, displaying the C2C RI logo communicating with (via a blue bi-directional arrow) a photograph of a traffic management center, which is labeled "SUT" for System Under Test.)

Slide 39:

Skills Required to Use C2C RI

Skill set summary

(Extended Text Description: Skills Needed: This slide is identical to Slide 31; it provides a list of skills that an operator needs to have to use the C2C RI with each item shown in a box with a blue background and a related image on the left-hand side. The images and text for each item is as follows: 1. The text "*.xml" on an orange background for the item "Encoding languages" 2. An electronic-looking stream of zeros and ones for the item "Protocols" 3. A MS Windows "Settings" icon for the item "Windows networking" 4. Four connected vehicles driving through an intersection for the item "ITS Standards" 5. A hand holding a transparent ball with words on it, with the text "experience" highlighted for the item "Testing experience" 6. The text "<script>" on a reddish background for the item "Scripting language" 7. A clipboard with a sheet of paper with checkboxes and text with a hand hovering over it for the item "System under test.")

Slide 40:

What Functions Can Be Tested

What does the C2C RI test?

• Standards
  • NTCIP 2306 v1.69
  • TMDD v3.03c
• Center Type
  • Owner center emulation
  • External center emulation
• Types of Tests
  • Valid conditions
  • Invalid conditions

Slide 41:

What Functions Can Be Tested

Sample test cases for NTCIP 2306

(Extended Text Description: Author's relevant description: Sample test cases for NTCIP 2306: This slide includes the table shown on Slide 21 with the WSDL box highlighted. Specifically, the table shows the Information and Application Levels of the diagram and shows how they relate to the ITE TMDD and NTCIP 2306 standards. The upper-right of the diagram is in blue and is labeled TMDD Messages, indicating that this standard defines various messages to perform TMC-related operations. Below this are two options shown in green: on the left is SOAP, which is the preferred solution for exchanges with error handling and it includes support for publish/subscribe; on the right is Direct XML, which is a simple solution for one-way exchanges and request-reply without error handling. Below these boxes are two more side-by-side boxes in green. On the left and spanning all of the SOAP box and half of the Direct XML box is HTTP/S, which supports bi-directional exchanges with optional security. On the far right, under only a portion of the Direct XML box, is FTP, which can be used for one-way information flows. Finally, on the far left of the stack and spanning all three layers is a green box labeled WSDL, which allows an owner center to advertise which services are available. This is the portion of the table that is highlighted for this slide.)

• For NTCIP 2306, C2C RI verifies that a system:
  • Advertises its web services in a conformant manner
    • Ensures advertised file is conformant
    • Ensures advertised file supports the required interfaces

Slide 42:

What Functions Can Be Tested

Sample test cases for NTCIP 2306

(Extended Text Description: Sample test cases for NTCIP 2306: This slide includes the same table shown on Slide 21 and 41, but this time the other NTCIP 2306 boxes (i.e., SOAP, Direct XML, HTTP/S, and FTP) are highlighted.)

• Is able to connect through the required and advertised interface(s)
  • Defined communication stacks
  • Defined exchange patterns
    • Request/Reply
    • Subscription/Publication
    • Publication only

Slide 43:

What Functions Can Be Tested

Sample C2C RI test cases for TMDD

(Extended Text Description: Sample test cases for TMDD: This slide includes the same table shown on Slide 21, 41, and 42 but this time the other TMDD box is highlighted.)

• For the TMDD, the C2C RI verifies that a system:
  • Supports a valid request
  • Properly handles invalid requests
    • Missing fields
    • Incorrect values
    • Etc.
  • Similar tests, reversed, when C2C RI acts as an Owner Center

Slide 44:

Unavailable/Planned Functions

What are planned enhancements?

• Enhanced emulation
  • If RI is acting as Owner Center:
    • RI responds to EC requests, such as:
      • Inventory request
      • Status request
      • Information request
      • Control request

Version 1

Response message is statically determined based on

• A user-defined configuration file

Version 2

Response message is dynamically determined based on

• A user-defined configuration file and
• The contents of the request
  • > E.g. if the request contains filters, the response may contain only a subset of the configuration file

Slide 45:

Unavailable/Planned Functions

What are planned enhancements?

Version 2

• Verification for compliance to §1201 of SAFETEA-LU

(Extended Text Description: Author's relevant description: What are planned enhancements: This slide shows a sample Information Layer Standard Compliance Report from version 2 of the software. The first column shows the User Need ID and is labeled "UN ID". The second column shows the name of the user need and is labeled "User Need". The third column displays the requirement ID and is labeled "Requirement ID". The fourth column shows the data exchange format specification identifier and is labeled "Related DXFS Requirement". The final column shows the pass/fail status of the requirement and is labeled "Results". The full text of the table is shown below:

Information Layer Standard Conformance Report

UN ID	User Need			Results
2.3.1.1	Verify Connection Active			Passed
		Requirement ID	Related DXFS Requirement	Results
		3.3.1.1.1	3.4.1.1.1	Passed
		3.3.1.1.2	3.4.1.1.2	Passed
		3.3.1.1.3	3.4.1.1.3	Passed
		3.3.1.1.4	34.1.1.4	No Test Cases Applicable in this Test Mode
		3.3.1.1.4.1	3.4.1.1.5	No Test Cases Applicable in this Test Mode
		3.3.1.1.5	3.4.1.1.6	Passed

)

Slide 46:

Slide 47:

Question

What skill is not needed to use the C2C RI?

Answer Choices

1. Windows networking
2. X.509 certificates
3. HTTP
4. WSDL

Slide 48:

Review of Answers

a) Windows networking
Incorrect. The user needs to be able to configure the RI host to support incoming messages.

b) X.509 certificates
Correct! The user does not necessarily need to understand how X.509 certificates work as they are not required.

c) HTTP
Incorrect. The user needs to be aware of HTTP as this is often used as an underlying protocol for NTCIP 2306.

d) WSDL
Incorrect. The user needs to be familiar with WSDL as this is how the interface to the system is described.

Slide 49:

Learning Objectives

• Recognize purpose of C2C Reference Implementation
• Acknowledge key capabilities and limitations of the C2C RI
• Follow process for producing test documentation that relies upon the C2C RI

Slide 50:

Learning Objective 3

• Follow process for producing test documentation that relies upon the C2C RI

Slide 51:

IEEE 829 Test Documentation

Relationships of IEEE 829-2008 test documents

(Extended Text Description: Relationships of IEEE 829-2008 test documents: The top of this slide shows a series of right-facing arrow blocks labeled in order "Test Plan", "Test Design", "Test Cases", "Test Procedures", "Execute", and "Test Reports". The first four blocks have an orange background and the last two have a grey background.)

For more information see modules

• T101: Introduction to Standards Testing
• T201: How to Write a Test Plan
• T202: Test Design, Cases & Procedures
• T203: How to Develop Test Cases
• T204: How to Develop Test Procedures
• T321: Applying your Test Plan to TMDD

Slide 52:

Test Plan for C2C

Test plan is a high level document

(Extended Text Description: Test plan is a high-level document: The top of this slide shows a series of right-facing arrow blocks labeled in order "Test Plan", "Test Design", "Test Cases", "Test Procedures", "Execute", and "Test Reports". The first block has a blue background, the next three have an orange background and the last two have a grey background.)

• Types
  • Master Test Plan
  • Level Test Plan
• Context
• Project management issues
• Reference to test design

Slide 53:

Test Plan for C2C

Example C2C RI test plan context

Test plan using C2C RI

• Communications/Functional/Environmental
• Factory/Laboratory/On-Site
• Verification/Validation
• Component/Integration
• Acceptance/Deployment
• Which standards? (NTCIP 2306, TMDD, any custom extensions)

Slide 54:

Test Plan for C2C

C2C RI is an active emulator, not just a sniffer

(Extended Text Description: C2C RI is an active emulator, not just a sniffer: This slide shows the example test environment graphic used in Module T321, which displays a center building, labeled "System Under Test", near the top of the slide connected through a communications cloud to a center on bottom, labeled "External Center", with a PC off to the right side, labeled "Test Software", also connected to the cloud. The entire figure is visually nullified by overlaying a red circle with a slash through it. The slide is then enhanced with a new image on the right side that shows the same "System Under Test" center near the top of the slide connected via a communications cloud to a PC labeled "C2C RI" at the bottom of the slide.)

Example Test Environment in Module T321

Slide 55:

Test Plan for C2C

C2C RI does not develop a test plan

Test plan is not covered by C2C RI

• Test plan is a management plan that should be defined before using C2C RI
• Outline defined by IEEE 829-2008 and provided in Student Supplement

Slide 56:

Test Design for C2C

Test design defines traceability from requirements

(Extended Text Description: Test design defines traceability from requirements: The top of this slide shows a series of right-facing arrow blocks labeled in order "Test Plan", "Test Design", "Test Cases", "Test Procedures", "Execute", and "Test Reports". The first block has an orange background, the next has a blue background, the next two have an orange background and the last two have a grey background. The body of the slide is presented as three bullet points, each with a downward facing chevron to the left of the bullet with text in it. The top is orange and is labeled "Test Plan", the middle is labeled "Test Design" and the bottom is labeled "Test Cases". The bulleted text reads:

• Context and reference to...
• Specific requirements to be tested and reference to...
• Specific scenarios to test

)

Slide 57:

Test Design for C2C

Test design example

Test Plan

• Verify TMDD interface in a laboratory environment for approval of Stage 1 payment

Test Design 1

• Verify that the system supports SOAP message encodings
  • Reference to appropriate test cases

Test Design 2

• Verify that the system supports connection active requests
  • Reference to appropriate test cases

Slide 58:

Test Design for C2C

Test Design Specifications for TMDD

(Extended Text Description: Test Design Specifications for TMDD: This slide shows an example of the Test Case to Requirements Mapping table from the TMDD. The first column shows the User Need ID and is labeled "Need ID". The second column shows the name of the associated test case and is labeled "Test Case Identifier". The third column shows the requirement identifiers that relate to the test case and is labeled "Requirements".

Table 5: TMDD v3.03c Test Case to Requirements Mapping

	Test Case Identifier	Requirements
2.3.1.1	TCS-1-dlCenterActive VerificationRequest-OC-Valid	3.3.1.1.1, 3.3.1.1.5, 3.3.1.1.5.1, 3.3.1.1.5.2.1
	TCS-1-dlCenterActiveVerificationRequest-OC-In Valid-1	3.3.1.1.1, 3.3.1.4.1, 3.3.1.4.1.1, 3.3.1.4.1.2.1
	TCS-1-dlCenterActive VerificationRequest-OC-InValid-2	3.3.1.1.1, 3.3.1.4.1, 3.3.1.4.1.1, 3.3.1.4.1.2.1
	TCS-1-dlCenterActive VerificationRequest-OC-InValid-3	3.3.1.1.1, 3.3.1.4.1, 3.3.1.4.1.1, 3.3.1.4.1.2.1
	TCS-1-dlCenterActive VerificationRequest-OC-InValid-4	3.3.1.1.1, 3.3.1.4.1, 3.3.1.4.1.1, 3.3.1.4.1.2.1
	TCS-1-dlCenterActive VerificationRequest-OC-lnValid-5	3.3.1.1.1, 3.3.1.4.1, 3.3.1.4.1.1, 3.3.1.4.1.2.1

)

Slide 59:

Test Design for C2C

Test designs in the RI Reports

Complete traceability table available on request

Version 1

• Includes a built-in traceability table
• Shows every test that traces to any selected requirement
• Allows user to select when to perform the tests

Version 2

Also allows user-generated traceability report

Slide 60:

Test Case for C2C

Role of test case

(Extended Text Description: Role of test case: The top of this slide shows a series of right-facing arrow blocks labeled in order "Test Plan", "Test Design", "Test Cases", "Test Procedures", "Execute", and "Test Reports". The first two blocks have an orange background, the next has a blue background, the next has an orange background and the last two have a grey background. The body of the slide is presented as three bullet points, each with a downward facing chevron to the left of the bullet with text in it. The top is orange and is labeled "Test Design", the middle is labeled "Test Cases", and the bottom is labeled "Test Procedures". The bulleted text reads:

• Specific requirements to be tested and reference to...
• Specific scenarios, including objective, inputs, outputs, and reference to...
• Specific process used to test

)

Slide 61:

Test Case for C2C

Test case example

Test Design 1

• Verify that the system supports SOAP message encodings

Test Case 1

• Ensure that the system accepts valid SOAP messages
  • Input: Valid TMDD file
  • Output: System accepts message without error
  • Procedure: <reference>

Test Case 2

• Ensure that the system rejects an invalid SOAP message (type element)
  • Input: TMDD file with invalid type element
  • Output: System rejects message with distinct error code
  • Procedure: <reference>

Slide 62:

Test Case for C2C

2306 Test Case Specification

(Extended Text Description: Author's relevant description: 2306 Test Case Specification: This slide shows an example of the three two-column tables related to the test case specification. The first column of the first table shows the Identifier of the test case and is labeled "Identifier". The second column of the first table shows the description of the test case and is labeled "Description". The first column of the second table shows the inputs required for the test case and is labeled "Inputs". The second column of the second table shows the name of the test procedure to implement the test case and is labeled "Procedures". The first column of the third table shows the outputs expected for the test case and is labeled "Outputs". The second column of the third table is empty and is labeled "Procedures". The complete table information is below:

69.1 Test Case Specification identifier

Identifier	Description
TCS-C2CRI-NTCIP2306-WSME-SUT-SIIRR-OC	To verify that the SL"T can communicate with the RT using the protocol stack for SOAP over HTTP with Request-Response defined in the SUT's WSDL document.

69.3 Input Specifications

Inputs	Procedures
The WSDL input file will be user defined for the owner center.	TPS-NTCIP2306-SOAP-RR-OC

69.4 Output Specifications

Outputs	Procedures
The input execution shall generate an RI Test Result Status of Passed or Failed associated with the matching expected result shown in the Test Case Data Variable Table in the appendix.

)

Slide 63:

Test Case for C2C

Test cases in the RI Reports

Supplement contains a complete example of the Test Case Specification

Version 1

• Shows test case descriptions within tool

Version 2

• Will also allow a user to print reports showing test cases

Slide 64:

Test Procedure for C2C

Role of test procedure

(Extended Text Description: Role of test procedure: The top of this slide shows a series of right-facing arrow blocks labeled in order "Test Plan", "Test Design", "Test Cases", "Test Procedures", "Execute", and "Test Reports". The first three blocks have an orange background, the next has a blue background, and the last two have a grey background. The body of the slide is presented as three bullet points, each with a downward facing chevron to the left of the bullet with text in it. The top is orange and is labeled "Test Cases", the middle is labeled "Test Procedures", and the bottom is labeled "Test Steps". The bulleted text reads:

• Specific scenarios, including objective, inputs, outputs, and reference to...
• Step-by-step process used to test
• Specific actions of tester

)

Slide 65:

Test Procedure for C2C

Test procedure example

Test Case

• Ensure that the system accepts valid SOAP messages
  • Input: Valid TMDD file
  • Output: System accepts message without error
  • Procedure: <reference>

Test Procedure defines steps such as

• Configure the Application Layer standard to be used
• Verify that the specified WSDL file exists
• If the file is acceptable, do ...
• Send message ...

Slide 66:

Test Procedure for C2C

TMDD Test Procedure

(Extended Text Description: Author's relevant description: TMDD Test Procedure: This slide shows an example of a test procedure. The first column shows the number of each test step and is labeled "Test Step Number". The second column provides a description of the test step and is labeled "Test Procedure". The third column shows the results of the step is labeled "Results".

Test Step Number	Test Procedure	Results
1	CONFIGURE: Determine the Application Layer Standard that will be used for this test. RECORD this information as: ApplicationLayerStandard	NA
2	CONFIGURE: Determine the dialog performance requirement for Send Center Active Verification Upon Request (NRTM 3.3.1.1.1). RECORD this value as: TMDD_N1R1_Send_Center_Active_Verification_Upon_Request_Para meter	NA
3	CONFIGURE: Determine whether Restrictions - Center Active is required by the specification. (NRTM 3.3.1.1.5.2.1). RECORD this information as: TMDD_N1R8_Restrictions___Center_Active_Supported	NA
4	CONFIGURE: Determine whether Restrictions - Error Report is required by the specification. (NRTM 3.3.1.4.1.2.1). RECORD this information as: TMDD_N1R14_Restrictions___Error_Report_Supported	NA
5	CONFIGURE: Define the message that will be sent to the SUT. RECORD this information as: RequestMessage	NA
6	CONFIGURE: Determine whether an error response message is expected for this test. RECORD this information as: ErrorResponseExpected	NA
7	CONFIGURE: IF ErrorResponseExpected is true, determine the expected error code response for this test. RECORD this information as: ErrorTypeExpected	NA
8	REQUEST-RESPONSE-EC with the following parameters: DIALOG=dlCenterActiveVerificationRequest RESPONSETIMEREQUIRED=TMDD_N1R1_Send_Center_Active_Verification_Upon_Request_Parameter REQUESTMESSAGE = RequestMessage ERRORRESPONSEEXPECTED = ErrorResponseExpected ERRORTYPEEXPECTED = ErrorTypeExpected	PASS/FAIL (3.3.1.1.2, 3.4.2)

)

Slide 67:

Test Procedure for C2C

Implemented test procedures

Supplement contains a complete example of this test procedure

Version 1

• Built in procedures implemented in scripts

Version 2

• Will allow a user to print test procedures

Slide 68:

Slide 69:

Question

Which test document requires information from sources beyond the C2C RI?

Answer Choices

1. Test plan
2. Test design specification
3. Test cases
4. Test procedures

Slide 70:

Review of Answers

a) Test plan
Correct! The test plan is a high-level document and contains management information beyond the scope of the C2C RI.

b) Test design specification
Incorrect. The C2C RI Configuration Report allows the user to map between the requirements and associated test cases.

c) Test cases
Incorrect. The C2C RI Configuration Report identifies the test script used for each test case.

d) Test procedures
Incorrect. The C2C RI Test Script Report provides the test scripts as implemented in the C2C RI tool.

Slide 71:

Learning Objectives

• Recognize purpose of C2C Reference Implementation
• Acknowledge key capabilities and limitations of the C2C RI
• Follow process for producing test documentation that relies upon the C2C RI
• Recognize results a tester might produce after using the C2C RI

Slide 72:

Learning Objective 4

• Recognize results a tester might produce after using the C2C RI

Slide 73:

Hands-On Guidance

Benefits of C2C RI

(Extended Text Description: Benefits of C2C RI: The top of this slide shows a series of right-facing arrow blocks labeled in order "Test Plan", "Test Design", "Test Cases", "Test Procedures", "Execute", and "Test Reports". The first four blocks have an orange background, the next has a blue background, and the last has a grey background.)

C2C RI

• Largely automates testing
  • Simpler
  • More repeatable
  • Less prone to error
• Decreases costs
  • Labor
  • Schedule
• Increases thoroughness
  • Improves quality of product
  • Identifies bugs faster/earlier

See Module T351 for more information

Slide 74:

C2C RI Test Reports

Types of Reports

(Extended Text Description: Types of reports: The top of this slide shows a series of right-facing arrow blocks labeled in order "Test Plan", "Test Design", "Test Cases", "Test Procedures", "Execute", and "Test Reports". The first four blocks have an orange background, the next has a grey background, and the last has a blue background.)

Assist in developing formal test reports:

• Test logs
• Anomaly reports
• Test summary

C2C RI test reports

• Test logs
• Test summaries

Slide 75:

C2C RI Test Reports - Test Logs

Purpose of Log

Purpose of a Test Log

• Chronological record of details
• Assists in repeating process
• Assists in debugging

Slide 76:

C2C RI Test Reports - Test Logs

C2C RI Test Log Reports

• Test Case Detail Log Report
• Test Script Action Log Report
• Message Detail Report

Slide 77:

C2C RI Test Reports - Test Logs

Test Case Detail Log

Purpose of a Test Case Detail Log

• Logs test steps in order of execution
• Logs values used and calculations made
• Logs results of pass/fail steps
• Summarizes reason for failure
• Timestamp
• Script being executed

Slide 78:

C2C RI Test Reports - Test Logs

Test Case Detail Log Report

(Extended Text Description: Test Case Detail Log Report: This slide shows an example of a test case detail log report that shows two tables with some additional background information at top such as the C2C RI version and test suites performed. The upper table shows the Log File Name in the first row, the Log File Creator in the second row, the Log File Creation Date in the third row, and the Log File Description in the fourth and final row. The lower table shows the time in the first column, the test case name in the second column, the test case description in the third column, the Pass/Fail status in the fourth column, and the fail reason in the fifth and final column. The upper portion of the slide is labeled "Background" while the lower table is labeled "Detail". The complete content from the tables is below:

C2C R1 Version: Version 1.0.7
Created by: Minsignares
Test Suites:
Application: NTCIP 2306 v1.69
Information: TMDDv3.03c 08/09/2016 11.20 AM

Log File Name:	c:\c2cri\TRANSCOM Stand-alone Test 2 Run 2.2016-08-09_10-31-35.xml
Log File Creator:	Minsignares
Log File Creation Date:	2016-OB-09_10-31-35
Log File Description:	Second run of the transcom Stand-alone test 2, circumventing a problem discovered in the

Time	Test Case Name	Test Step Description	Pass/Fail	Fail Reason
09/08/2016 10.31.56.368	TCS-C2CRI-NTCIP2306-WSDL-SUT		FAILED
39/08/2016 10.32.00.879		Step 1 CONFIGURE; Determine the URL for the WSDL tile that will be used for this test. RECORD this information as: WSDL File = ittpy/standards2.xcmdata.org :8080/MiddlewareOutbound/w sdl/XCM-TMDD.wsdl	PASSED
39/08/2016		Step 2 CONFIGURE:	PASSED

)

Slide 79:

C2C RI Test Reports - Test Logs

Test Script Action Log

Purpose of a Test Script Action Log

• Primarily a tool for debugging test scripts
• Chronological log of the start and end of each test script
• Logs results of the test script
• Filenames and line numbers
• Shows timestamps

Slide 80:

C2C RI Test Reports - Test Logs

Test Script Action Log Report

Time Stamp	Test Script Action	Results
09/08/2016 10.31.54.539	User Started the Test with selected Test Case Scripts: Application Layer: TCS-C2CRI-NTCIP2306-WSDL-SUT
09/08/2016 10.31.56.352	testCase - Begin Script: jar:file:/C:/C2CRl/dist/RIGUI.jar!/org/fhwa/c2cri/testmodel/TestCase?launcher/xml line: 14 c column: 58
09/08/2016 10.31.56.664	ri-execute-script - Begin Script: jar:file:/C:/C2CRl/dist/RIGUI.jar!/org/fhwa/c2cri/testmodel/TestCase?launcher/xml line: 22 c column: 79 functionId; TCS-C2CRI-NTCIP2306-WSDL-SUT
09/08/2016 10.32.00.879	testStep - Begin Script: jar:file://C :/C2CRI/./TestSuites/NTCIP2306v01 _69Signed.jar!/AppLayer/Scripts/TPS-NTClP2306-WSDL.xml line: 13 column: 187 functionId: Step 1 CONFIGURE: Determine the URL tor the WSDL file that will be used for this test. RECORD this information as: WSDLFile =
09/08/2016 10.32.00.895	testStep - End jar:file://C :/C2CRI/./TestSuites/NTCIP2306v01 _69Signed.jar!/AppLayer/Scripts/TPS-NTClP2306-WSDL.xml line: 13 column: 187 functionId: Step 1 CONFIGURE: Determine the URL tor the WSDL file that will be used for this test. RECORD this information as: WSDLFile =	PASSED

Slide 81:

C2C RI Test Reports - Test Logs

Message Detail Report

• Purpose of a Message Detail Report
  • Logs the messages that are transmitted/received
  • Source and destination
  • Shows complete details of contents
  • Shows timestamps

Slide 82:

C2C RI Test Reports - Test Logs

Message Detail Report

Log File Name:	C:\c2cri\TRANSCOM Stand-alone Test 2 Run 2.2016-08-09_ 10-31 -35.xml
Log File Creator:	Minsignares
Log File Creation Date:	2016-08-09_10-31-35
Log File Description:	Second run of the TRANSCOM Stand-alone test 2, circumventing a problem discovered in the

Time	Message	Source	Destination
08/09/16 10:33:24.605	REQUEST(centerActiveVerificationRequestMsgErrorAddOn)	192.168.2.168:64673	160.79.9.145:8080
tmdd:centerActiveVerificationRequestMsgErrorAddOn.authentication.user-id = tmdd tmdd:centerActiveVerificationRequestMsgErrorAddOn.authentication.password = tmdd@123 tmdd:centerActiveVerificationRequestMsgErrorAddOn.authentication.operator = string tmdd:centerActiveVerificationRequestMsgErrorAddOn.organization-requesting.organization-id = agency.com tmdd:centerActiveVerificationRequestMsgErrorAddOn.organization-requesting.organization-name = string tmdd:centerActiveVerificationRequestMsgErrorAddOn.organization-requesting.organization-location = string tmdd:centerActiveVerificationRequestMsgErrorAddOn.organization-requesting.organization-function = string tmdd:centerActiveVerificationRequestMsgErrorAddOn.organization-requesting.organization-contact-details.contact-id = string tmdd:centerActiveVerificationRequestMsgErrorAddOn.organization-requesting.organization-contact-details.person-name = string tmdd:centerActiveVerificationRequestMsgErrorAddOn.organization-requesting.organization-contact-details.person-title = string tmdd:centerActiveVerificationRequestMsgErrorAddOn.organization-requesting.organization-contact-details.phone-num = string

Slide 83:

C2C RI Test Reports - Test Summaries

Slide 84:

C2C RI Test Reports - Test Summaries

C2C RI Test Summary Reports

• Test Case Summary
• Test Message Summary
• Test Conformance/Compliance

Version 2

• Section 1201 Conformance/Compliance

Slide 85:

C2C RI Test Reports - Test Summaries

Test Case Summary Report

Purpose of a Test Case Summary Report

• Identifies test cases performed, in order
• Identifies each performance as passed/failed
• Timestamp

Slide 86:

C2C RI Test Reports - Test Summaries

Test Case Summary Report

Log File Name:	C:\c2cri\TRANSC0M Stand-alone Test 2.2016-08-09_09-31-32.xml
Log File Creator:	Minsignares
Log File Creation Date:	2016-O8-09_09-31-32
Log File Description:	TRANSCOM Stand-alone Test 2. Aug 9 2016, C2C RI 1.0.7.

Time	Test Case Name	Pass/Fail
Tue Aug 09 09:32:34 EDT 2016	TCS-l-dlCenterActiveVerificationRequest-OC-InValid-2	FAILED
Tue Aug 09 09:42:29 EDT 2016	TCS-l-dlCenterActiveVerificationRequest-OC-InValid-2	PASSED
Tue Aug 09 09:42:58 EDT 2016	TCS-l-dlCenterActiveVerificationRequest-OC-InValid-3	PASSED
Tue Aug 09 09:43:16 EDT 2016	TCS-l-dlCenterActiveVerificationRequest-OC-InValid-4	PASSED
Tue Aug 09 09:43:34 EDT 2016	TCS-l-dlCenterActiveVerificationRequest-OC-InValid-5	PASSED
Tue Aug 09 09:43:52 EDT 2016	TCS-l-dlCenterActiveVerificationRequest-OC-InValid-6	PASSED

Slide 87:

C2C RI Test Reports - Test Summaries

Test Message Summary Report

Purpose of a Test Message Summary Report

• Logs summary of messages transmitted/received
• Shows source and destination
• Shows timestamps

Slide 88:

C2C RI Test Reports - Test Summaries

Test Message Summary Report

Log File Name:	C:\c2cri\TRANSCOM Stand-alone Test 2 Run 2.20l6-Q8-09_10-31-35.xml
Log File Creator:	Minsignares
Log File Creation Date:	2016-08-09_10-31-35
Log File Description:	Second run of the TRANSCOM Stand-alone test 2, circumventing a problem discovered in the

Time	Message	Source	Destination
08/09/16 10:33:24.605	REQUEST (centerActiveVerificationRequestMsgErrorAddOn)	192.168.2.168:64673	160.79.9.145:6080
08/09/16 10:33:24.605	RESPONSE (errorReportMsg)	160.79.9.145:8080	192.166.2.166:64673
08/09/16 10:33:43.315	REQUEST (centerActiveVerificationRequestMsg)	192.168.2 1 68:64683	160.79.9 145:8080
08/09/16 10:33:43.315	RESPONSE (errorReportMsg)	160.79.9.145:8080	192.166.2.166:64663
08/09/16 10:34:00.837	REQUEST (Unknown)	192.166.2.166:64693	160.79.9.145:8080
08/09/16 10:34:00.837	RESPONSE (errorReportMsg)	160.79.9.145:8080	192.168.2.168:64693

Slide 89:

C2C RI Test Reports - Test Summaries

Test Conformance/Compliance Report

Purpose of a Test Conformance/Compliance Report

• Summarizes results against tested requirements/needs
  • Using traceability tables discussed earlier
• Assists in identifying the practical impacts of failure

Slide 90:

C2C RI Test Reports - Test Summaries

Test Conformance/Compliance Report

Information Layer Standard Conformance Report

UN ID	User Need			Results
2.3.1.1	Verify Connection Active			Passed
		Requirement ID	Other Requirements	Results
		3.3.1.1.1	The owner center shall respond within _____ (100 ms -1 hour; Default = 1 minute) after receiving the request See Section 3.4.2.	Passed
		3.3.1.1.4		No Test Cases Applicable in this Test Mode
		3.3.1.1.4.1		No Test Cases Applicable in this Test Mode
		3.3.1.1.5		Passed
		3.3.1.1.5.1		Passed
		3.3.1.4.1		Passed
		3.3.1.4.1.1		Passed

Slide 91:

C2C RI Test Reports - Test Summaries

Section 1201 Conformance/Compliance Report

Purpose of Section 1201 Report

• Summarizes results against
  • SAFETEA-LU Section 1201 requirements
  • CFR Title 23 Part 511 regulations
• An extension of the more basic conformance/compliance report
• Assists in identifying impacts related to Section 1201 compliance

Slide 92:

C2C RI Test Reports - Test Summaries

Section 1201 Conformance/Compliance Report

Information Layer Standard Conformance Report

UN ID	User Need			Results
2.3.1.1	Verify Connection Active			Passed
		Requirement ID	Related DXFS Requirement	Results
		3.3.1.1.1	3.4.1.1.1	Passed
		3.3.1.1.2	3.4.1.1.2	Passed
		3.3.1.1.3	3.4.1.1.3	Passed
		3.3.1.1.4	3.4.1.1.4	No Test Cases Applicable in this Test Mode
		3.3.1.1.4.1	3.4.1.1.5	No Test Cases Applicable in this Test Mode
		3.3.1.1.5	3.4.1.1.6	Passed
		3.3.1.1.5.1	3.4.1.1.7	Passed

Slide 93:

C2C RI Test Reports - Test Summaries

Complete test summary

Additional information for complete test summary

• Tester needs to compile data to prepare IEEE 829 summary
• These reports aid in that preparation
• Tester is ultimately responsible for analysis and recommendations

Slide 94:

Interpret Test Results

Complete test summary

C2C RI output is algorithmic

• May report false failures due to external problems
• Provides information about problem
• Does not judge severity or impact

Tester needs to analyze results

Ultimately needs to determine impact to project

Slide 95:

Limitations of Test Results

What is not tested?

C2C RI does not test

• Implied functionality of messages
• User interface
• Algorithms
• Reliability of the system

Master test plan should consider all aspects

Slide 96:

Slide 97:

Question

Which is the best way to describe the C2C RI- generated test reports?

Answer Choices

1. The conformance report provides the final assessment of whether the implementation conforms to the communications interface
2. When combined together, the various reports produce all of the elements of IEEE 829 test documentation
3. The reports assist the tester in identifying potential issues for further analysis
4. The reports fail to provide the information that they were intended to provide

Slide 98:

Review of Answers

a) Conformance report provides the final assessment
Incorrect. The conformance report produces a formulaic result & may produce an erroneous result if an error was made in testing.

b) When combined, the various reports produce all elements
Incorrect. A proper test summary includes analysis that requires manual review.

c) Reports assist the tester in identifying issues
Correct! Issues identified in the reports should be investigated to determine why a failure was reported.

d) Reports fail to provide what was intended
Incorrect. The reports provide useful information, as intended, but require analysis before final conclusions are drawn.

Slide 99:

Module Summary

• Recognize purpose of C2C Reference Implementation
• Acknowledge key capabilities and limitations of the C2C RI
• Follow process for producing test documentation that relies upon the C2C RI
• Recognize results a tester might produce after using the C2C RI

Slide 100:

TMDD Testing Curriculum

Module T321:
Applying your test plan to the TMDD standard.

Module T251:
Center-to-Center (C2C) Reference Implementation (RI) - Introduction.

Curriculum complete for those not needing hands-on
experience with C2C RI

Module T351:
Center-to-Center (C2C) Reference Implementation (R ) - Applying the C2C Reference implementation.

Slide 101:

Next Course Module

T351: Center-to-Center (C2C) Reference Implementation (RI) - Applying the C2C Reference Implementation

Concepts taught in next module (Learning Objectives):

1. Install and configure the C2C RI on a host system
2. Operate the C2C RI
3. Retrieve the C2C RI results from a test
4. Prepare a report based on the C2C RI results

Slide 102:

Thank you for completing this module.

Feedback

Please use the Feedback link below to provide us with your thoughts and comments about the value of the training.

Thank you!