Abstract
In the paper a very simple model of a software failure rate is derived. This model is not intended to compute the failure rate or failure probability of software under realistic conditions. It is rather used to show the influences of measures for software quality assurance and of measures required by software safety standards on this failure rate, i.e. a tendency. In particular, it is shown that testing is important to reduce software failure rate and the effect is the larger, the closer testing is to exhaustive testing. Verification is also important and it needs to be done by an independent person or party to give a good effect. Another result is that software failure rate grows with the size of the software, the frequency the software is used and, the fraction of the software that is used per demand cycle. As a result, it is recommended to implement the measures with more consequence and rigidity, the larger the part of the software that is used, the larger the software itself and the more frequently it is used.