Overview of Kovair Omnibus Integration Platform
17
Omnibus Integration Omnibus Integration Platform Platform Kovair Marketing [email protected] www.kovair.com August 2014 Kovair Software Copyright © 2000-2014
description
Kovair’s Omnibus Integration Platform works on ESB (Enterprise Service Bus) model and allows integration of vendor-specific and Open source tools by using Kovair integration adapters and plug-ins. Kovair has almost 50 out-of-the-box integrations with leading third-party ALM and IT tools and all of these integrations are available off the shelf.
Transcript of Overview of Kovair Omnibus Integration Platform
Omnibus Integration PlatformOmnibus Integration Platform
Kovair Marketing
www.kovair.com
August 2014
Kovair Software Copyright © 2000-2014
Presentation Content
• What does your development project need?• Problems faced by a developer in distributed environment• Solutions to these problems• Omnibus based Integrations• Kovair Omnibus Integration Platform - A complete solution to the
problems• Requirements to Release scenario with Omnibus• Currently available third-party and open source Integrations
What does your development project need?
Facing problems as a developer in todays global
environment ?-Using tools from different
vendors?
Significant manual handoff
No real time actionable metrics for corrective actions
No real time updates between tools
Login to different tools to understand the requirements
Prioritizing jobs based on mails and discussions
Dependent on QA team feedback on testing
Login to different tools for defects
Solutions to these problems
Kovair Omnibus Integration Platform-A complete solution to the problems
Requirements to Release scenario with Omnibus
• Requirements getting approved at DOORS.
• Using workflow in Kovair, task gets generated for development.
• Developer gets a notification that development needs to be done for a requirement.
• Tester gets notification for test case creation.
• Developer opens eclipse and views the approved requirements.
• Developer writes code against the requirements.
• On a parallel path tester opens HPQC and views the requirements of DOORS.
• Tester writes test cases at HPQC and completes the task.
Requirements to Release scenario with Omnibus
• On completion of this task, developer gets a notification and does the functional testing
• Once he completes testing, he checks in the code and completes the task from the IDE.
• On checking in of the code, a build gets triggered using Hudson.
• The tester gets notified as soon as the development completes and starts the testing using HPQC & Selenium
• Defects raised by the tester can be viewed by the developer in the IDE for fixing.
• This continues till all the bugs are fixed.
• Using this cross tool data managers can track the progress of the release along with the quality of the release.
• This completes the development and testing process..
Requirements to Release scenario with Omnibus
Currently available third-party and open source Integrations
Q & A
THANK YOU
For further queries please email us at :
[email protected]: www.kovair.com
Kovair Software Copyright © 2000-2014
