Skip to main content
RVS 3.21 Launched
Embedded Office GmbH & Co. KG and Rapita Systems announce strategic partnership
Rapita Systems and LICRIT announce strategic partnership
RVS 3.20 Launched
Control Coupling Basics in DO-178C
Components in Data Coupling and Control Coupling
The ‘A’ Team comes to the rescue of code coverage analysis
Why there’s no standard approach for Data Coupling and Control Coupling Analysis
DO-278A Guidance: Introduction to RTCA DO-278 approval
ISO 26262
Data Coupling & Control Coupling
Verifying additional code for DO-178C
HISC 2024
DO-178C Multicore In-person Training (Munich)
DO-178C Multicore In-person Training (Fort Worth, TX)
DO-178C Multicore In-person Training (Toulouse)
When you're using RapiCover justifications to mark your untestable code as covered by analysis, you can configure custom fields for your justifications, for example to reference the requirements your justified element is specified in, or the rationale for justifying it.
Using a simple interface, it's easy to configure new text fields that let you enter any string, or selection boxes that let you select one from a number of values you add for the field. After configuring your new custom field, you can use it in both new and existing justifications, and the values you set for custom fields are reported with your justifications.
If you're using templates for your justifications, you can add default values for custom fields to your templates, and of course, values in custom fields are migrated along with your justifications.
Feature applies to:
