Rapita co-authored paper wins ERTS22 Best paper award
A look back on Rapita's Multicore DO-178C training in Huntsville
RVS 3.17 Launched
York Aerospace and Rocketry Society MACH-22 Update
There are how many sources of interference in a multicore system?
Supporting modern development methodologies for verification of safety-critical software
Flexible licensing software fit for modern working
DO-178C - Stage of Involvement 4
DO-178C Guidance: Introduction to RTCA DO-178 certification
MATLAB® Simulink® MCDC coverage and WCET analysis
Code coverage for Ada, C and C++
AMC 20-193
High Integrity Software Conference 2022
Webinar: Efficient DO-178C verification - Functional testing
Webinar: Efficient DO-178C verification - Code coverage
Aerospace Tech Week Americas
RVS tools store a copy of the code they analyze, which you can view in the RVS Project Manager.
Results such as coverage obtained from RapiCover or RapiCoverZero or your software's worst-case path (as calculated by RapiTime) are highlighted and color-coded to help you understand how your results map to specific areas of your code.
Within the code viewer, where they are available, you can view source code, preprocessed code, instrumented code and object code. If you're using a zero-footprint RVS tool such as RapiCover Zero and have access to source code and debug symbols, you can view your object code and source code side-by-side to support traceability of your results between the two.
Feature applies to:
