This paper describes a new analysis technique developed specifically to study the safety implications of the relationship between software and the hardware on which it runs. The technique was developed in response to a request for assistance in completing the safety argument for a critical avionics application. Evidence was required that the segregation mechanism, used to partition functions of different integrity levels running on the same processor, would adequately protect critical program and data memory from corruption by the lower integrity software. The technique is based on an analysis of time and physical resources, using interpretations of a number of generic failure classes to prompt consideration of various hypothetical deviatio...
Even if software code is fault-free, hardware failures can alter a value in memory, possibly where t...
For a possibility of using the safety relevant system in practice, it is necessary to prove, that sa...
Abstract—It is difficult to demonstrate that safety-critical software is com-pletely free of dangero...
When considering the production of a computer-based system, it is common to partition the arrangemen...
The safety analysis of an evolving software system has to consider the impact that changes might hav...
Computing systems in which the consequences of failure are very serious are termed safety-critical....
: A growing number of safety--related applications are dependent on software for their control. High...
Embedded systems based on different types of hardware platforms are nowadays increasingly used in sa...
The safety analysis of an evolving software system has to consider the impact that changes might hav...
Abstract: In order to facilitate the process of safety analysis of an evolving software system, this...
As software systems increasingly are used to control critical infrastructure, transportation systems...
Techniques developed for hardware reliability and safety do not work on software-intensive systems; ...
Abstract. Safety is a system property and software, of itself, cannot be safe or unsafe. However sof...
It is difficult to demonstrate that safety-critical software is completely free of dangerous faults....
Traditional methods for the assessment of software safety suffer from poor integration (from methodo...
Even if software code is fault-free, hardware failures can alter a value in memory, possibly where t...
For a possibility of using the safety relevant system in practice, it is necessary to prove, that sa...
Abstract—It is difficult to demonstrate that safety-critical software is com-pletely free of dangero...
When considering the production of a computer-based system, it is common to partition the arrangemen...
The safety analysis of an evolving software system has to consider the impact that changes might hav...
Computing systems in which the consequences of failure are very serious are termed safety-critical....
: A growing number of safety--related applications are dependent on software for their control. High...
Embedded systems based on different types of hardware platforms are nowadays increasingly used in sa...
The safety analysis of an evolving software system has to consider the impact that changes might hav...
Abstract: In order to facilitate the process of safety analysis of an evolving software system, this...
As software systems increasingly are used to control critical infrastructure, transportation systems...
Techniques developed for hardware reliability and safety do not work on software-intensive systems; ...
Abstract. Safety is a system property and software, of itself, cannot be safe or unsafe. However sof...
It is difficult to demonstrate that safety-critical software is completely free of dangerous faults....
Traditional methods for the assessment of software safety suffer from poor integration (from methodo...
Even if software code is fault-free, hardware failures can alter a value in memory, possibly where t...
For a possibility of using the safety relevant system in practice, it is necessary to prove, that sa...
Abstract—It is difficult to demonstrate that safety-critical software is com-pletely free of dangero...