It goes without saying that safety is key when it comes to developing software in aerospace & defense. DO-178C advocates that in order to develop high integrity and reliable code 3 simple steps must be followed: have a process, adopt a coding standard or best practice and have proven, fit for purpose software tools. DO-330 describes how qualification can be achieved, both for development tools that modify code and potentially introduce errors and for verification tools such as static code analyzers, which do not introduce errors but may fail to detect them.
The webinar will explore:
- the key processes and coding standards/best practice adopted by aerospace & defense
- the role of coding standards/best practice in generating deterministic software
- determining a verification tool’s effectiveness
- some specific examples where safety has been compromised when errors were not detected
