{"title":"Sample implementation of the Littlewood holistic model for assessing software quality, safety and reliability","authors":"D. Herrmann","doi":"10.1109/RAMS.1998.653698","DOIUrl":null,"url":null,"abstract":"Software quality, safety and reliability metrics should be collected, integrated, and analyzed throughout the development lifecycle so that corrective and preventive action can be taken in a timely and cost effective manner. It is too late to wait until the testing phase to collect and assess software quality information, particularly for mission critical systems. It is inadequate and can be misleading to only use the results obtained from testing to make a software safety or reliability assessment. To remedy this situation a holistic model which captures, integrates and analyzes product, process, and people/resource (P/sup 3/R) metrics, as recommended by B. Littlewood (1993), is needed. This paper defines one such possible implementation.","PeriodicalId":275301,"journal":{"name":"Annual Reliability and Maintainability Symposium. 1998 Proceedings. International Symposium on Product Quality and Integrity","volume":"111 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"1998-01-19","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"7","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"Annual Reliability and Maintainability Symposium. 1998 Proceedings. International Symposium on Product Quality and Integrity","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/RAMS.1998.653698","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 7
Abstract
Software quality, safety and reliability metrics should be collected, integrated, and analyzed throughout the development lifecycle so that corrective and preventive action can be taken in a timely and cost effective manner. It is too late to wait until the testing phase to collect and assess software quality information, particularly for mission critical systems. It is inadequate and can be misleading to only use the results obtained from testing to make a software safety or reliability assessment. To remedy this situation a holistic model which captures, integrates and analyzes product, process, and people/resource (P/sup 3/R) metrics, as recommended by B. Littlewood (1993), is needed. This paper defines one such possible implementation.