The connector of Kovair Omnibus for LDRA Testbed will enable developers to easily apply LDRA’s static code analysis capabilities from within their IDEs. Kovair Omnibus is also integrating with the unit testing and test case generation capabilities of LDRA. Kovair Omnibus, with its existing integrations with Continuous Integration -CI tools such as Jenkins, Hudson, etc., also helps organizations setup an automated CI environment. Having this type of CI environment will enable constant monitoring of stability and functionality, providing more granular measurement at all stages of development. This will provide confidence to the organizations for all software development projects in safety-critical, security-critical, and business-critical applications.
- Synchronization support for all major LDRA analysis types such as Static Analysis, Instrumentation Analysis, Dynamic Analysis
- Direct access to LDRA tests from within ClearCase by Kovair ClearCase plug-in for LDRA
- Visibility of LDRA file, execution, execution results from 3rd party tools like DOORS
- Direct view of ClearCase File information and changesets from Kovair as an ALM repository
- Support for Omnibus dialog box where engineers can link the defects / requirements based on which they have developed and checked in the code
- Allows LDRA users to achieve continuous integration from a single interface
- Enforces code quality compliance
- Establishes complete traceability between code files, change sets, results, requirements and defects
- Enables organizations to streamline their development processes around LDRA and associated tools and follow industry standards
- No need to rip and replace any existing tools that development teams use
- Allows developers to automate defect tracking and removal process for each LDRA failed code
- Enables project managers to evaluate the ratio between lines of codes written and defects generated, thus measuring developers’ performance
The integration of LDRA tools with Kovair Omnibus platform fuels the development of Safety Critical Software and maximizes the value of LDRA tool investment. Together with Kovair Application and Omnibus integration technology, LDRA provides a Continuous Integration (CI) platform to its users that automates and manages the build process for large-scale, system-level software projects.
With this integration in place, organizations can enforce LDRA compliance test as a mandatory step for their development teams operating in a multi-tool environment, and thus ensures that development errors are identified early in the lifecycle and resolved at the source code level itself, even before they are checked-in into source control repository and the build process continues.
Kovair Omnibus applies a unique mechanism that restricts developers to check-in their codes into an SCM tool without running them through LDRA analysis tests. Only if the results of the analyses turn out ‘Pass’, codes can be checked in successfully followed by automatic build and testing – the way to achieve Continuous Integration.
Kovair facilitates this integration solution with the help of Kovair LDRA Integration Adapter/ Connector and Kovair ClearCase Plug-in for LDRA. The adapter provides bi-directional synchronization between LDRA Testbed and Kovair Omnibus, thus resulting in data flow to and fro from other development tools via Omnibus. The ClearCase Plug-in for LDRA installed locally in developer’s system pulls in code files from ClearCase during code check-in and then pushes them to LDRA tool via Kovair LDRA integration adapter.
Once the LDRA tests are done, users can view the execution results from the plug-in itself. As the associated data flows to Kovair Omnibus centralized repository, it provides a vivid picture of the execution. The overall status can also be pushed to other desired tools like DOORS.
One can manage the entire development process starting from importing requirements from a requirement management tool to developing code in an IDE, analyzing coding standards in LDRA, code check-in into an SCM tool to managing builds and deployment in an integrated tool setup.
In real life scenario, it is often seen that developers due to many unavoidable circumstances end up checking in erroneous codes into an SCM tool that do not adhere to the quality standards defined at project level. The results are obvious defects that are identified later when the build fails during automated testing. Avoiding code errors early in the development stage causes rework, incremental issues, and delivery delays.
It is also important that developers are able to perform all their development steps including LDRA analysis from within their preferred tool environment and there is no communication barrier between the participating tools, since automating development progress is the ultimate objective.
In a common development setup, Business Analyst manages Requirements in any Requirement management tool like IBM DOORS; Developer writes code in IDE like IBM RTRT and check-ins codes in SCM tool like IBM ClearCase; analyzes Source Code quality in LDRA Testbed; tracks Defects in a defect management tool like Atlassian JIRA and manages Builds in Jenkins. All these best-of-breed tools for different development functions are not connected to each other resulting in frequent manual interventions to complete the build process, starting from requirements analysis, code check-in to code analysis, repair of erroneous codes to successful build.