Your browser does not support JavaScript! Skip to main content
Free 30-day trial DO-178C Handbook RapiCoupling Preview DO-178C Multicore Training Multicore Resources
Rapita Systems
 

Industry leading verification tools & services

Rapita Verification Suite (RVS)

  RapiTest - Unit/system testing  RapiCover - Structural coverage analysis  RapiTime - Timing analysis (inc. WCET)  RapiTask - Scheduling visualization  RapiCoverZero - Zero footprint coverage analysis  RapiTimeZero - Zero footprint timing analysis  RapiTaskZero - Zero footprint scheduling analysis  RapiCouplingPreview - DCCC analysis

Multicore Verification

  MACH178  MACH178 Foundations  Multicore Timing Solution  RapiDaemons

Engineering Services

  V&V Services  Data Coupling & Control Coupling  Object code verification  Qualification  Training  Consultancy  Tool Integration  Support

Industries

  Civil Aviation (DO-178C)   Automotive (ISO 26262)   Military & Defense   Space

Other

RTBx Mx-Suite Software licensing Product life cycle policy RVS Assurance issue policy RVS development roadmap

Latest from Rapita HQ

Latest news

SAIF Autonomy to use RVS to verify their groundbreaking AI platform
RVS 3.22 Launched
Hybrid electric pioneers, Ascendance, join Rapita Systems Trailblazer Partnership Program
Magline joins Rapita Trailblazer Partnership Program to support DO-178 Certification
View News

Latest from the Rapita blog

How to certify multicore processors - what is everyone asking?
Data Coupling Basics in DO-178C
Control Coupling Basics in DO-178C
Components in Data Coupling and Control Coupling
View Blog

Latest discovery pages

control_tower DO-278A Guidance: Introduction to RTCA DO-278 approval
Picture of a car ISO 26262
DCCC Image Data Coupling & Control Coupling
Additional Coe verification thumb Verifying additional code for DO-178C
View Discovery pages

Upcoming events

Avionics and Testing Innovations 2025
2025-05-20
DASC 2025
2025-09-14
DO-178C Multicore In-person Training (Fort Worth, TX)
2025-10-01
DO-178C Multicore In-person Training (Toulouse)
2025-11-04
View Events

Technical resources for industry professionals

Latest White papers

Mitigation of interference in multicore processors for A(M)C 20-193
Sysgo WP
Developing DO-178C and ED-12C-certifiable multicore software
DO178C Handbook
Efficient Verification Through the DO-178C Life Cycle
View White papers

Latest Videos

Rapita Systems - Safety Through Quality
Simulation for the Motorola 68020 microprocessor with Sim68020
AI-driven Requirements Traceability for Faster Testing and Certification
Multicore software verification with RVS 3.22
View Videos

Latest Case studies

GMV case study front cover
GMV verify ISO26262 automotive software with RVS
Kappa: Verifying Airborne Video Systems for Air-to-Air Refueling using RVS
Supporting DanLaw with unit testing and code coverage analysis for automotive software
View Case studies

Other Resources

 Webinars

 Brochures

 Product briefs

 Technical notes

 Research projects

 Multicore resources

Discover Rapita

Who we are

The company menu

  • About us
  • Customers
  • Distributors
  • Locations
  • Partners
  • Research projects
  • Contact us

US office

+1 248-957-9801
info@rapitasystems.com
Rapita Systems, Inc.
41131 Vincenti Ct.
Novi
MI 48375
USA

UK office

+44 (0)1904 413945
info@rapitasystems.com
Rapita Systems Ltd.
Atlas House
Osbaldwick Link Road
York, YO10 3JB
UK

Spain office

+34 93 351 02 05
info@rapitasystems.com
Rapita Systems S.L.
Parc UPC, Edificio K2M
c/ Jordi Girona, 1-3
Barcelona 08034
Spain

Working at Rapita

Careers

Careers menu

  • Current opportunities & application process
  • Working at Rapita
Back to Top Contact Us

Going above and beyond the quality standards

Breadcrumb

  1. Home
Sevane Fourmigue
2020-11-03

We take the quality and testing of our software very seriously – as seriously as you take yours. We take it so seriously that we meet many criteria that aren't required (per DO-330) for qualification of our tools, based on their Tool Qualification Level, TQL-5. We do this because we think it’s good practice, and because it gives us confidence in the quality of our products, which we consider to be just as important to us as it is to our customers. In this blog, we share a few examples of how we ensure this quality.

Requirements-based engineering

A key element of our quality approach is that we take requirements-based development further than is required by DO-330 or ISO 26262. Rather than using only a single set of Tool Operational Requirements for our RVS tools, we add a second level of detail to these requirements to better ensure that we examine the full scope of tool inputs. This is essential for a tool that deals with the complexities of different programming language standards.

Within that context, we write the developer-TOR, the internal tool requirements, the tool test plans and the tool component tests, and we manage full upwards and downwards traceability of all of these items. We ensure that all items are reviewed independently and against each other, hence complying with items in DO-330's “ Table T-6: Testing of outputs of integration process ”. This approach means that we have baselines both for the development and qualification of our tools. This is an example of how we respect the DO-330 criterion “ T8-2 Baselines and traceability are established ”, for which compliance is not required at TQL5.

This is a very laborious process, but it gives us confidence in understanding exactly how our tools behave, giving credence to the claim that we take quality very seriously.

Testing and automation

We’ve developed our own test harness and infrastructure that lets us fully automate running our tests. We run our full testing suite (a close equivalent to running system acceptance tests) multiple times daily as part of our in-house continuous build system. This reduces the risk of human error and lets us run tests often and detect any defects early in development.

We run state-of-the art testing – not only of nominal cases, but also of robustness cases, range cases etc. Our full qualification kit test suite includes over 180,000 lines of code. Of course, it isn’t just about the quantity of test code, but about testing the right components of our tools, and we have this covered – for example, we test nested decisions up to a nesting depth of 80 to ensure that our tools work with rare (but possible) corner cases. This gives us visibility and confidence in the completeness of our test suite.

Configuration management process

We use version control and issue-tracking (bug) management systems. This respects the DO-330 criterion “ T8-3 Problem reporting, change control, change review, and configuration status accounting are established ”, which we meet even though it‘s not needed at TQL-5. Whenever we fix a bug in our software, we write a test demonstrating that the bug is no longer present. We then add this to our growing suite of regression tests to ensure that we never reintroduce past errors in our software.

We maintain our tool life cycle environment under revision control, and we tag it automatically as part of the tool release process. This complies with another DO-330 criterion that’s optional for us – “ T8-5 Tool life cycle environment control is established ” – and helps us provide support to customers using previous versions of our tools. We also tag and securely store all of our tool releases for future use or reference. Finally, we can (and sometimes do) re-run the release process and compare the built artifacts with the ones we stored previously to ensure that we are able to rebuild superseded releases.

Plans and standards

We have internal processes that we apply to tool releases and non-conformance scenarios, and we perform periodic internal audits. We also have internal coding standards, requirements standards, and testing standards that we follow and audit against. This meets the DO-330 criterion “ T9-1 Assurance is obtained that tool plans and standards are developed and reviewed for consistency ”.

Assurance issues

There is no software without bugs. We do everything we can to find defects in our tools as early as possible and fix them. If we find defects that affect our assurance case, we let you know about them instead of hiding them, as is well explained in our post on our Assurance Issue process.

Conclusion

At Rapita, we don’t just do what we must to develop and qualify our tools, we do everything we think is important to deliver quality tools that we’re confident about, so that you can rely on them for your software verification.

Whatever your tool qualification needs are, we believe that we can meet them. We currently offer tool qualification support for the use of RVS tools in DO-178B, DO-178C and ISO 26262 projects. For more information, visit our qualification page or contact us.

DO-178C webinars

DO178C webinars

White papers

Mitigation of interference in multicore processors for A(M)C 20-193
Sysgo WP Developing DO-178C and ED-12C-certifiable multicore software
DO178C Handbook Efficient Verification Through the DO-178C Life Cycle
A Commercial Solution for Safety-Critical Multicore Timing Analysis

Related blog posts

DO-178C - Stage of Involvement 4

.
2022-04-06

DO-178C - Stage of Involvement 3

.
2022-03-23

DO-178C - Stage of Involvement 2

.
2022-03-09

DO-178C - Stage of Involvement 1

.
2022-03-01

Pagination

  • Current page 1
  • Page 2
  • Page 3
  • Page 4
  • Page 5
  • Next page Next ›
  • Last page Last »
  • Solutions
    • Rapita Verification Suite
    • RapiTest
    • RapiCover
    • RapiTime
    • RapiTask
    • MACH178

    • Verification and Validation Services
    • Qualification
    • Training
    • Integration
  • Latest
  • Latest menu

    • News
    • Blog
    • Events
    • Videos
  • Downloads
  • Downloads menu

    • Brochures
    • Webinars
    • White Papers
    • Case Studies
    • Product briefs
    • Technical notes
    • Software licensing
  • Company
  • Company menu

    • About Rapita
    • Careers
    • Customers
    • Distributors
    • Industries
    • Locations
    • Partners
    • Research projects
    • Contact
  • Discover
    • Multicore Timing Analysis
    • Embedded Software Testing Tools
    • Worst Case Execution Time
    • WCET Tools
    • Code coverage for Ada, C & C++
    • MC/DC Coverage
    • Verifying additional code for DO-178C
    • Timing analysis (WCET) & Code coverage for MATLAB® Simulink®
    • Data Coupling & Control Coupling
    • Aerospace Software Testing
    • Automotive Software Testing
    • Certifying eVTOL
    • DO-178C
    • AC 20-193 and AMC 20-193
    • ISO 26262
    • What is CAST-32A?

All materials © Rapita Systems Ltd. 2025 - All rights reserved | Privacy information | Trademark notice Subscribe to our newsletter