{"title":"When to stop testing and start using software?","authors":"A. Goel, K. Okumoto","doi":"10.1145/800003.807921","DOIUrl":"https://doi.org/10.1145/800003.807921","url":null,"abstract":"During the last decade, numerous studies have been undertaken to quantify the failure process of large scale software systems. (see for example, references 1-12.) An important objective of these studies is to predict software performance and use the information for decision making. An important decision of practical concern is the determination of the amount of time that should be spent in testing. This decision of course will depend on the model used for describing the failure phenomenon and the criterion used for determining system readiness.\u0000 In this paper we present a cost model based on the time dependent fault detection rate model of Goel and Okumoto (4,5) and describe a policy that yields the optimal value of test time T.","PeriodicalId":262059,"journal":{"name":"Measurement and evaluation of software quality","volume":"60 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1981-04-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121489880","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"The application development process: What's wrong with it?","authors":"J. Crowley","doi":"10.1145/800003.807927","DOIUrl":"https://doi.org/10.1145/800003.807927","url":null,"abstract":"This paper will examine the process used in the development of computer applications. The claim is made that the current methodology has serious deficiencies, but that a software development approach is becoming available to help address these problems.","PeriodicalId":262059,"journal":{"name":"Measurement and evaluation of software quality","volume":"4 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1981-04-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116953813","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Producers and consumers views of software quality (Panel Session)","authors":"P. Gross","doi":"10.1145/1010627.807910","DOIUrl":"https://doi.org/10.1145/1010627.807910","url":null,"abstract":"At this very ACM workshop/symposium indicates, software quality is of great concern to both producers and users of software. It should be obvious to those who have attended the earlier sessions today and to those who will attend the sessions tomorrow that quality is something that cannot be tested into a system or added to a system. It must be integral from the start of the definition of the system's requirements through each phase of analysis, design, implementation, integration, testing, and installation.\u0000 Software quality implies an engineering type approach to the development of software. It implies the use of a disciplined development environment, and the use of tools and techniques to provide assurances throughout the software development process that both the software and its baseline specifications are complete, consistent, and traceable from one to another.","PeriodicalId":262059,"journal":{"name":"Measurement and evaluation of software quality","volume":"21 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1981-04-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132051771","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Predicting numbers of errors using software science","authors":"Linda M. Ottenstein","doi":"10.1145/800003.807924","DOIUrl":"https://doi.org/10.1145/800003.807924","url":null,"abstract":"An earlier paper presented a model based on software science metrics to give quantitative estimate of the number of bugs in a programming project at the time validation of the project begins. In this paper, we report the results from an attempt to expand the model to estimate the total number of bugs to expect during the total project development. This new hypothesis has been tested using the data currently available in the literature along with data from student projects. The model fits the published data reasonably well, however, the results obtained using the student data are not conclusive.","PeriodicalId":262059,"journal":{"name":"Measurement and evaluation of software quality","volume":"31 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"134549366","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}