{"title":"智能控制的可维护性分析","authors":"D. Raheja, G. Raheja","doi":"10.1109/ISIC.1988.65462","DOIUrl":null,"url":null,"abstract":"The issue of software maintainability analysis for intelligent controls is discussed. Software maintainability can be expressed as the probability that the downtime caused by software error shall be no more than a specified time when maintenance action is performed in accordance with the prescribed procedures and resources. The proposed approach makes use of systematic analysis such as failure modes, effects, and criticality analysis (FMECA) or an equivalent methodology. The purpose is to predict missing requirements that could help in reducing the downtime. The procedure used involves constructing the program instruction flow chart, documenting maintainability requirements, and software failure mode and effects analysis. Examples of the development of requirements are presented.<<ETX>>","PeriodicalId":155616,"journal":{"name":"Proceedings IEEE International Symposium on Intelligent Control 1988","volume":"38 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"1988-08-24","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"0","resultStr":"{\"title\":\"Maintainability analysis for intelligent controls\",\"authors\":\"D. Raheja, G. Raheja\",\"doi\":\"10.1109/ISIC.1988.65462\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"The issue of software maintainability analysis for intelligent controls is discussed. Software maintainability can be expressed as the probability that the downtime caused by software error shall be no more than a specified time when maintenance action is performed in accordance with the prescribed procedures and resources. The proposed approach makes use of systematic analysis such as failure modes, effects, and criticality analysis (FMECA) or an equivalent methodology. The purpose is to predict missing requirements that could help in reducing the downtime. The procedure used involves constructing the program instruction flow chart, documenting maintainability requirements, and software failure mode and effects analysis. Examples of the development of requirements are presented.<<ETX>>\",\"PeriodicalId\":155616,\"journal\":{\"name\":\"Proceedings IEEE International Symposium on Intelligent Control 1988\",\"volume\":\"38 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"1988-08-24\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"0\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"Proceedings IEEE International Symposium on Intelligent Control 1988\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/ISIC.1988.65462\",\"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 IEEE International Symposium on Intelligent Control 1988","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/ISIC.1988.65462","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
The issue of software maintainability analysis for intelligent controls is discussed. Software maintainability can be expressed as the probability that the downtime caused by software error shall be no more than a specified time when maintenance action is performed in accordance with the prescribed procedures and resources. The proposed approach makes use of systematic analysis such as failure modes, effects, and criticality analysis (FMECA) or an equivalent methodology. The purpose is to predict missing requirements that could help in reducing the downtime. The procedure used involves constructing the program instruction flow chart, documenting maintainability requirements, and software failure mode and effects analysis. Examples of the development of requirements are presented.<>
求助内容：
应助结果提醒方式：
京公网安备 11010802042870号
