1 / 9

Open source components in safety critical systems

Open source components in safety critical systems. Suvi-Maaret Suomalainen 7.12.2004. Introduction QA for safety critical system QA in open source development Examples Conclusions. Content. Introduction (1/2). Background - use of safety critical system - closed automation system

clodia
Télécharger la présentation

Open source components in safety critical systems

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Open source components in safety critical systems Suvi-Maaret Suomalainen 7.12.2004

  2. Introduction QA for safety critical system QA in open source development Examples Conclusions Content

  3. Introduction (1/2) • Background • - use of safety critical system • - closed automation system • - quality of OSS • Motivation • - closed system • - few suppliers • - high prices

  4. Introduction (2/2) • Research Problem and objectives • Can components of the safety critical software be open source components? • Comparing OSS quality assurance to the requirements of IEC 61508 • Method • Literature study • INSPEC and IEEE databases • Scope • European IEC 61508 • Verification methods • No hardware requirements

  5. QA for safety critical system • Safety plan • software lifecycle • Testing • test plans in early phases • documentation • test tools and environments • testing independence • Testing techniques • dynamic • static • modeling

  6. QA in open source projects • No project plan • good configuration tools • change management differs • No testing plans • Different techniques • Testing independence • No documents • Highly motivated developers

  7. Examples • Most used Linux (OS and real time OS) • CVS repositories • Bug database • Documentation volunteer work • Others used in user interfaces and specification tool (not so safety critical) • NASA experiences • Project maturity • Project longevity • Flexibililty

  8. Conclusions • Differences between IEC 61508 and OSS • test plans • testing techniques mainly dynamic • documentation • change management • OSS can’t be used as such • management for the developer of the safety system • testing and documenting…

More Related