Guidelines for NOT embedded SW?

Guidelines for NOT embedded SW? - Printable Version

+- MISRA Discussion Forums (https://forum.misra.org.uk)
+-- Forum: MISRA (https://forum.misra.org.uk/forumdisplay.php?fid=20)
+--- Forum: General Questions (https://forum.misra.org.uk/forumdisplay.php?fid=154)
+--- Thread: Guidelines for NOT embedded SW? (/showthread.php?tid=1380)

Guidelines for NOT embedded SW? - andream - 17-10-2017

I wonder if it has ever been specified a sort of equivalent MISRA C standard, always for safety-critical systems, but not embedded SW, rather running on host. For instance, Plant Monitoring and Air Traffic Management.

Re: Guidelines for NOT embedded SW? - misra-c - 13-11-2017

The Vision of MISRA C states:

Quote:The MISRA C Guidelines define a subset of the C language in which the opportunity to make mistakes is either removed or reduced. ... {and} can also be used to develop any application with high integrity or high reliability requirements.

While the legacy of the automotive origin of MISRA C is that it is focused on Freestanding applications, there is nothing inherent that precludes its use in Hosted applications... other than some broad-reaching Rules in the Standard Library sections (21.x and 22.x) which restrict the use of stdio.h and signal.h and some features of stdlib.h - you will require Deviations if you need to use those features.

These restrictions are due the undefined, unspecified and implementation-defined behaviours prevalent in those parts of the Standard Library.

Existing work within the MISRA C Working Group is, however, looking at creating more targeted guidance to aid wider take-up.

Re: Guidelines for NOT embedded SW? - andream - 13-11-2017

Thanks for the reply: quite rewarding and interesting. Thanks for informing me if and when a more targeted guidance, to aid wider MISRA C take-up, is available.