The LDRA tool suite has integrated with the IBM Rational Rose RealTime model-driven development environment. LDRA now includes code quality analysis and code coverage techniques for model-driven development (MDD) using Unified Modeling Language (UML). The LDRA tool suite supports the analysis, instrumentation, and testing of both auto-generated and user-created source code both from within the Rose RealTime user interface or the LDRA development environment. LDRA’s integration of the LDRA tool suite with the IBM Rational Rose RealTime has been written and tested using IBM Rational Rose RealTime v7.0. The integration leverages the makefile and source code structures generated under a UML component so that, while these structures remain unchanged, the integration is forward and backward compatible.
Rose RealTime helps developers create high-quality embedded applications by supporting MDD benefits such as abstraction, encapsulation and distribution. LDRA’s integration of Rose RealTime with the LDRA tool suite combines the strengths of both environments. The integration creates a complete solution which enables models to be checked against coding standards such as MISRA, to be analyzed for potential quality problems, and to be instrumented at the source code level so that model-driven tests deliver coverage metrics alongside test results.
LDRA produces code review, quality review, and coverage overview reports that attach to the UML component, ensuring that analysis and testing can be carried out from within the Rose RealTime development environment. Alternatively, the generated source code can be automatically loaded into the LDRA tool suite, allowing the full range of analysis techniques to be applied or unit testing to be executed.
Analysis by the LDRA tool suite can highlight implementation issues during design, allowing them to be fixed before they become a problem. When Rose RealTime capsules and classes are ready to be tested, the LDRA tool suite can instrument the associated source code, offering metrics on the effectiveness of the tests and identifying untested branches and unreachable code. If necessary, code can be transferred to the LDRA tool suite for unit testing to exercise routes through the code which otherwise remain untriggered.
More info: LDRA