Changing software to implement new features, correct problems, update functions, or replace obsolete hardware components (e.g., microprocessors) is a way of life in today's industry. A systematic software change process is essential for the maintenance and reuse of safety-critical software. This paper presents activities to consider when changing software in safety-critical systems. The focus is on the aviation industry; however, the concepts are also applicable to other safety-critical domains, such as medical or nuclear.
A systematic process for changing safety-critical software
19th DASC. 19th Digital Avionics Systems Conference. Proceedings (Cat. No.00CH37126) ; 1 ; 1B1/1-1B1/7 vol.1
2000-01-01
611243 byte
Aufsatz (Konferenz)
Elektronische Ressource
Englisch
A Systematic Process for Changing Safety-Critical Software
British Library Conference Proceedings | 2000
|Changing safety-critical software
IEEE | 2001
|Articles - Changing Safety-Critical Software
Online Contents | 2001
|Software Production Process for Safety Critical Software
AIAA | 2008
|Changing Safety Critical Communications Behaviour
British Library Conference Proceedings | 2007
|