Verification Validation of Safety Critical Software安全关键软件验证与确认.pptVIP

下载本文档

8
0
约9.49千字
约 28页
2019-08-07 发布于江西
举报
版权申诉

Verification Validation of Safety Critical Software安全关键软件验证与确认.ppt

1、原创力文档（book118）网站文档一经付费（服务费），不意味着购买了该文档的版权，仅供个人/单位学习、研究之用，不得用于商业用途，未经授权，严禁复制、发行、汇编、翻译或者网络传播等，侵权必究。。
2、本站所有内容均由合作方或网友上传，本站不对文档的完整性、权威性及其观点立场正确性做任何保证或承诺！文档内容仅供研究参考，付费前请自行鉴别。如您付费，意味着您自己接受本站规则且自行承担风险，本站不退款、不进行额外附加服务；查看《如何避免下载的几个坑》。如果您已付费下载过本站文档，您可以点击这里二次下载。
3、如文档侵犯商业秘密、侵犯著作权、侵犯人身权等，请点击“版权申诉”（推荐），也可以打举报电话：400-050-0827(电话支持时间：9:00-18:30)。
4、该文档为VIP文档，如果想要下载，成为VIP会员后，下载免费。
5、成为VIP后，下载本文档将扣除1次下载权益。下载后，不支持退款、换文档。如有疑问请联系我们。
6、成为VIP后，您将拥有八大权益，权益包括：VIP文档下载权益、阅读免打扰、文档格式转换、高级专利检索、专属身份标志、高级客服、多端互通、版权登记。
7、VIP文档为合作方或网友上传，每下载1次，网站将根据用户上传文档的质量评分、类型等，对文档贡献者给予高额补贴、流量扶持。如果你也想贡献VIP文档。上传文档

Abstract of talk (1) The increasing trend towards systems integration, and increased automation of critical functions which were once performed by humans, means that more and more reliance is placed on software. Procurers of safety-critical systems are becoming more aware of the need for appropriate levels of safety assurance, and are increasingly requiring system developers to produce a Safety Case to document the reasons why a system is safe to be operated. Abstract of talk (2) This talk looks at recent and emerging standards for safety-critical software, and will introduce listeners to the key principles of safety assurance, including: hazard and risk analysis safety integrity levels the structure and content of safety cases management of the safety process Computer Aided Disasters Therac 25 (1985-87, N. America) radiation therapy machine delivers severe radiation overdoses (x6) London Ambulance Service (1992) 20+ die unnecessarilly when dispatch system fails USS Vincennes (1988) shoots down Iran Air airliner after faulty identification Airbus A320 (1988-) various crashes Ariane 5 (1996) software exception causes self-destruct etc See lab.ox.ac.uk/archive/safety.html /risks.html What’s Different About Software? Broadly speaking, traditional safety engineering is concerned with physical failures: e.g. wear-out, corrosion, faulty manufacture mitigations include: well-tried designs, safety margins, redundant components, inspection, maintenance this has little relevance for software On the other hand, software is typically: novel, complex, highly input-sensitive, not designed by domain experts Software demands a new approach to safety engineering Talk outline Define main terms concepts in safety engineering as they relate to software: hazards, risk, safety integrity levels, etc Explain the basic principles of safety management the safety lifecycle for software systems Outline 3 important safety analysis techniques Failure Modes Effects Analysis (FMEA)