Your browser does not support JavaScript! Skip to main content
Free 30-day trial Customer portal Careers DO-178C Handbook
 
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

Multicore verification

  MACH178   Multicore Timing Solution   RapiDaemons

Services

  V & V Services   Qualification   Training   Tool Integration  Support

Industries

  Aerospace (DO-178C)   Automotive (ISO 26262)   Space

Other

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

Latest from Rapita HQ

Latest news

RVS 3.18 Launched
Solid Sands partners with Rapita Systems
Danlaw Acquires Maspatechnologies - Expanding Rapita Systems to Spain
Rapita co-authored paper wins ERTS22 Best paper award
View News

Latest from the Rapita blog

Measuring response times and more with RapiTime
Why mitigating interference alone isn’t enough to verify timing performance for multicore DO-178C projects
There are how many sources of interference in a multicore system?
Supporting modern development methodologies for verification of safety-critical software
View Blog

Latest discovery pages

do178c DO-178C Guidance: Introduction to RTCA DO-178 certification
matlab_simulink MATLAB® Simulink® MCDC coverage and WCET analysis
code_coverage_ada Code coverage for Ada, C and C++
amc-20-193 AMC 20-193
View Discovery pages

Upcoming events

Aerospace Tech Week Europe 2023
2023-03-29
Aeromart Montreal 2023
2023-04-04
Certification Together International Conference
2023-05-10
View Events

Technical resources for industry professionals

Latest White papers

DO178C Handbook
Efficient Verification Through the DO-178C Life Cycle
A Commercial Solution for Safety-Critical Multicore Timing Analysis
Compliance with the Future Airborne Capability Environment (FACE) standard
View White papers

Latest Videos

Streamlined software verification with RVS 3.18
Sequence analysis with RapiTime
Visualize call dependencies with RVS thumbnail
Visualize call dependencies with RVS
Analyze code complexity thumbnail
Analyze code complexity with RVS
View Videos

Latest Case studies

Supporting ISO 26262 ASIL D software verification for EasyMile
RapiCover’s advanced features accelerate the certification of military UAV Engine Control
Front cover of whitepaper collins
Delivering world-class tool support to Collins Aerospace
View Case studies

Other Downloads

 Webinars

 Brochures

 Product briefs

 Technical notes

 Research projects

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 930 46 42 72
info@rapitasystems.com
Rapita Systems S.L.
Parc UPC, Edificio K2M
c/ Jordi Girona, 1-3, Office 306-307
Barcelona 08034
Spain

Working at Rapita

Careers

Careers menu

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

What should we really think about measuring WCET?

Breadcrumb

  1. Home
  2. Blog
  3. What should we really think about measuring WCET?
Ian Broster
2012-02-23

Following on from my last blog post grumbling about the mixing of terminologies from timing and safety domains, this post explains some of the background to WCET analysis and what RapiTime does.

Understanding what hard and soft real-time actually means

First, we need to think about safety and criticality. I'm going to start by talking about what we mean by hard and soft real-time.

The term "hard real-time" is often misquoted and misused. Hard real-time typically means that missing the deadline implies that the system may fail to achieve its requirements. We should not confuse the "hardness" of a deadline with the system safety.

(As an example, the electronics that controls a camera flash on a mobile phone could be considered hard real-time: if it's too slow then you get dark photos and fail to meet the requirement of taking good photos, but nobody dies. To complete the example, a soft real-time deadline might be the reaction to pressing the button on the camera: if it's too slow, you take a good picture, but perhaps you would have liked it to be a bit quicker).

For most computer systems, if people can be bothered to think about execution times, using a WCET based on a simple end to end maximum, or a maximum + margin is a perfectly adequate method to ensure that their program works well enough for their purposes.

For the remaining (and relatively small percentage of) systems that actually deal with hard deadlines (our customers), what happens if you underestimate the WCET? That depends on the system, how it's been designed and what it's used for. If you're building safety-critical hard real-time systems (say a flight control system), then you might want to understand your WCET really well. If you're building a camera flash, you might want to understand it pretty well (after all, who wants a phone where the camera flash doesn't always work properly).

So, can you use measurements for safety-critical real-time systems?

Of course you can. It's what people have been doing for years. Testing is fundamental to the way we build reliable software. Would you fly in an airplane that had been thoroughly analyzed but had never been tested?

So what does RapiTime do?

  1. RapiTime automatically takes many detailed measurements of small parts of your program (not just end-to-end measurements!) to allow you to understand your execution times, worst case execution times and optimize your program.
  2. RapiTime computes a WCET estimate based on a careful structural analysis of the source code and lots of test-based evidence.
  3. RapiTime helps you to improve your testing, so you can show real, traceable evidence that you have tested your system adequately.

Are RapiTime's WCET results "optimistic" or "pessimistic"?

Contrary to popular rumour, pessimism is the bigger challenge, not optimism! We spend time to reduce the pessimism with various techniques to provide you with a really good WCET value.

DO-178C webinars

DO178C webinars

White papers

DO178C Handbook Efficient Verification Through the DO-178C Life Cycle
A Commercial Solution for Safety-Critical Multicore Timing Analysis
Compliance with the Future Airborne Capability Environment (FACE) standard
5 key factors to consider when selecting an embedded testing tool

Related blog posts

Why Static analysis doesn't work for Multicore WCET estimation

.
2019-10-07

WCET analysis of object code with zero instrumentation

.
2017-02-27

A funny thing happened on the way to a Worst-Case Execution Time Conference...

.
2015-10-09

Things that make real-time hard - parallelization

.
2013-09-04

Pagination

  • Current page 1
  • Page 2
  • Page 3
  • Page 4
  • Page 5
  • Page 6
  • 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
    • AMC 20-193
    • What is CAST-32A?
    • Multicore Timing Analysis
    • MC/DC Coverage
    • Code coverage for Ada, C & C++
    • Embedded Software Testing Tools
    • Aerospace Software Testing
    • Automotive Software Testing
    • Certifying eVTOL
    • DO-178C
    • WCET Tools
    • Worst Case Execution Time
    • Timing analysis (WCET) & Code coverage for MATLAB® Simulink®

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