MISRA Compliancy

Willert Software Tools GmbH has gone through great effort to adapt the code in the RXF to make it MISRA C++ 2008 compliant. If your application must be MISRA compliant, you must set up your own MISRA compliance process, which can be based on our product, your model and project specific MISRA documents and procedures. This should at least include:
  1. A compliance matrix, which shows how compliance has been enforced. 
  2. All of the code in the product is compliant with the MISRA rules or is subject to documented deviations. 
  3. A list of all instances of rules not being followed is maintained, and for each instance there is an appropriately signed-off deviation.
  4. The following issues have been addressed in the development team: 
    1. Training 
    2. Style guide 
    3. Compiler selection and validation 
    4. Checking tool validation 
    5. Metrics 
    6. Test coverage

In the sources of the RXF, excluding those of the Container Classes, you will find code comments, which refer to MISRA rules. These MISRA suppression comments use macros to be able to support different tools for MISRA compliancy checking. Some tools can be adapted to recognize these macros as specific rule suppression comments while for other tools such as PC-lint the macros need to be replaced by tool specific suppressions first.

Please contact our sales department at +49 5722 9678 60 for any questions or inquiries for acquiring our MISRA specific documents and procedures.

MISRA Settings / Profiles

The RXF profile implies MISRA improvement properties, which are automatically used when the RXF is used. The details of the overridden MISRA-related properties can be reviewed via the file "RXF\Profiles\Rhapsody\Properties\MISRA.prp".

In addition our RXFStereotypesCpp profile offers stereotypes that can be used in the user model to make e.g. an operation suppress some MISRA rule(s) in their body or specification, set up via tags.