Tezislər / Theses

1. Introduction 
Much of the safety critical software is written for embedded systems. 
Industries, like the automotive industry rely a lot on software in their products 
being robust and well tested. Failure in critical parts of the system will result 
in unacceptable levels of damage, such as the loss of or serious damage to 
human lives. In addition to that, embedded software is almost exclusively 
developed in the C and C++ programming languages because they are very 
efficient, allow high levels of control over the hardware and require little to no 
runtime support, in compression to managed languages, like Java. But C and 
C++ are very prone to errors and bugs. Many of such problems arise from 

---

THE 3
rd
 INTERNATIONAL SCIENTIFIC CONFERENCES OF STUDENTS AND YOUNG RESEARCHERS 
dedicated to the 99
th
anniversary of the National Leader of Azerbaijan Heydar Aliyev
194
the fact that those languages are not memory safe, thus do not protect from 
misuse of pointers and memory buffers. Another point to consider is that 
different implementations of these languages show different behavior under 
different circumstances in subtle and sometimes difficult to test or detect 
ways. Behavior of the generated binary is left unspecified or implementation-
defined in many cases, even though the languages are standardized by 
international bodies like ISO and ANSI. To ameliorate safety issues, 
programmers rely on well tested guidelines which are designed to be robust 
and tested throughout years. 
Different sets of guidelines and rules are designed and developed over 
the years and each of those sets have different tradeoffs designed for 
different fields. This paper presents our overview of some of the guidelines 
we consider to be good and widely applicable.