{"title":"IEC 880: feedback of experience and guidelines for future work","authors":"N. Thuy, F. Ficheux-Vapne","doi":"10.1109/SESS.1995.525957","DOIUrl":null,"url":null,"abstract":"This paper presents an outline of the work currently done at Electricite de France for the identification of requirements applicable to software in category, B (as defined by publication 1226 of the IEC) systems. The first part presents an analysis of the weaknesses of publication 880 of the IEC, an existing and related standard expressing requirements applicable to software in category A systems. Based on this feedback of experience, the second part identifies some general recommendations and guidelines that should be followed for the establishment of requirements in a standard for software. The third part presents the main technical objectives that can be proposed for software in category B systems. These technical objectives are all derived from a unique primacy objective: safety integrity, i.e., the likelihood of software to achieve its safety functions under all stated conditions within a stated period of time.","PeriodicalId":178570,"journal":{"name":"Proceedings of Software Engineering Standards Symposium","volume":"1 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"1995-08-21","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"3","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"Proceedings of Software Engineering Standards Symposium","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/SESS.1995.525957","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 3
Abstract
This paper presents an outline of the work currently done at Electricite de France for the identification of requirements applicable to software in category, B (as defined by publication 1226 of the IEC) systems. The first part presents an analysis of the weaknesses of publication 880 of the IEC, an existing and related standard expressing requirements applicable to software in category A systems. Based on this feedback of experience, the second part identifies some general recommendations and guidelines that should be followed for the establishment of requirements in a standard for software. The third part presents the main technical objectives that can be proposed for software in category B systems. These technical objectives are all derived from a unique primacy objective: safety integrity, i.e., the likelihood of software to achieve its safety functions under all stated conditions within a stated period of time.