Jama Connect – Jira Integration with Target Before Sync Configuration Feature

Jama Connect - Jira Integration with Target Before Sync Configuration Feature

Integrating cross-system data every day requires a robust automated data integration solution. Users opting for manual methods of integration most often end up with inaccurate, outdated, and duplicate data, making it inconsistent and untrustworthy. The Search in Target Before Sync feature allows customers to configure search on target system fields with source system fields for mapping purposes. This feature enables OpsHub Integration Manager (OIM) to search for duplicate entities in the source and target systems and indicate to the customer the course of action. This video showcases how OIM enables integration between Jama Connect and Jira with the Target Before Sync Configuration feature.

Experience seamless integration & eliminate data silos with OIM

Schedule a 30-minute live demo with our integration experts

Request a Demo

Video Transcript

Most businesses handle tremendous amounts of data each day; therefore, data integration is a major component of an effective data strategy for every organization. Most customers who integrate manually end up with inaccurate, outdated, and duplicate data, making it inconsistent, untrustworthy, and prone to leakage. The “Search in Target Before Sync” feature helps customers using manual methods or tools configure searches on any target system field linked to the source system field for mapping. This feature allows OIM to search for duplicate entities in the source and target systems and indicate to the customer what the course of action should be.

When the feature is not selected, OIM synchronizes entities normally and creates them in the target system if they were not synchronized already. In this video, we will showcase the integration between Jira and Jama using the target lookup configuration. The product owner creates a feature in Jama, gives it a name, and fills in all mandatory details like the development field before saving it.

The developer creates a feature in Jira in the project that needs to be integrated using OIM and provides a summary that should match the name given to the feature in Jama. Since the summary in Jira is mapped to the name in Jama, users need to fill the Jama ID field with the actual Jama feature ID that was recently created. The Jama ID is a custom field created in Jira by the user.

The feature is successfully created, and the developer goes on to update the summary for the feature and adds a comment to notify the product owner in Jama. In OIM, the entity and project in Jira are mapped to the corresponding entity and project in Jama. Here, we can see that the status and description in Jira are mapped to the status and description in Jama, and the summary in Jira is mapped to the name in Jama. The comments are also enabled. To navigate to the integration page, the OIM admin clicks “Integrate” on the mapping page to begin the integration.

OIM searches for the entity created in the target system, which is Jama, and maps it to the corresponding entity updated in the source system, which is Jira, using the Jama ID provided in the custom field created in Jira. On the integration page, the OIM admin clicks on “Entity Level Advanced Settings” and then on “Override Parameters.” Here, the OIM admin fills in the remote ID, remote link, and selects “Yes” for the “Search in Target Before Sync” option. This option allows users to search for items in Jira coming from Jama based on common attributes before creating an entity in Jira.

Users also need to provide the target search query and click on “Fail the Sync” to avoid duplication of entities or skip creating deleted entities in the target system. During the sync, users can select “Skip the Event” for cases where no entries match the query. Once all the required details are filled, the OIM admin saves and activates the integration. The product owner in Jama refreshes the page to view the updates made to the feature. The comment added in Jira is successfully synchronized to Jama.

That completes the demo. Thank you for watching.

Experience seamless integration & eliminate data silos with OIM

Schedule a 30-minute live demo with our integration experts

Request a Demo

Digital.ai Agility – Azure DevOps Server (TFS) Integration

Digital.ai Agility - Azure DevOps Server (TFS) Integration

Traditional approaches to collaboration and data sync can cause challenges such as loss of data, lengthy timelines, loss of productivity, and lack of clarity. Enterprises today need a modern planning solution that is flexible and scalable and can meet market demands and customer needs. Digital.ai Agility integrations using OpsHub Integration Manager (OIM) drives consistency and efficiency by scaling agile practices across all levels, from teams to the entire product portfolio. OIM integrates Digital.ai Agility with 60+ best-of-breed industry systems. Integrating Digital.ai Agility with Azure DevOps Server (TFS) helps the project, portfolio and development teams achieve greater transparency, traceability, and cross-functional collaboration in a heterogeneous environment, with access to all historical and current data in their preferred system in real-time. Watch the video to learn how OIM enables a bidirectional integration between Digital.ai Agility and Azure DevOps Server (TFS).

Experience seamless integration & eliminate data silos with OIM

Schedule a 30-minute live demo with our integration experts

Request a Demo

Video Transcript

Many enterprises still struggle with the decades-old problem of managing a product portfolio consisting of multiple projects and available resources. Transitioning from a traditional waterfall approach to an agile delivery system can be daunting, with challenges such as identifying, prioritizing, and organizing different products potentially costing heavily.

For enterprises following the orthodox model, integration challenges can range from data loss, lengthy timelines, and productivity loss to lack of clarity, among other issues. What is vital for enterprises today is a modern planning solution that is flexible, scalable, and capable of meeting market demands and customer needs.

Digital.ai Agility drives consistency and efficiency by scaling agile practices across all levels, from teams to the entire product portfolio. OpsHub Integration Manager integrates Digital.ai Agility with 60+ best-of-breed industry systems, enabling multi-tool integrations so product and portfolio teams can achieve greater transparency, feasibility, and cross-functional collaboration. This is accomplished in a heterogeneous environment with access to all historical and current data in their preferred systems in real time.

In this video, we will showcase the integration of Digital.ai Agility with Azure DevOps (VSTS/ TFS) using OIM. No portfolio item has been created yet in Azure DevOps (ADO) and Digital.ai Agility. The product manager in Agility creates a portfolio item, gives it a title, selects the type, adds a description and priority, and saves it. Once the portfolio item is created, the product manager adds an attachment under it and saves it. The portfolio item created in Agility synchronizes to ADO as a feature, providing the developer visibility into the feature they need to work on.

In ADO, the developer refreshes the page to view the feature, which has successfully synchronized from Agility. All details, including the remote link, remote ID, and attachment, have successfully synchronized. The developer starts planning the feature by adding a comment as a clarification question to the product team in Agility and changes the state to “Active”, which synchronizes back to Agility as “In Progress”. This automatic bidirectional synchronization enables the product manager and developer to collaborate effectively on feature clarification.

In Agility, the product manager views the updated details under the portfolio item, which were added under the feature in ADO. The product manager adds a reply in the form of a comment and saves it. In ADO, the developer views the comment added by the product manager in Agility. The developer in ADO then starts breaking down the feature into user stories. For the first user story, the developer changes the link type to “Child,” adds a title and description, and saves it. The developer similarly adds a second user story, adds the title and description, and saves it. Both user stories are created and reflected in ADO.

In Agility, the product manager refreshes the page to view the synchronized user stories from ADO. Both user stories are visible and linked to the portfolio item. In ADO, the QA engineer starts adding test cases under each user story. For the first user story, the QA engineer selects the link type as “Tested By,” changes the work item type to “Test Case,” adds a summary, and saves it. The QA engineer then adds another test case under the second user story.

In ADO, the entire hierarchy, including the parent feature, child user stories, and test cases under each user story, is visible. In Agility, the product manager refreshes the page to view the recently added test cases under the first user story, which have synchronized from ADO. The product manager adds a comment and saves it. The product manager then clicks on the second user story, views the test case added under it, and adds a similar comment before saving it.

In ADO, the QA engineer refreshes the page to view the comment added under the test case for the first user story. The QA engineer responds to the product manager’s comment and saves it. Navigating to the test case under the second user story, the QA engineer views the comment synchronized from Agility, adds a reply, and saves it. In Agility, the product manager navigates to the test cases under each user story to view the comments added by the QA engineer in ADO. Both comments have automatically synchronized back to Agility.

The developer in ADO begins working on the user stories, changes their state to Active, and saves them. In Agility, the product manager views the updated status. Back in ADO, the developer changes the state of the user stories to Resolved, and this change in status is reflected in Agility. The QA engineer then changes the state of the test cases first to “Ready”, and then to “Closed, indicating completion.

The QA engineer changes the state of both user stories to “Closed”, indicating the task’s completion. Once the expected results are fulfilled, the product manager in Agility views the updated status. Status changes made to the test cases are also reflected here. All changes made to the status of user stories and test cases in ADO have bidirectionally synchronized to Agility.

Finally, in ADO, the developer changes the state of the feature from “Active” to “Closed”, indicating its completion. In Agility, the product manager navigates to the portfolio item to view the updated status as Closed. This completes the demo.

Thanks for watching. Integrating Digital.ai Agility with other tools using OIM helps teams gain enhanced visibility into the complete delivery ecosystem, enabling them to produce better quality products faster.

Experience seamless integration & eliminate data silos with OIM

Schedule a 30-minute live demo with our integration experts

Request a Demo

TestRail – Azure DevOps Integration

TestRail - Azure DevOps Integration

In the ALM ecosystem, the choice of systems and powerful collaboration play a significant role in delivering quality products. While the choice of systems impacts a team’s productivity, cross-functional communication helps them get full context into business requirements. In this video, we spotlight the integration between best-of-breed tools, TestRail and Azure DevOps (ADO) using OpsHub Integration Manager (OIM), enabling developers and QA teams to gain greater transparency, visibility and collaboration without impacting productivity. OIM integrates TestRail and ADO bidirectionally – ensuring all the data is available to each user, in their preferred system, with full context in real-time.

Experience seamless integration & eliminate data silos with OIM

Schedule a 30-minute live demo with our integration experts

Request a Demo

Video Transcript

For enterprises, effective collaboration plays a major role in managing projects. The lack of communication and transparency between developers and QA teams can hinder tackling and organizing software testing efforts, impacting productivity and timely delivery of quality products. What teams need is real-time visibility to coordinate seamlessly over planning iterations, defects, quality parameters, and test results to get a complete context of the customer’s requirements.

Integrating TestRail with Azure DevOps using OpsHub Integration Manager (OIM) enhances teamwork and provides clarity into client priorities, thereby reducing manual efforts, errors, and delayed timelines. OIM integrates TestRail and Azure DevOps bidirectionally, ensuring all data is available to each user in their preferred system with content in real time.

Let’s see how OIM enables TestRail and Azure DevOps integration. The verification engineer creates a new requirement in Azure DevOps, gives it a name, description, and saves it. In TestRail, the testing engineer creates four test cases under the existing suite.

For the first test case, the testing engineer adds a title, saves it, and provides Azure DevOps’ requirement ID in the required ID field before saving it again. The test case link automatically synchronizes back to the remote links field in Azure DevOps. The testing engineer then proceeds to add the second and third test cases. However, the third test case is not linked to the requirement created in Azure DevOps. As a result, no remote link syncs back to the remote links field. For the fourth test case, the testing engineer links it with the requirement ID, similar to the first and second cases, and saves it.

All recently added test cases are visible in TestRail with their respective details, including the Azure DevOps requirement ID. In Azure DevOps, the verification engineer views the remote link of the first TestRail case that synced through OIM under the specific requirement. The verification engineer opens the link to view all the details of the case added in TestRail. The remote links for the second and fourth test cases are also visible and synced successfully. However, since the third test case was not linked with the Azure DevOps requirement ID, it did not produce a remote link, and the case with ID C17067 does not reflect in Azure DevOps. This completes phase 1 of the demo.

In phase 2, we will showcase test cases added in Azure DevOps synchronizing back to TestRail. The verification engineer in Azure DevOps adds the first test case, gives it a title, saves it, and links the test case with the parent requirement created in Phase 1 of the demo. Here, the parent requirement is linked to the child test case. The case created in Azure DevOps reflects in TestRail with the parent requirement ID and also as a remote link under Azure DevOps’ requirement.

The verification engineer then creates another test case in Azure DevOps without linking it to a parent requirement. In TestRail, the testing engineer refreshes the page to view the first test case created in Azure DevOps, which has successfully synchronized back with the requirement ID. The first test case is linked with the requirement created in Azure DevOps during Phase 1 of the demo. The testing engineer clicks on the test case to view all the details attached to it. The second test case, which was added in Azure DevOps, also synchronizes back to TestRail but without the requirement ID since it was not linked to any entity in Azure DevOps.

Since the first child test case added in Azure DevOps is linked with the requirement ID in TestRail, the verification engineer in Azure DevOps refreshes the page to view the updated Remote Links field, which now includes a new link to the child test case.

That completes the demo. Thanks for watching.

OpsHub supports TestRail integrations with 60+ ALM, DevOps, ITSM, and CRM systems.

Experience seamless integration & eliminate data silos with OIM

Schedule a 30-minute live demo with our integration experts

Request a Demo

IBM Rational DOORS Next Generation and Verisium Manager Integration

IBM Rational DOORS Next Generation and Verisium Manager Integration

Seamlessly integrate IBM Rational DOORS or DOORS Next Generation (DOORS NG), a best-of-breed requirements management tool, with Verisium Manager (formerly Cadence vManager) for enhanced traceability and real-time updates. This integration fosters a robust digital thread, accelerating your digital transformation. Watch this video to learn how integrating DOORS NG with Verisium Manager provides complete visibility, improved teamwork, and seamless accessibility within your preferred tools, streamlining your entire product lifecycle.  

Manual data exchange between tools often leads to errors and communication gaps. OpsHub Integration Manager (OIM) eliminates these challenges by ensuring smooth, real-time cross-functional collaboration across teams, minimizing manual effort, and guaranteeing 100% data accuracy, even for complex entities. This integration enhances efficiency and accelerates verification closure. 

Experience seamless integration & eliminate data silos with OIM

Schedule a 30-minute live demo with our integration experts

Request a Demo

Video Transcript

Here’s the refined and joined version of the text, incorporating the specified changes:

Enterprises face challenges during complex verification processes, such as achieving easy access to information, real-time visibility, risk compliance, and better collaboration between teams. Information silos lead to poor visibility and disconnect between product management, quality assurance, and verification teams, which impacts productivity, resulting in poor-quality products and delayed delivery.

Integrating Cadence vManager with IBM DOORS Next Generation (IBM DOORS NG) using OpsHub Integration Manager (OIM) breaks these silos, enhances transparency, and enables cross-system traceability, improved communication between teams, and data-driven risk evaluation and validation. OIM integrates Cadence vManager and IBM DOORS NG bidirectionally, preserving all historical and current data in real-time for each user in their preferred system.

Let’s take a look at the demo. The product team starts by adding a feature requirement in IBM DOORS NG, used by the DRAM team, gives it a content name, and saves it. They then add a description under the same feature requirement and save it. The systems architect reviews the feature requirement and adds verification requirements under it.

Under the first verification requirement, the systems architect adds a content name and saves it. These verifications are tasks for the verification team to perform. The systems architect then adds a second verification requirement, assigns it a content name, and saves it.

In IBM DOORS NG, we now have a feature requirement linked to two verification requirements. Navigating to vManager, the verification team resyncs to view the latest requirements. In vManager, all three requirements added in IBM DOORS NG are visible. The verification team proceeds to add two test cases, one under each verification requirement.

The verification team in vManager begins working on both verification requirements by adding planned test cases back in IBM DOORS NG. The product team refreshes the page to view the recently added planned tests, which are linked to their respective verification requirements.

The product team reviews the test cases and updates one of the verification requirements by modifying its description, changing the status to “Under Review,” and saving the changes. Back in vManager, the verification team resyncs to view the updates made in IBM DOORS NG. They examine the newly added details and status and add another test case, which syncs back to IBM DOORS NG.

The product team refreshes IBM DOORS NG to view the new test case, verifies it, and upon completion, changes the status of the requirements to “Approved,” signaling the verification team to start testing.

This completes phase 1 of the demo, demonstrating effective collaboration between the product team, systems architect, and verification team on requirement definition. Real-time updates reduce the risks associated with test cases based on outdated requirement definitions.

In phase 2, we will showcase similar collaboration during the testing phase to obtain verification results. The systems architect and product team, working in IBM DOORS NG for DRAM in this demo, can view the results and ensure compliance.

Switching to vManager, the verification team starts executing tests and attaching results to all tests. Before proceeding, they map regression sessions to the planned tests. Once mapped, they click on “Grade Analysis,” a feature provided as part of OpsHub vManager Sync solution.

After completing grade analysis, the verification team resyncs to get the results, where they can view coverage and test data. Back in IBM DOORS NG, the product team refreshes the page to see the updated test results, verifies them, and finds them as expected. With no further action required, the product team concludes their part.

We saw how integrating vManager with other tools enables seamless collaboration, ensuring all teams work within their preferred tools while accessing the latest requirements and results.

This concludes the demo. Thanks for watching. Integrating Cadence vManager with other tools using OIM improves organizational productivity by minimizing manual intervention and reducing errors.

Experience seamless integration & eliminate data silos with OIM

Schedule a 30-minute live demo with our integration experts

Request a Demo

Verisium Manager Integration with Leading ALM & Requirements Management Tools

Verisium Manager Integration with Leading ALM & Requirements Management Tools

Product development in the semi-conductor landscape has grown complex with changing customer requirements. As a result, manual methods no longer match the pace of innovation and managing risks becomes challenging.  An automated integration can facilitate traceability and collaboration transparency across the hardware toolchain, ensuring data compliance. This video demonstrates how automated bi-directional integration of quality & verification tool, Verisium Manager  (Formerly known as vManager) with the ALM and requirements management tools (Jira and IBM DOORS NG) using OpsHub Integration Manager (OIM) empowers the verification and requirements management teams with richer traceability, transparency, and regulatory compliance leading to better product delivery and driving innovation at scale.

Experience seamless integration & eliminate data silos with OIM

Schedule a 30-minute live demo with our integration experts

Request a Demo

Video Transcript

The demo begins by adding requirements in both tools, .e., Jira and Verisium Manager (Formerly known as vManager). First, Jira, used by the USB Flash Drives team, is where a feature requirement is added. Basic details like the summary and description are provided, and then the requirement is saved. The System Architect creates a couple of verification requirements under the same feature requirement. Additional details are added, linking the verification requirements to the feature requirement. After saving, another verification requirement is added, linked, and saved.

OpsHub runs in the background, checking for created or updated requirements and integrating them into Verisium Manager. While this happens, requirements are also added in DOORS NG and G2. These tools are used by the DRAM team, where a feature requirement is added with a description and saved. The DRAM system architect reviews the feature requirement and adds verification requirements under it. The requirements are saved, and another verification requirement is added.

In DOORS NG, a feature requirement needs to be verified under two verification requirements. In Jira, refreshing the view reveals the USB 26 feature requirement, which is also linked to two verification requirements. Switching to Verisium Manager, two V plans are created: one for the DRAM team, integrated with DOORS NG, and another for the USB Flash Drives team, integrated with Jira. The USB V plan is checked for requirements from Jira, with a resync performed to capture the latest data. All three created requirements—the feature requirement and two verification requirements—are displayed.

In the DRAM V plan, a resync is performed, ensuring the same three requirements appear in the correct hierarchy, as seen in Jira and DOORS NG. The verification team proceeds to add test cases under each verification requirement. For the USB V plan, two test cases are added—one for each verification requirement.

The verification team begins working on both V plans and adds planned test cases. For the DRAM team, the requirements team needs visibility into the actual planned test cases. Therefore, test cases are integrated back into DOORS NG. The USB team does not need visibility into planned tests, so in their case, only final results at the requirements level are integrated.

In Jira, refreshing the page shows no changes, as test cases are not integrated there. However, in DOORS NG, the refreshing page displays the planned tests linked to their respective verification requirements. The DOORS NG team reviews the test cases, adds additional details to one of the verification requirements, and changes the status to “under review.” These changes are reflected in Verisium Manager after a refresh. The verification team sees the updates and adjusts the status, accordingly, adding another planned test.

The new test case is sent back to DOORS NG. After a refresh, the test case appears. The DRAM team verifies the test and marks the requirement as approved. At this point, the signaling verification requirement indicates that testing can begin.

This concludes phase one of the demo, where the product, system architect, and verification teams effectively collaborated on defining requirements, ensuring everyone stayed updated and reducing the risk of writing test cases based on outdated requirements. In phase two, similar collaboration occurs during the testing phase. The system architect and product teams in DOORS NG and Jira will review the results to ensure all compliance is met.

Moving back to Verisium Manager, the team begins executing tests and attaching test results. For the USB V plan, regression sessions are mapped to the tests. Grade analysis is then performed, persisting the verification results so they can be sent back to Jira and DOORS NG.

Once grade analysis is complete, the results are resynced to capture the latest data. The test coverage and data are now available. A similar process is followed for DRAM, with sessions mapped to the planned test cases and grade analysis performed. This analysis is done using a Tickle script provided as part of the OpsHub Verisium Manager sync solution.

Now that test results are available in Verisium Manager, Jira is refreshed. The USB team sees that the test results are below the acceptable percentage—one of the verification requirements is only 33% covered. Consequently, the status is changed to “Requires Re-verification.”

This change is reflected in Verisium Manager, signaling the verification team to add more tests. Meanwhile, the updated results are checked in DOORS NG. After refreshing the page, the results are displayed in DOORS NG. The team verifies the coverage and finds the results as expected, so no further action is needed.

Back in Verisium Manager, the USB requirements are marked as “Requires Re-verification,” signaling that the results were not as expected. Additional tests are added to the regression suite, and the recent results are attached. A rerun of grade analysis is done, and the results are resynced. Now, the coverage is 100%. These updated results are sent back to Jira.

In Jira, after refreshing the page, the latest results are synced. All tests show 100% coverage, with no failed runs. The status is then changed to “Closed” or “Done,” marking the completion of the cycle. This action signals the verification team that all necessary testing for the requirements is complete.

Verisium Manager is checked again, and the updated status shows that all requirements are marked as “Done”. This completes the demo, demonstrating how integrating Verisium Manager with other tools allows teams to collaborate seamlessly, focusing on their areas of responsibility without needing to coordinate manually across different tools.

Throughout this demo, the verification team worked in Verisium Manager, while the requirements and system architect teams worked in DOORS NG and Jira, ensuring that everyone was viewing the latest version of the requirements and results. This concludes the sync demo.

Experience seamless integration & eliminate data silos with OIM

Schedule a 30-minute live demo with our integration experts

Request a Demo

Verisium Manager – Jira Integration

Verisium Manager - Jira Integration

Verification engineers need visibility into requirements with full context. They also need updates on the tests associated with each requirement and the Grade Attributes. Similarly, Jira teams need to take informed business decisions based on verification outcomes in Verisium manager (Formerly known as Cadence vManager). Collaborating manually for verification engineers, testers, and product owners leads to information gaps and avoidable delays. In addition, manual processes to map verification requirements are neither agile nor scalable. As a result, it impacts productivity, resulting in quality issues, delivery delays, and compliance risks. The answer lies in the automated synchronization of data between Jira and Verisium manager. Cross-functional insights and real-time data with full context result in a robust and transparent verification process. Verisium Manager integration with Jira enables traceability and comprehensive functional verification by minimizing manual intervention and errors. Watch the demo video to learn how OpsHub Integration Manager (OIM) integrates vManager and Jira bidirectionally, improving collaboration between teams and ensuring all current data is available to both users with full context, in their preferred system, in real-time. By leveraging this integration, users can eliminate subjectivity associated with complex and diverse sets of verification, requirements, and defects data.

Experience seamless integration & eliminate data silos with OIM

Schedule a 30-minute live demo with our integration experts

Request a Demo

Video Transcript

Teams using best-of-breed tools need visibility and access to cross-functional data within their own tools without relying on manual and tedious data transfers. When product managers, verification engineers, and QA teams collaborate effectively by automating data synchronization, it empowers them to enhance quality and product delivery. The integration of Verisium Manager (Formerly known as Cadence vManager) with Jira using OpsHub Integration Manager (OIM) breaks information silos between teams and enables comprehensive functional verification with enhanced traceability and planning, thereby minimizing manual intervention and errors.

OIM integrates Verisium Manager and Jira bidirectionally, preserving all historical and current data for each user in their preferred system in real time. The product team starts by adding requirements in Jira, which is being used by the USB Flash Drives team. The product team, or in this case, the USB team, adds a feature requirement, provides a summary and description, and saves it. The systems architect then creates a couple of verification requirements under the same feature requirement. Under the first verification requirement, the systems architect adds a summary, description, links it to the feature requirement, and saves it. These are the verifications that the systems architect wants the verification team to perform. The systems architect goes ahead and adds the second verification requirement, gives it a name and description, similarly links it to the feature requirement, and saves it.

OpsHub Integration Manager runs in the background, checking for created or updated requirements and integrating them into Verisium Manager. In Jira, the feature requirement is linked to both verification requirements. Switching to Verisium Manager, the verification team resyncs to view the latest requirements. In Verisium Manager, the feature requirement shows the actual requirement to be completed along with both verification requirements. The verification team then adds two test cases, one under each verification requirement, and begins working on both by adding planned test cases.

The USB team’s requirement is to avoid visibility until the planned tests are complete. Therefore, this demo will show integrations of the final results at the requirements level, although it is also possible to integrate planned tests from Verisium Manager to Jira if required. The verification team starts executing tests and attaches test results to all the tests. Before proceeding, they map some regression sessions to these tests. Once the sessions are mapped with the planned tests, the team clicks on Grade Analysis, which persists the verification results in the planned tests so they can be synchronized back to Jira. After completing the grade analysis, the verification team resyncs to get the results.

In Jira, all the coverage and test data are visible. The USB team refreshes the page to find the test results. They discover that one verification requirement reflects only 33% coverage, while the overall feature requirement reflects 66%. Consequently, the USB team changes the status to “Requires Reverification.” This status change syncs back to Verisium Manager, alerting the verification team that additional tests need to be added. In Verisium Manager, the status of the parent requirement reflects “Requires Reverification,” prompting the verification team to add more tests in regression and attach the recent results. The team runs grade analysis again and resyncs to view the latest results.

Now, 100% coverage is achieved. These updated results sync back to Jira. The USB team refreshes the page to view the updated results, reflecting 100% coverage with zero failed runs and all past runs included. The USB team changes the status of the feature and verification requirements to “Done,” marking the closure of the process. This status change syncs back to Verisium Manager, alerting the verification team that all work and required testing are completed for these requirements. Finally, in Verisium Manager, the verification team resyncs to view the updated status, confirming that the requirements are successfully marked as “Done.”

This demo showcased how integrating Verisium Manager with other tools allows teams to collaborate seamlessly within their own environments, ensuring everyone has access to the latest requirements and results. This completes the demo. Thanks for watching. Integrating Verisium Manager with other tools using OIM enables transparent and robust verification, helping teams gain cross-system visibility and insights.

Experience seamless integration & eliminate data silos with OIM

Schedule a 30-minute live demo with our integration experts

Request a Demo

TeamForge – IBM DOORS NG Integration

TeamForge - IBM DOORS NG Integration

In the ALM ecosystem, the choice of systems and collaboration between cross-functional teams is extremely crucial to delivering quality products on time without impacting productivity. By integrating TeamForge with other tools in the software lifecycle, teams can build an integrated pipeline from planning through deployment to deliver high-quality products to customers faster. Watch this video to learn how integrating TeamForge with IBM DOORS Next Generation using OpsHub Integration Manager (OIM) ensures clear visibility, transparency, and powerful teamwork with end-to-end insights. The OIM synchronization brings teams working in their respective tools on the same page with a single source of truth without having them move from one system to another.

Experience seamless integration & eliminate data silos with OIM

Schedule a 30-minute live demo with our integration experts

Request a Demo

Video Transcript

TeamForge is an ALM platform for traditional and hybrid software development, delivery, and collaboration. TeamForge reduces IT support costs and drives standardization and IP reuse. By integrating TeamForge with other tools in the software life cycle, teams can build an integrated pipeline from planning through deployment to deliver high-quality products to customers at a faster pace. OpsHub Integration Manager (OIM) supports the integration of TeamForge with 60+ ALM, DevOps, ITSM, and CRM systems.

In this video, we will showcase how OpsHub facilitates the integration of TeamForge with IBM DOORS Next Generation (IBM DOORS NG). The product manager in BM DOORS NG creates a new strategic theme, gives it a content description name, and saves it. The product manager then adds a file as an artifact and saves it. Once the artifact is attached, the product manager saves the strategic theme.

The developer in TeamForge refreshes the page to view the strategic theme created in IBM DOORS NG, which reflects here as an Epic. The developer clicks on the Epic and goes to attachments to view the Artifact added in DOORS NG. The developer then adds a comment and saves it. Both the Remote Entity ID and Remote Entity link are available in TeamForge. After synchronization, you can acquire information on the DOORS NG ticket ID and link to access it here.

In DOORS NG, the Product manager refreshes the page to view the comment added in TeamForge and replies to the developer in TeamForge with another comment. The Product manager in IBM DOORS NG then changes the status of the strategic theme from Draft to Under Review. Both the comment and the status change sync back to TeamForge upon saving it. In TeamForge, the comment and status change are successfully reflected.

The developer in TeamForge creates two user stories as children associated with the epic. The developer creates the first child, gives it a title and description, and saves it. The developer then adds the second child, gives it a name and description, and saves it back in DOORS NG. The product manager refreshes the page to view both synchronized user stories added as children.

The product manager clicks on the first user story artifact in DOORS NG, adds a subject line and comment, and saves it. They then change the status of the artifact from Draft to Under Review. Back in TeamForge, the developer clicks on the first child user requirement to view the added comment and updated status. The developer then adds a comment under the same child user requirement indicating the completion of the user story and changes the status to “Approved” in DOORS NG.

The comment added in TeamForge is successfully reflected in DOORS NG along with the updated status. The developer clicks on the second child user requirement, similarly, adds a comment indicating the completion of the user story, and updates the status to “Approved”. Back in DOORS NG, under the second child, the product manager views the comment added in TeamForge along with the updated status.

In TeamForge, the developer navigates back to the epic and changes the status to “Approved”, which synchronizes back to IBM DOORS NG. Finally, in IBM DOORS NG, the product manager refreshes the page to view the updated status of the strategic theme as “Approved”.

This completes the demo. Thanks for watching.

Experience seamless integration & eliminate data silos with OIM

Schedule a 30-minute live demo with our integration experts

Request a Demo

Verisium Manager Integrations Using OpsHub Integration Manager (OIM)

Verisium Manager Integrations Using OpsHub Integration Manager (OIM)

It is critical for chip design companies to manage processes alongside customer demands, quality, innovation, and speedy delivery. Swift verification closure helps them meet these challenges leading to faster regression testing, speedier tape out, and accelerated SoC. Verisium Manager  (Formerly known as vManager), a robust verification and management solution, optimizes verification and improves productivity for organizations eliminating time-consuming data organization tasks. OpsHub Integration Manager (OIM) enables the synchronization of Verisium Manager with requirements tools, quality assurance tools, and other cross-functional tools used by project managers and QA teams. This facilitates seamless synchronization of defects and requirements data without losing cross-system traceability, transparency, or access to information. Watch this video to learn more about Verisium Manager and its integrations using OpsHub Integration Manager.

Experience seamless integration & eliminate data silos with OIM

Schedule a 30-minute live demo with our integration experts

Request a Demo

Video Transcript

Chip design companies around the globe hustle every day to manage processes alongside customer demands, quality, new technology, and speedy delivery. It becomes critical to ensure that operating models and projects meet the challenges of new technologies in the interconnected world.

What separates the innovators from the rest is their ability to get verification closure quickly, resulting in faster regression testing, speedier tape-out, and accelerated SoC. Cadence, a leader in electronic design, caters to the world’s most innovative companies, delivering products from chips to boards to systems for dynamic market applications, including consumer hyperscale computing, 5G communication, automotive, aerospace, industrial, and health.

When, despite the availability of resources, tools, and methodologies, organizations have to execute critical projects with inadequate details, what they need is a system to manage verification accurately across an array of global projects. Verisium Manager (Formerly known as vManager) Verification Management’s powerful, scalable, and automated verification planning and management solution supports multi-user, multi-engine, multi-project, and multi-series simultaneously. It provides the data needed to optimize verification.

vManager automates verification processes at the block, chip, system, and project levels. Its easy-to-adopt regression management and failure triage features improve productivity, eliminating time-consuming and tedious data organization tasks. Along with feedback about verification completeness, it enables data-driven schedule and resource decisions.

vManager’s connection with OpsHub Integration Manager enables it to synchronize defects and requirements data with systems like JIRA, JAMA, and DOORS. This synchronization eliminates the subjectivity associated with complex and diverse sets of verification requirements and defect data. OpsHub Integration Manager ensures transparent and robust verification with easy access to information, data-driven evaluation and validation, cross-system traceability and visibility, proactive management of requirements, compliance with real-time data, and improved collaboration between teams to avoid quality issues, delivery delays, and financial loss.

Verisium Manager provides multi-engine verification for many semiconductor companies worldwide. It caters to a unified user interface for verification engineers, designers, and managers. Cadence Computational Software for intelligent software design.

Experience seamless integration & eliminate data silos with OIM

Schedule a 30-minute live demo with our integration experts

Request a Demo

PTC Codebeamer and Verisium Manager Integration

PTC Codebeamer and Verisium Manager Integration

Integrating PTC Codebeamer, an Application Lifecycle Management (ALM) tool, with Verisium Manager (formerly known as vManager), a verification management tool establishes clear requirement-verification traceability throughout the development lifecycle. This integration enables engineers to ensure that all requirements are thoroughly tested, while product owners can easily monitor the verification status of these requirements, identify potential issues, and make informed decisions.
By integrating PTC Codebeamer and Verisium Manager using OpsHub Integration Manager (OIM), a robust digital thread is implemented, enabling seamless connectivity across the development lifecycle. OpsHub facilitates the integration of over 60 diverse tools, including support for custom or home-grown connectors, helping you establish robust digital continuity by leveraging the full potential of best-of-breed tools. In this video, watch how real-time, automated two-way synchronization enables robust verification with enhanced traceability and planning resulting in faster time to market and increased customer satisfaction.

Experience seamless integration & eliminate data silos with OIM

Schedule a 30-minute live demo with our integration experts

Request a Demo

Video Transcript

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.

Experience seamless integration & eliminate data silos with OIM

Schedule a 30-minute live demo with our integration experts

Request a Demo

PTC Codebeamer Integration Using OpsHub

PTC Codebeamer Integration Using OpsHub

Information silos create significant challenges in building a seamless digital thread. When data is isolated within different systems and departments, it becomes difficult to establish traceability in the product lifecycle and access the end performance. The lack of digital continuity and inconsistent data, compromises decision-making and hinders identifying potential issues early in the development cycle.
Best-of-breed Application Lifecycle Management (ALM) tools like PTC Codebeamer can effectively break down silos and foster a seamless digital thread. By providing a unified platform for managing requirements, Codebeamer enables teams across the product lifecycle to access and share information seamlessly. PTC Codebeamer integrations with OpsHub guarantee 100% reliable and accurate data synchronization without any manual intervention. It allows you to effortlessly scale to accommodate growing business needs and expand teams and projects over time.

Experience seamless integration & eliminate data silos with OIM

Schedule a 30-minute live demo with our integration experts

Request a Demo

Video Transcript

Digital transformation, caused by emerging digital technologies and business models, is a reality across sectors. To function seamlessly, what enterprises need today is enhanced teamwork with end-to-end visibility across the tool chain.

PTC’s Codebeamer is an agile Application Lifecycle Management (ALM) solution for distributed software development, empowering teams across industries. Codebeamer is a complete lifecycle management solution with requirements management, software development, risk management, variance management, DevOps, and QA testing capabilities.

The Codebeamer support in OpsHub Integration Manager (OIM), OpsHub’s flagship product, enables users to integrate Inclan Codebeamer with 60+ best-of-breed systems.

The bidirectional synchronization of entities from Codebeamer with the use of OIM enhances traceability, transparency, and strong collaboration between cross-functional teams, resulting in better quality products and faster delivery cycles.

OpsHub provides rich integration support for Codebeamer platform using OIM, which enables more agility and enhanced visibility in the product delivery ecosystem.

This leads to an improved flow of information and eliminates duplication of work, resulting in enhanced productivity, efficiency, and time-to-value by leveraging Codebeamer integrations using OpsHub Integration Manager.

Experience seamless integration & eliminate data silos with OIM

Schedule a 30-minute live demo with our integration experts

Request a Demo