-
Notifications
You must be signed in to change notification settings - Fork 2
Norms and certifications
Table of content:
DO-330 is a set of considerations which can also be used outside airborne and ground based avionics systems. It is not a supplement DO-178C & DO-278A like DO-331, 223, and 333.
source: https://www.advicegear.net/do-330-understanding/
RTCA DO-330 (paid): https://my.rtca.org/NC__Product?id=a1B36000001IcfkEAC
TODO
Basic information about the standard can be found here: https://apps.dtic.mil/dtic/tr/fulltext/u2/a558107.pdf
RTCA DO-178C (paid): https://my.rtca.org/NC__Product?id=a1B36000001IcmqEAC
Used by NASA and can be found on their NODIS (MASA Online Directives Information System). Website: https://nodis3.gsfc.nasa.gov/
The document can be found on NODIS database.
MISRA C is a set of software development guidelines for the C programming language developed by MISRA (Motor Industry Software Reliability Association). Its aims are to facilitate code safety, security, portability and reliability in the context of embedded systems, specifically those systems programmed in ISO C / C90 / C99.
Webiste: https://www.misra.org.uk Wiki page : https://en.wikipedia.org/wiki/MISRA_C
MISRA-RUST : https://github.com/PolySync/misra-rust
An investigation into what adhering to each MISRA-C rule looks like in Rust. The intention is to decipher how much we "get for free" from the Rust compiler.