No-code integration platform for rich bi-directional sync
Zero downtime migration to tool of your choice
Keep Historical Data, Without Slowing Down Your Tools
Migrate or restructure Azure DevOps Instances
Real-time, context-rich data lake for AI or analytics
By Role
Accelerate delivery with clear insights
Transform smarter with a connected digital thread
Confident transitions for every enterprise change
By Initiative
Modernize and move to cloud without disruption
Build a compliant digital thread for complex environments
Build the foundation for smarter AI
By Domain
No-code integration across teams & systems
Enable collaboration between IT, support & business teams
Connect PLM & engineering teams for smarter products
Ensure regulatory compliance from start to release
Explore the latest in technology and best practices
Success stories from the field
Actionable insights for your business challenges.
See solutions in action
Learn, plan, and execute with confidence
Official announcements and updates
Join discussions that drive results
Stay ahead with curated insights
The defense industry is entering a pivotal phase with the introduction of DoDI 5000.97, mandating the shift to Digital Engineering (DE). This article examines the challenges, including tool interoperability and data governance, and how suppliers can adapt through Intelligent Federation and integration platforms like OpsHub.
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.
Schedule a 30-minute live demo with our integration experts
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.
Schedule a 30-minute live demo with our integration experts
