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

Engineering 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

NAVAIR FACE & SOSA TIM and Expo
2023-09-12
DASC 2023
2023-10-01
HISC 2023
2023-10-17
Aerospace Tech Week Americas 2023
2023-11-14
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

Challenges of certifying multicore avionics in line with A(M)C 20-193 objectives - ATW Europe 2023
Streamlined software verification with RVS 3.18
Sequence analysis with RapiTime
Visualize call dependencies with RVS thumbnail
Visualize call dependencies 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 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

1000 conditions per decision ought to be enough for anybody

Breadcrumb

  1. Home
  2. Blog
  3. 1000 conditions per decision ought to be enough for anybody
Dr Antoine Colin
2019-01-28

Modified condition/decision coverage (MC/DC) testing requires testing, among other things, that each condition in a decision takes every possible outcome, and independently affects the outcome of the decision.

Coverage analysis tools test for MC/DC by observing results when the value of each condition is changed independently from the other conditions in the decision (though, with some clever logic, masking MC/DC can reduce overheads in some cases).

Most coverage analysis tools support what they deem to be a "reasonable" number of conditions per decision (our customers report that limits of 17 to 20 conditions per decision are common). But what if one of your decisions exceeds this arbitrary limit? You could:

  • Change your code (but why should you?)
  • Perform MC/DC analysis by hand (how many conditions? 50? good luck!)

RapiCover, however, is not like most coverage analysis tools - supporting up to 1000 conditions per decision.

Q&A:

Why do you support so many conditions per decision?
Because we can, and because your code may include giant decisions (we aren't judging). In fact, when NASA analyzed 5 different Line Replacement Units (LRU) from 5 different airborne systems they found 2 decisions with more than 36 conditions (table below). Table from NASASource: https://shemesh.larc.nasa.gov/fm/papers/Hayhurst-2001-tm210876-MCDC.pdf

Surely, nobody would write a decision that big, right?
While you're unlikely to write something like this by hand, if you're using model driven development (MDD), your automatically generated code may include decisions with a large number of conditions (for example code for aggregating large numbers of boolean signals).

Why only 1000 conditions?
We can support more than 1000 if you really need it! (but we'd be curious to see the code that requires this).

What does a RapiCover report with such large decisions look like?
I'm glad you asked. See Figure 1 below. Note that you can scroll to view the full file in the source code view.

 
 
 

   

Figure 1. RapiCover report from a decision with almost 1000 conditions

The example in Figure 1 shows a function that aggregates hundreds of boolean signals (just short of 1000 ) into a "warning light" signal. This is a bit like the piece of software that lights up the engine light on your dashboard. There are many error signals that can cause this light to come on and they can be all listed in a large or  boolean expression making a very large MC/DC decision.

The example report above shows the RapiCover MC/DC view with the coverage status of close to 1000 conditions in both the table view and the colorized source code view.

In the source code view, you can see a few coverage holes. For example, while various subsystems are missing a few tests to cover all their signals, the Turbolift subsystem has not been tested at all, and all of the GravityGenerator signals have been addressed using justifications rather than tested.

As a final note, it is interesting to see that Ada is still a popular choice for Aerospace software development in the 23rd century - as shown by this example.

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

False positive and false negative in software testing

.
2019-05-22

Code coverage without instrumentation

.
2018-10-18

Merging coverage data from multiple test runs

.
2017-01-31

How do I demonstrate the safe use of instrumented source code analysis?

.
2015-08-21

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