Bipin Shah, CEO and Chairman, Kovair Software speaks on “Deploying Kovair Integrated ALM for Test Automation and DevOps” during the conference program at STeP-IN SUMMIT 2014 at Bangalore on June 26.
Bipin Shah, CEO and Chairman, Kovair Software speaks on “Deploying Kovair Integrated ALM for Test Automation and DevOps” during the conference program at STeP-IN SUMMIT 2014 at Bangalore on June 26.
This presentation briefly describes the fundamentals of Application Lifecycle management (ALM), its organizational use and the benefits of Enterprise Service Bus (ESB) based ALM integration model. One can also learn more about ALM/ SDLC steps in detail and the ways to perform them collaboratively, that helps achieve operational efficiency and ensures faster delivery of better software product.
Kovair Omnibus allows enterprise application integration and synchronization through its Omnibus Integration Platform. Integrate and synchronize standard multi-vendor ALM tools using Kovair adapters, plug-ins and build your own integrated ALM platform.
Collection of the fundamental decisions about a software product / solution designed to meet the project’s goals and quality attributions. Learn the basic components of SOA and understand how an organization can implement the same.
Kovair ALM is the web-based, feature-rich and highly configurable ALM platform that enables geographically diverse teams perform all steps of SDLC (Requirements Management, Test Management to Release Management and the processes in between) and beyond with work flow automation for all ALM functions.
This PPT presentation takes you through the challenges of software development and its consequences, problems of disjoint reporting and the benefits of cross tool and cross functional reporting in an integrated tool environment. To view sample reports and metrics, visit www.kovair.com and schedule a live demonstration with Kovair engineers.
Going back to the year 2014, Kovair touched upon several milestones in different arenas starting from Product Enhancements to Enhanced Website Launch to Event Participations and Partnerships. We would like to hear your feedback on how we can help you serve better in the years to come.
In this presentation, you will learn the power of Application Lifecycle Management in an integrated environment and how Kovair orchestrates the four major pillars of ALM – Collaboration, Process, Tracking, and Quality Control.
Perforce is a popular scalable Version Control system/ Software Configuration Management (SCM) tool used in development lifecycle for securely maintaining frequent changes to the code files, provide audit trails to changes, support parallel development and code reuse. Developers use Perforce to maintain current and historical versions of files, such as code files, web pages, and documents. Perforce maintains a centralized repository for files and allows access to the repository across networks, thereby fostering collaboration and speeding up project progress.
But for the changes and updates committed to the files in Perforce repository, distributed team of developers, QA/testers, support using different tools needs to be automatically updated with the information about the changes done. Kovair Perforce Integration Adapter connects Perforce with IDEs and tools from other domains, such as Requirement Management, Test Management, Change Management, and Defect Management for automatic exchange of information.
Kovair Perforce Integration Adapter’ exposes Perforce artifacts File, ChangeList, File Version, Job, and Label (as traceable items) in the integrated ALM scenario.
Kovair provides a vendor-neutral ALM platform called Kovair Omnibus Integration Platform to which you can connect your Perforce instance using Kovair Perforce Integration Adapter. This integration makes information about Perforce files and changesets accessible from any tool connected to Kovair Omnibus Integration Platform. Perforce changesets can be linked to any Requirement or Defect item in any integrated tool like DOORS or JIRA to establish traceability. Perforce Files are not duplicated in the integrated tools; instead, file information (Metadata) is made available to the other tools. File content/difference can also be made available on demand through a federated architecture to certain ALM tools and Kovair plug-ins for IDEs like Eclipse and Visual Studio.
The adapter component is Kovair Perforce Adapter which is a web service.
Kovair Omnibus currently supports Perforce Version 2008.2, 2010.2, 2013, 2014.1.
Fig: Kovair Perforce Integration
Throughout the lifecycle of an application, the source code files keep changing; existing files are modified, new files are created, and old files are deleted. As a result, keeping track of every change and preventing one user from accidentally overwriting the changes made by another becomes a necessity. Perforce has the built-in source code control capability to allow multiple developers to work on the same project/ project files at the same time. When Perforce is integrated into the ALM eco-system by means of Kovair Perforce Integration Adapter, Perforce events like changeset creation are propagated to other tools providing visibility to the specific files and file versions that are being worked upon for a particular requirement, change request or defect. As a result, different stakeholders can get visibility into Perforce changes without having to navigate away from their preferred tool environment.
Implementing change requests and fixing defects always require addition of code files or modifications in existing code files that are stored in source code control tools, such as Perforce. Each such addition or modification generates a changeset with certain details on the nature of changes. By virtue of Perforce integration using the Kovair Perforce Integration Adapter, you can get access to the changeset information and associate the changesets to the corresponding change request or defect in another tool.
Version control implies keeping track of which changes were made, who made them, when they were made, and why. Also, it involves grouping versioned files for a release, maintaining multiple releases that are still being widely used and merging files from different releases. Therefore, it is imperative to keep multiple versions of the source code and other necessary files well within the reach of the developers. Perforce integration addresses this requirement and allows developers to access information about specific versions of code files from their development tools.
In order to ensure that the final product is in accordance with the requirements specified by the customers during the inception of a project, it is vital to bring in traceability at every stage of the application development life cycle. By integrating Perforce with other tools in the ALM system, you can ensure that all the changes in any of the files can be traced to its originating cause – be it a fix for a defect or a change request implementation.
As shown in the figure above, you can integrate Perforce with Kovair, Eclipse/ Visual Studio IDE and Hudson/ Jenkins so that as developers check in code files from their respective IDE(s) to Perforce SCM tool repository, Kovair through automated workflow triggers build for those files in build tool like Hudson or Jenkins. Changesets corresponding to the source code files in Perforce are replicated in Kovair and linked with the corresponding requirements, change requests or defects to achieve traceability.
Mathwork’s Simulink is a visual modeling tool used to create design architecture for various project requirements in a model driven development environment. Kovair Omnibus allows users to link Simulink models with Requirements from Kovair or Kovair connected popular Requirement management tools like IBM DOORS Next Gen. The integration provides cross-tool traceability facilitating easy identification of design impact for the change in Requirements.
Kovair Omnibus Simulink adapter allows users to link Simulink design specifications and requirements from Kovair directly to their implementation in MATLAB Simulink. Simulink Users can add, link, or browse linked requirements from within the Kovair Simulink Connector. Kovair exposes a menu in Mathworks Simulink that acts as a plug-in.
Kovair Omnibus Connector for Simulink allows bi-directional traceability between Simulink models and Kovair Omnibus Requirements Work Items. You can navigate from Simulink model elements to its associated Kovair ALM Requirements Work Item and vice versa.
For MATLAB users, it will be of great value to link model elements and subsystems in diagrams to the external requirements management system. Kovair Omnibus leverages this capability to enable linking of MATLAB model components to requirements managed in Kovair ALM. This has significant advantages for MATLAB users who design components in companies and industries with stringent compliance mandates.
The components of the adapter are:
Kovair Omnibus currently supports integration with Simulink on Matlab R2014b.
Enhanced Collaboration –Kovair’s integration with Simulink helps both developers and designers to stay connected to a single source of information thereby removing silos. When integrated with Omnibus, all stakeholders in ALM scenario can view changes in speciation from within their preferred IDEs, work on them immediately.
Absolute Traceability – The integration provides flexibility to create many-to-many links between Simulink Models and Kovair Requirement Items. One can create a link from multiple Simulink model elements to the same Requirement Item or link multiple Requirement Items to a single Simulink model element. The traceability information is stored both within the Simulink model and Kovair Requirements, enabling access from both the design and the requirements management environment.
This bi-directionality along with versioning and audit trails help facilitate collaborative design and requirements reviews in Model-Based Design workflows. For example, one can track the impact of changed/deleted requirements on your design.
Users can also link Kovair Omnibus Connected SCM repositories (Subversion, IBM ClearCase) to Simulink models and have traceability between models, requirements, and code.
Management Reporting – Using Kovair’s traceability matrix, managers can view published design items from Simulink and related requirements from Kovair, or other requirements management tools to do change impact analysis and conduct reviews. Once integrated with Kovair, Simulink models and blocks are automatically exported into Kovair native environment, including Simulink model preview.
All these visual representations of reports can be accessed remotely from Kovair’s centralized platform, which aids in risk management, process improvement, and project management.
Fig: Kovair and Simulink integration
This is a major release from Kovair for its two major product lines ‘ALM ‘ & ‘Omnibus Integration Platform‘. The users of previous release 8.0 are encouraged to evaluate and upgrade to the new release for a better Kovair experience.
The Kovair 8.6 has been designed with an approach to improve its UI as well as to introduce a series of new features and functionalities to both of its product lines. The UI advancements make the application more user-friendly and the newly introduced features give users more control and flexibility in operation.