There are two key aspects of delivering quality products: choice of systems and collaboration between cross-functional teams. While the choice of systems impacts the productivity of a team, cross-functional collaboration strengthens communication to make better decisions faster.
The integration of PTC’s Codebeamer and Cadence vManager using OpsHub Integration Manager (OIM) enables strong teamwork, complete transparency, enhanced traceability, and increased efficiency between the development, QA, and requirements management teams to fulfill the customer’s need on time and make the verification process more robust.
OpsHub Integration Manager integrates Codebeamer and vManager bidirectionally and ensures all historical and current data is available to each user in their preferred system with full context in real time.
In this video, we will showcase how to integrate PTC’s Codebeamer with Cadence vManager using OpsHub Integration Manager.The product owner in Codebeamer creates a system requirement specification, gives it a name and description, and saves it. The product owner now adds a child system requirement specification, gives it a name, and saves it.
The parent and child system requirement specifications created in Codebeamer will successfully synchronize in vManager. The system requirement specification and child system requirement specification get synchronized in vManager as section and subsection, respectively.
Here, in vManager, to view the synchronized section and subsection, the verification engineer clicks on sync so that the section and subsection details are visible on the vManager UI from the vManager database. Both the section and subsection are reflected in vManager.
The verification engineer now navigates to details to change the status from Draft to Active. Back in Codebeamer, the product owner refreshes the page to view the updated status, which now reads “to verify.”
Now, in vManager, the verification engineer adds 2 metric ports of type test case port. The verification engineer adds the first metric port and then goes ahead and adds the second metric port.
In Codebeamer, both the metric ports have successfully synchronized as test cases under the child system requirement specification. In vManager, the verification engineer clicks on metrics to map existing mapping patterns to these metric ports.
The verification engineer now clicks on individual metrics to map them with the test case ports. Once the mapping is complete, the verification engineer executes the verification run.
Once the analysis is complete, the grade results are rolled up and are preserved in Cadence vManager database using VPLAN script. The grade results from the section and subsection will get synchronized in the system requirement specification and child system requirement specification in Codebeamer. The product owner refreshes the page to view the synchronized grade results.
Back in vManager, the verification engineer goes ahead and changes the status of the subsection and section to “Approved”.
Finally, now in Codebeamer, the product owner refreshes the page to view the status of the child system requirement specification, which is updated to show “Verified,” and then views the updated status of the system requirement specification, which shows “Accepted.”
This completes the demo. Thanks for watching.