{"title":"将软件故障模式和影响分析应用于界面","authors":"N. Ozarin","doi":"10.1109/RAMS.2009.4914732","DOIUrl":null,"url":null,"abstract":"Software failure modes and effects analysis (SFMEA) is sometimes applied to new mission-critical and safety-critical system development. This kind of analysis, like its older cousin Hardware FMEA (HFMEA), tries to determine all possible types of failure for each component, one by one, and attempts to predict system-level effects for each failure. While software variables and classes don't fail in the sense that hardware fails, variables do sometimes assume unexpected values [1] and class methods don't always perform as expected.","PeriodicalId":201787,"journal":{"name":"2009 Annual Reliability and Maintainability Symposium","volume":"22 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2009-05-12","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"10","resultStr":"{\"title\":\"Applying software failure modes and effects analysis to interfaces\",\"authors\":\"N. Ozarin\",\"doi\":\"10.1109/RAMS.2009.4914732\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"Software failure modes and effects analysis (SFMEA) is sometimes applied to new mission-critical and safety-critical system development. This kind of analysis, like its older cousin Hardware FMEA (HFMEA), tries to determine all possible types of failure for each component, one by one, and attempts to predict system-level effects for each failure. While software variables and classes don't fail in the sense that hardware fails, variables do sometimes assume unexpected values [1] and class methods don't always perform as expected.\",\"PeriodicalId\":201787,\"journal\":{\"name\":\"2009 Annual Reliability and Maintainability Symposium\",\"volume\":\"22 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2009-05-12\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"10\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"2009 Annual Reliability and Maintainability Symposium\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/RAMS.2009.4914732\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"2009 Annual Reliability and Maintainability Symposium","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/RAMS.2009.4914732","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
Applying software failure modes and effects analysis to interfaces
Software failure modes and effects analysis (SFMEA) is sometimes applied to new mission-critical and safety-critical system development. This kind of analysis, like its older cousin Hardware FMEA (HFMEA), tries to determine all possible types of failure for each component, one by one, and attempts to predict system-level effects for each failure. While software variables and classes don't fail in the sense that hardware fails, variables do sometimes assume unexpected values [1] and class methods don't always perform as expected.