{"title":"建筑安全关键系统的软件安全风险分类中的产品工程类","authors":"Janice Hill, D. Victor","doi":"10.1109/ASWEC.2008.72","DOIUrl":null,"url":null,"abstract":"When software safety requirements are imposed on legacy safety-critical systems, retrospective safety cases need to be formulated as part of recertifying the systems for further use and risks must be documented and managed to give confidence for reusing the systems. The SEI software development risk taxonomy focuses on general software development issues. It does not, however, cover all the safety risks. The software safety risk taxonomy was developed which provides a construct for eliciting and categorizing software safety risks in a straightforward manner. In this paper, we present extended work on the taxonomy for safety that incorporates the additional issues inherent in the development and maintenance of safety-critical systems with software. An instrument called a software safety risk taxonomy based questionnaire (TBQ) is generated containing questions addressing each safety attribute in the software safety risk taxonomy. Software safety risks are surfaced using the new TBQ and then analyzed. In this paper we give the definitions for the specialized product engineering class within the software safety risk taxonomy. At the end of the paper, we present the tool known as the 'legacy systems risk database tool' that is used to collect and analyze the data required to show traceability to a particular safety standard.","PeriodicalId":231903,"journal":{"name":"19th Australian Conference on Software Engineering (aswec 2008)","volume":"17 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2008-03-26","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"9","resultStr":"{\"title\":\"The Product Engineering Class in the Software Safety Risk Taxonomy for Building Safety-Critical Systems\",\"authors\":\"Janice Hill, D. Victor\",\"doi\":\"10.1109/ASWEC.2008.72\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"When software safety requirements are imposed on legacy safety-critical systems, retrospective safety cases need to be formulated as part of recertifying the systems for further use and risks must be documented and managed to give confidence for reusing the systems. The SEI software development risk taxonomy focuses on general software development issues. It does not, however, cover all the safety risks. The software safety risk taxonomy was developed which provides a construct for eliciting and categorizing software safety risks in a straightforward manner. In this paper, we present extended work on the taxonomy for safety that incorporates the additional issues inherent in the development and maintenance of safety-critical systems with software. An instrument called a software safety risk taxonomy based questionnaire (TBQ) is generated containing questions addressing each safety attribute in the software safety risk taxonomy. Software safety risks are surfaced using the new TBQ and then analyzed. In this paper we give the definitions for the specialized product engineering class within the software safety risk taxonomy. At the end of the paper, we present the tool known as the 'legacy systems risk database tool' that is used to collect and analyze the data required to show traceability to a particular safety standard.\",\"PeriodicalId\":231903,\"journal\":{\"name\":\"19th Australian Conference on Software Engineering (aswec 2008)\",\"volume\":\"17 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2008-03-26\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"9\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"19th Australian Conference on Software Engineering (aswec 2008)\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/ASWEC.2008.72\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"19th Australian Conference on Software Engineering (aswec 2008)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/ASWEC.2008.72","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
The Product Engineering Class in the Software Safety Risk Taxonomy for Building Safety-Critical Systems
When software safety requirements are imposed on legacy safety-critical systems, retrospective safety cases need to be formulated as part of recertifying the systems for further use and risks must be documented and managed to give confidence for reusing the systems. The SEI software development risk taxonomy focuses on general software development issues. It does not, however, cover all the safety risks. The software safety risk taxonomy was developed which provides a construct for eliciting and categorizing software safety risks in a straightforward manner. In this paper, we present extended work on the taxonomy for safety that incorporates the additional issues inherent in the development and maintenance of safety-critical systems with software. An instrument called a software safety risk taxonomy based questionnaire (TBQ) is generated containing questions addressing each safety attribute in the software safety risk taxonomy. Software safety risks are surfaced using the new TBQ and then analyzed. In this paper we give the definitions for the specialized product engineering class within the software safety risk taxonomy. At the end of the paper, we present the tool known as the 'legacy systems risk database tool' that is used to collect and analyze the data required to show traceability to a particular safety standard.