{"title":"用于回顾性安全案例的软件安全风险分类法","authors":"Janice Hill","doi":"10.1109/SEW.2007.88","DOIUrl":null,"url":null,"abstract":"Safety standards contain technical and process-oriented safety requirements. The best time to include these requirements is early in the development lifecycle of the system. When software safety requirements are levied on a legacy system after the fact, a retrospective safety case will need to be constructed for the software in the system. This can be a difficult task because there may be few to no artifacts available to show compliance to the software safety requirements. The risks associated with not meeting safety requirements in a legacy safety-critical computer system must be addressed to give confidence for reuse. This paper introduces a proposal for a software safety risk taxonomy for legacy safety-critical computer systems, by specializing the Software Engineering Institute's 'Software Development Risk Taxonomy' with safety elements and attributes.","PeriodicalId":277367,"journal":{"name":"31st IEEE Software Engineering Workshop (SEW 2007)","volume":"12 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2007-03-06","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"7","resultStr":"{\"title\":\"A Software Safety Risk Taxonomy for Use in Retrospective Safety Cases\",\"authors\":\"Janice Hill\",\"doi\":\"10.1109/SEW.2007.88\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"Safety standards contain technical and process-oriented safety requirements. The best time to include these requirements is early in the development lifecycle of the system. When software safety requirements are levied on a legacy system after the fact, a retrospective safety case will need to be constructed for the software in the system. This can be a difficult task because there may be few to no artifacts available to show compliance to the software safety requirements. The risks associated with not meeting safety requirements in a legacy safety-critical computer system must be addressed to give confidence for reuse. This paper introduces a proposal for a software safety risk taxonomy for legacy safety-critical computer systems, by specializing the Software Engineering Institute's 'Software Development Risk Taxonomy' with safety elements and attributes.\",\"PeriodicalId\":277367,\"journal\":{\"name\":\"31st IEEE Software Engineering Workshop (SEW 2007)\",\"volume\":\"12 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2007-03-06\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"7\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"31st IEEE Software Engineering Workshop (SEW 2007)\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/SEW.2007.88\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"31st IEEE Software Engineering Workshop (SEW 2007)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/SEW.2007.88","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
A Software Safety Risk Taxonomy for Use in Retrospective Safety Cases
Safety standards contain technical and process-oriented safety requirements. The best time to include these requirements is early in the development lifecycle of the system. When software safety requirements are levied on a legacy system after the fact, a retrospective safety case will need to be constructed for the software in the system. This can be a difficult task because there may be few to no artifacts available to show compliance to the software safety requirements. The risks associated with not meeting safety requirements in a legacy safety-critical computer system must be addressed to give confidence for reuse. This paper introduces a proposal for a software safety risk taxonomy for legacy safety-critical computer systems, by specializing the Software Engineering Institute's 'Software Development Risk Taxonomy' with safety elements and attributes.
求助内容：
应助结果提醒方式：
京公网安备 11010802042870号
