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

XPONENTIAL 2025
2025-05-19
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
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

Measuring response times and more with RapiTime

Breadcrumb

  1. Home
Daniel Wright & Greg Manning
2023-03-10

Analysis of the timing behavior of avionics software helps avoid errors such as timing overruns and is needed to support DO-178C certification.

While many timing requirements relate to the worst-case execution time of software, some may relate to other metrics such as response time, periodicity of execution, or separation between different instances of a sequence running.

Execution time vs. response time  

The execution time of a piece of software is the time taken for a task to finish, ignoring time spent executing other functions or interrupts.  

The response time of a piece of software is the total time taken for a task to finish, including time spent executing code in other functions or interrupts.

 

As of RVS 3.18, RapiTime includes a sequence analysis feature that provides a flexible framework for making these kinds of timing observations. This lets you define sequences of checkpoints within your code across which you want to take measurements. For each sequence, you can define the measurements you want taken, which can be the elapsed time between any two checkpoints within the sequence. After measurements have been defined, RapiTime can instrument your code appropriately, collect the necessary results during software execution, and display these results in your RapiTime report.

Sequence analysis conceptual diagram
Interesting timing metrics across and between sequences include response time, periodicity and separation
Checkpoints and measurements for RapiTime sequences
Checkpoints and measurements for a sequence configured in Rapi Time
Results from RapiTime sequence analysis
Results from measuring execution of sequences in Rapi Time

This flexible framework also supports multicore timing analysis such as that carried out in our MACH178 solution to meet A(M)C 20-193 objectives for multicore DO-178C projects. Sequence analysis makes it possible to measure end-to-end timing metrics for sequences of events when multiple tasks run simultaneously, even when sequences involve checkpoints executing on different cores (as shown below).

 
References support distinguishing between different instances of sequences
Example multicore sequence involving multiple instances of a sequence executing on multiple cores, for which timing results can be collected by RapiTime
 

To support analysis in situations where multiple instances of a task may be running simultaneously, we needed to have a way to uniquely attribute checkpoints as belonging to a specific instance of a sequence. We did this by annotating each checkpoint with a sequence reference. When you define a checkpoint, you can supply a snippet of code that returns an integer shared by all checkpoints in the sequence, and is unique to each instantiation of the sequence. When each checkpoint is hit, this code is evaluated and the resulting integer is recorded in the checkpoint. This allows RVS to demultiplex sequences that execute simultaneously, so long as there is a distinguishing integer available.

 
References support distinguishing between different instances of sequences
Results from different instances of a sequence can be collected by using references – in this example, “num” is used as a reference as it has a unique value for each instance of the sequence
 

We're looking forward to see how RVS’s new sequence analysis feature can help you verify your critical software. We’ll be building on the feature to support more complex, non-linear sequences and sequences where no single distinguishing integer reference is available in future RVS versions, stay tuned!

To learn more about sequence analysis, visit our feature page or contact us. For more information on multicore certification, visit our MACH178 page.

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

Out of the box RVS integration for DDC-I's Deos RTOS

.
2020-02-23

WCET analysis of object code with zero instrumentation

.
2017-02-27

What happened first? Handling timer wraparound

.
2016-01-08

Conditional code without branches

.
2015-12-10

Pagination

  • Current page 1
  • Page 2
  • Page 3
  • Page 4
  • Page 5
  • Page 6
  • Page 7
  • Page 8
  • Page 9
  • 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