{"title":"将正式的安全分析集成到未来的软件工程过程中:来自起搏器行业的一个例子","authors":"D. Santel, C. Trautmann, W. Lui","doi":"10.1109/ECBS.1988.5465","DOIUrl":null,"url":null,"abstract":"An example from the cardiac pacemaker industry of safety-orientated software-design methodology is provided. Safety consideration begins upon product description with a hazard analysis whereby potential hazards are classified according to their criticality and rough probability of occurrence. The completed hazard analysis determines the software safety requirements which specify what the system will not do. A system-hazard cross-check matrix is defined that serves to direct the design team to those areas requiring more scrutiny. Traceability matrices provide a verifiable link from safety requirements design to the actual code. This methodology should serve to minimize hazards in the final software product.<<ETX>>","PeriodicalId":291071,"journal":{"name":"Proceedings of the Symposium on the Engineering of Computer-Based Medical","volume":"58 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"1988-06-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"8","resultStr":"{\"title\":\"The integration of a formal safety analysis into the future software engineering process: An example from the pacemaker industry\",\"authors\":\"D. Santel, C. Trautmann, W. Lui\",\"doi\":\"10.1109/ECBS.1988.5465\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"An example from the cardiac pacemaker industry of safety-orientated software-design methodology is provided. Safety consideration begins upon product description with a hazard analysis whereby potential hazards are classified according to their criticality and rough probability of occurrence. The completed hazard analysis determines the software safety requirements which specify what the system will not do. A system-hazard cross-check matrix is defined that serves to direct the design team to those areas requiring more scrutiny. Traceability matrices provide a verifiable link from safety requirements design to the actual code. This methodology should serve to minimize hazards in the final software product.<<ETX>>\",\"PeriodicalId\":291071,\"journal\":{\"name\":\"Proceedings of the Symposium on the Engineering of Computer-Based Medical\",\"volume\":\"58 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"1988-06-08\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"8\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"Proceedings of the Symposium on the Engineering of Computer-Based Medical\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/ECBS.1988.5465\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"Proceedings of the Symposium on the Engineering of Computer-Based Medical","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/ECBS.1988.5465","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
The integration of a formal safety analysis into the future software engineering process: An example from the pacemaker industry
An example from the cardiac pacemaker industry of safety-orientated software-design methodology is provided. Safety consideration begins upon product description with a hazard analysis whereby potential hazards are classified according to their criticality and rough probability of occurrence. The completed hazard analysis determines the software safety requirements which specify what the system will not do. A system-hazard cross-check matrix is defined that serves to direct the design team to those areas requiring more scrutiny. Traceability matrices provide a verifiable link from safety requirements design to the actual code. This methodology should serve to minimize hazards in the final software product.<>
求助内容：
应助结果提醒方式：
京公网安备 11010802042870号
