OpsHub Integration Manager (OIM) helps bridge the information gap in semiconductor verification and testing. When Cadence vManager and Jana Connect are integrated using OIM, the coordination between product management and verification teams becomes seamless. With OIM synchronization, manual updates are automated, ensuring changes made in one system are reflected in the other. In this video, you will learn how OpsHub facilitates seamless integration between Cadence vManager and Jama Connect.

As the Systems Architect, I will begin by creating a new Requirements Entity in Jama Connect by selecting Verification Requirement under the category Add. Under Verification Requirements, I will add details such as Name, Description, Requirement, Status, Acceptance Criteria, Priority, and Weight. Once completed, the Verification Requirements entity will be created in the selected folder.

Next, I will select the newly created Verification Requirement by clicking on New Item under Add to create Sub Verification Requirements. I will update attributes like Name, Description, Requirement, Status, Acceptance Criteria, and Priority, then click Save and Close to create the sub-verification requirement.

To further demonstrate the structure, I will create additional Sub Verification requirements at the same level and add the necessary details. Upon completion, I will save and close to finalize these requirements. Additionally, I will create another layer by adding a fresh sub verification requirement, again including all required details such as Name, Description, Requirement, Status, Acceptance Criteria, Priority, and Weight.

Meanwhile, observe that OpsHub Integration Manager is synchronizing the newly created requirements and sub-requirements in Cadence vManager as sections. Now, I will navigate to Cadence vManager and open the Verification Plan (V Plan). Here, you can see that the requirements and sub-requirements created in Jama Connect have successfully synced into vManager, including all their details, within the V Plan Hierarchy window.

Now, as the Verification Engineer, I will select a sub-requirement and create a New Plan Test Case. Once the test case is created, I will click on it to rename the entity. Next, I will select Metrics under Planning and map it with the test case, adding parameters such as the description. I will then click on Details from the bottom panel to proceed.

Continuing as the Verification Engineer in V Manager, I will conduct a Grade Analysis by running a regression. By clicking on Grade Analysis, the tool runs an internal regression for the associated test. Once the analysis is complete, I will click Sync to make the regression output available at both the test case and section levels in vManager.

Once the Grade Analysis is successfully completed, I will navigate back to Jama Connect. The test case associated with sections in vManager is now available in Jama Connect, including all its details. Additionally, all information under requirements and sub-requirements is also reflected in Jama.

Back in vManager, the requirement has now been fulfilled. As the verification engineer, I will change the Status from Draft to Publish. Finally, returning to Jama Connect, we can see that the status has been updated to Publish.

That completes the demo. Thanks for watching.