Be the first to like this
Mission-critical software has become very reliable and robust by adhering to high quality safety standards in the development lifecycle. An example of mission-critical software, also called “safety
critical,” is the software implemented in passenger aircraft, or in control systems operating nuclear and chemical plants. Safety critical software includes those applications whose malfunction can
cause multiple deaths. Conventional software applications, i.e. applications that are not critical and more commonly used, can be
made as robust and reliable as mission-critical software by following the simple best practices required for mission-critical software with
very little or no additional effort. Though there are mandatory procedures prescribed by safety standards that can require significant additional effort, the focus of this paper is to highlight
practices that can be implemented in any project with very little additional effort.