Skip to main content
RapiTest - Functional testing for critical software
RapiCover - Low-overhead coverage analysis for critical software
RapiTime - In-depth execution time analysis for critical software
RapiTask - RTOS scheduling visualization
RVS Qualification Kits - Tool qualification for DO-178 B/C and ISO 26262 projects
RapiCouplingPreview - DCCC analysis
MACH178 - Multicore Avionics Certification for High-integrity DO-178C projects
MACH178 Foundations - Lay the groundwork for A(M)C 20-193 compliance
RapiDaemons - Analyze interference in multicore systems
RTBx - The ultimate data logging solution
Sim68020 - Simulation for the Motorola 68020 microprocessor
Data Coupling & Control Coupling
Training
Consultancy
Tool Integration
Support
RVS 3.23 Launched
Rapita System Announces New Distribution Partnership with COONTEC
Rapita partners with Asterios Technologies to deliver solutions in multicore certification
SAIF Autonomy to use RVS to verify their groundbreaking AI platform
RVS gets a new timing analysis engine
How to measure stack usage through stack painting with RapiTest
What does AMACC Rev B mean for multicore certification?
How emulation can reduce avionics verification costs: Sim68020
How to achieve multicore DO-178C certification with Rapita Systems
How to achieve DO-178C certification with Rapita Systems
Certifying Unmanned Aircraft Systems
DO-278A Guidance: Introduction to RTCA DO-278 approval
8th Annual Military Aviation & Air Dominance Summit
Avionics Certification Q&A: CERT TALK (with Consunova and Visure)
How emulation can reduce avionics verification costs: Sim68020
One of the unique challenges of working in the aerospace domain is the need to maintain onboard software for the long lifetimes of many aircraft. For both civil and military aircraft, software must often remain in the field for decades, during which time maintenance and updates may be needed to meet ever increasing demands.
When such software is certified to DO-178 (DO-178A, B or DO-178C), MIL-HDBK (MIL-HDBK-516A, B or MIL-HDBKC) or related guidelines, this means verification environments must also be available for long periods of time.
Multicore timing analysis: to instrument or not to instrument
When making timing measurements of software, there are generally two classes of approach:
