Proceedings The Eighth International Symposium on Software Reliability Engineering最新文献_第2页

What do the software reliability growth model parameters represent? 软件可靠性增长模型参数代表什么?

Proceedings The Eighth International Symposium on Software Reliability Engineering Pub Date : 1997-11-02 DOI: 10.1109/ISSRE.1997.630857

Y. Malaiya, J. Denton

{"title":"What do the software reliability growth model parameters represent?","authors":"Y. Malaiya, J. Denton","doi":"10.1109/ISSRE.1997.630857","DOIUrl":"https://doi.org/10.1109/ISSRE.1997.630857","url":null,"abstract":"Here we investigate the underlying basis connecting the software reliability growth models to the software testing and debugging process. This is important for several reasons. First, if the parameters have an interpretation, then they constitute a metric for the software test process and the software under test. Secondly, it may be possible to estimate the parameters even before testing begins. These a priori values can serve as a check for the values computed at the beginning of testing, when the test-data is dominated by short term noise. They can also serve as initial estimates when iterative computations are used. Among the two-parameter models, the exponential model is characterized by its simplicity. Both its parameters have a simple interpretation. However, in some studies it has been found that the logarithmic Poisson model has superior predictive capability. Here we present a new interpretation for the logarithmic model parameters. The problem of a priori parameter estimation is considered using actual data available. Use of the results obtained is illustrated using examples. Variability of the parameters with the testing process is examined.","PeriodicalId":170184,"journal":{"name":"Proceedings The Eighth International Symposium on Software Reliability Engineering","volume":"5 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1997-11-02","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121057831","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}

引用次数: 47

A top-down approach to high-consequence fault analysis for software systems 软件系统高后果故障分析的自顶向下方法

Proceedings The Eighth International Symposium on Software Reliability Engineering Pub Date : 1997-11-02 DOI: 10.1109/ISSRE.1997.630873

E. Fronczak

{"title":"A top-down approach to high-consequence fault analysis for software systems","authors":"E. Fronczak","doi":"10.1109/ISSRE.1997.630873","DOIUrl":"https://doi.org/10.1109/ISSRE.1997.630873","url":null,"abstract":"Summary form only given, as follows. Even if software code is fault-free, hardware failures can alter values in memory, possibly where the code itself is stored, causing a computer system to reach an unacceptable state. Microprocessor systems are used to perform many safety and security functions where a design goal is to eliminate single-point failures such as these. One design approach is to use multiple processors, compare the outputs, and assume a failure has occurred if the outputs don't agree. In systems where the design is constrained to a single processor, however, analytical methods are needed to identify potential single-point failures at the bit level so that an effective fault-tolerant strategy can be employed. This paper describes a top-down methodology, based upon fault tree analysis, that has been used to identify potential high-consequence faults in microprocessor-based systems. The key to making the fault tree analysis tractable is to effectively incorporate appropriate design features such as software path control and checksums so that complicated branches of the fault tree can be terminated early. The analysis uses simplified software flow diagrams depicting relevant code elements. Pertinent sections of machine language are then examined to identify suspect hardware. A comparison of this methodology with approaches based upon failure modes and effects analysis (FMEA) is made. The methodology is demonstrated through a simple example. Use of fault trees to show that software code is free of safety or security faults is also demonstrated.","PeriodicalId":170184,"journal":{"name":"Proceedings The Eighth International Symposium on Software Reliability Engineering","volume":"10 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1997-11-02","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121428324","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}

引用次数: 8

Building software quality classification trees: approach, experimentation, evaluation 构建软件质量分类树:方法、实验、评估

Proceedings The Eighth International Symposium on Software Reliability Engineering Pub Date : 1997-11-02 DOI: 10.1109/ISSRE.1997.630869

R. Takahashi, Y. Muraoka, Yukihiro Nakamura

{"title":"Building software quality classification trees: approach, experimentation, evaluation","authors":"R. Takahashi, Y. Muraoka, Yukihiro Nakamura","doi":"10.1109/ISSRE.1997.630869","DOIUrl":"https://doi.org/10.1109/ISSRE.1997.630869","url":null,"abstract":"A methodology for generating an optimum software quality classification tree using software complexity metrics to discriminate between high-quality modules and low-quality modules is proposed. The process of tree generation is an application of the AIC (Akaike Information Criterion) procedures to the binomial distribution. AIC procedures are based on maximum likelihood estimation and the least number of complexity metrics. It is an improvement of the software quality classification tree generation method proposed by Porter and Selby (1990) from the viewpoint that the complexity metrics are minimized. The problems of their method are that the software quality prediction model is unstable because it reflects observational errors in real data too much and there is no objective criterion for determining whether the discrimination is appropriate or not at a deep nesting level of the classification tree when the number of sample modules gets smaller. To solve these problems a new metric is introduced and its validity is theoretically and experimentally verified. In our examples, complexity metrics written in C language, such as lines of source code, Halstead's (1977) software science, McCabe's (976) cyclomatic number, Henry and Kafura's (1981) fan-in/out and Howatt and Baker's (1989) scope number, are investigated. Our experiments with a medium-sized piece of software (85 thousand lines of source code; 562 samples) show that the software quality classification tree generated by our new metric identifies the target class of the observed modules more efficiently using the minimum number of complexity metrics without any significant decrease of the correct classification ratio (76%->72%) than the conventional classification tree.","PeriodicalId":170184,"journal":{"name":"Proceedings The Eighth International Symposium on Software Reliability Engineering","volume":"12 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1997-11-02","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129543675","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}

引用次数: 30

Successful application of software reliability engineering for the NASA Space Shuttle 软件可靠性工程在NASA航天飞机上的成功应用

Proceedings The Eighth International Symposium on Software Reliability Engineering Pub Date : 1997-11-02 DOI: 10.1109/ISSRE.1997.630854

T. Keller, N. Schneidewind

{"title":"Successful application of software reliability engineering for the NASA Space Shuttle","authors":"T. Keller, N. Schneidewind","doi":"10.1109/ISSRE.1997.630854","DOIUrl":"https://doi.org/10.1109/ISSRE.1997.630854","url":null,"abstract":"Summary form only given. The Space Shuttle Primary Avionics Software Subsystem (PASS) represents a successful integration of many of the computer industry's most advanced software engineering practices and approaches. Beginning in the late 1970's this software development and maintenance project has evolved one of the world's most mature software processes applying the principles of the highest levels of the Software Engineering Institute's Capability Maturity Model and ISO 9001 Standards. This software process, considered to be a \"best practice\" by many software industry organizations includes state-of-the-practice software reliability engineering (SRE) methodologies. Life-critical PASS produced by this process is recognized to be among the highest quality and highest reliability software in operation in the world. Using this application, we show how SRE can be applied to: interpret software reliability predictions, support verification and validation of the software, assess the risk of deploying the software, predict the reliability of the software, develop test strategies to bring the software into conformance with reliability specifications, and make reliability decisions regarding deployment of the software.","PeriodicalId":170184,"journal":{"name":"Proceedings The Eighth International Symposium on Software Reliability Engineering","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1997-11-02","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129102604","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}

引用次数: 37

Quantitative evaluation of capture-recapture models to control software inspections 定量评估捕获-再捕获模型以控制软件检查

Proceedings The Eighth International Symposium on Software Reliability Engineering Pub Date : 1997-11-02 DOI: 10.1109/ISSRE.1997.630870

L. Briand, K. Emam, B. Freimut, O. Laitenberger

{"title":"Quantitative evaluation of capture-recapture models to control software inspections","authors":"L. Briand, K. Emam, B. Freimut, O. Laitenberger","doi":"10.1109/ISSRE.1997.630870","DOIUrl":"https://doi.org/10.1109/ISSRE.1997.630870","url":null,"abstract":"An important requirement to control the inspection of software artifacts is to be able to decide, based on objective information, whether inspection can stop or whether it should continue to achieve a suitable level of artifact quality. Several studies in software engineering have considered the use of capture-recapture models to predict the number of remaining defects in an inspected document as a decision criterion about reinspection. However, no study on software engineering artifacts compares the actual number of remaining defects to the one predicted by a capture-recapture model. Simulations have been performed but no definite conclusions can be drawn regarding the degree of accuracy of such models under realistic inspection conditions, and the factors affecting this accuracy. Furthermore, none of these studies performed an exhaustive comparison of existing models. In this study, we focus on traditional inspections and estimate, based on actual inspection data, the degree of accuracy of all relevant, state-of-the-art, capture-recapture models for which statistical estimators exist. We compare the various models' accuracies and look at the impact of the number of inspectors on these accuracies. Results show that model accuracies are strongly affected by the number of inspectors and, therefore, one must consider this factor before using capture-recapture models. When the number of inspectors is below 4, no model is sufficiently accurate and underestimation may be substantial. In addition, some models perform better than others in a large number of conditions and plausible reasons are discussed. Based on our analyses, we recommend using a model taking into account different probabilities of detecting defects and a Jacknife estimator.","PeriodicalId":170184,"journal":{"name":"Proceedings The Eighth International Symposium on Software Reliability Engineering","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1997-11-02","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132415851","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}

引用次数: 62

A non-parametric approach to software reliability prediction 软件可靠性预测的非参数方法

Proceedings The Eighth International Symposium on Software Reliability Engineering Pub Date : 1997-11-02 DOI: 10.1109/ISSRE.1997.630885

M. Barghout, B. Littlewood, A. Abdel-Ghaly

引用次数: 11

Optimization of reliability allocation and testing schedule for software systems 软件系统可靠性分配和测试计划的优化

Proceedings The Eighth International Symposium on Software Reliability Engineering Pub Date : 1997-11-02 DOI: 10.1109/ISSRE.1997.630881

Michael R. Lyu, S. Rangarajan, A. Moorsel

{"title":"Optimization of reliability allocation and testing schedule for software systems","authors":"Michael R. Lyu, S. Rangarajan, A. Moorsel","doi":"10.1109/ISSRE.1997.630881","DOIUrl":"https://doi.org/10.1109/ISSRE.1997.630881","url":null,"abstract":"To ensure an overall reliability of an integrated software system, software components of the system have to meet certain reliability requirements, subject to some testing schedule and resource constraints. The system testing activity can be formulated as a combinatorial optimization problem with known cost, reliability, effort and other attributes of the system components. In this paper, we consider the software component reliability allocation problem for a system with multiple applications. The failure rate of components used to build the applications are related to the testing cost through various types of reliability growth curves. We achieve closed-form solutions to problems where there is one single application in the system. Analytical solutions are not readily available when there are multiple applications; however, numerical solutions can be obtained using a nonlinear programming tool. To ease the specification of the optimization problem, we develop a GUI front-end to existing mathematical software. We present a systematic outline of the problem formulation and solution, and apply this to an example of a telecommunication software system.","PeriodicalId":170184,"journal":{"name":"Proceedings The Eighth International Symposium on Software Reliability Engineering","volume":"167 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1997-11-02","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116598449","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}

引用次数: 21

Use of software triggers to evaluate software process effectiveness and capture customer usage profiles 使用软件触发器来评估软件过程的有效性并获取客户使用概况

Proceedings The Eighth International Symposium on Software Reliability Engineering Pub Date : 1997-11-02 DOI: 10.1109/ISSRE.1997.630874

Kathryn Bassin, P. Santhanam

{"title":"Use of software triggers to evaluate software process effectiveness and capture customer usage profiles","authors":"Kathryn Bassin, P. Santhanam","doi":"10.1109/ISSRE.1997.630874","DOIUrl":"https://doi.org/10.1109/ISSRE.1997.630874","url":null,"abstract":"Summary form only given, as follows. We have analyzed fault data comprising nearly 30,000 records (including in-process and field data) from two real products A and B over multiple releases, using orthogonal defect classification (ODC). We exploit the information capture by ODC triggers to evaluate the development activities, and identify specific actions for improvement in development. We illustrate the use of triggers to capture customer usage in a way that is directly meaningful to product development and show: (i) the complete trigger profiles by the development activity for two releases of product A, and evaluate the effectiveness of product development activities; (ii) how systematically the appropriate trigger distribution during the development activities can be made to approach the trigger distribution in the field over six releases, as validated by /spl chi//sup 2/ tests; (iii) study the field defect trigger distributions for product A over three releases, and demonstrate the consistency of the profile over multiple releases and discuss the origin of differences; and (iv) compare the field trigger profiles of products A and B and discuss the differences in their customer usage and environment. This is the most comprehensive use of ODC triggers in development and field data reported to date.","PeriodicalId":170184,"journal":{"name":"Proceedings The Eighth International Symposium on Software Reliability Engineering","volume":"104 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1997-11-02","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114319857","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}

引用次数: 18

An approach to measuring and assessing dependability for critical software systems 一种测量和评估关键软件系统可靠性的方法

Proceedings The Eighth International Symposium on Software Reliability Engineering Pub Date : 1997-11-02 DOI: 10.1109/ISSRE.1997.630864

D. Tang, H. Hecht

{"title":"An approach to measuring and assessing dependability for critical software systems","authors":"D. Tang, H. Hecht","doi":"10.1109/ISSRE.1997.630864","DOIUrl":"https://doi.org/10.1109/ISSRE.1997.630864","url":null,"abstract":"Traditional software testing methods combined with probabilistic models cannot measure and assess dependability for software that requires very high reliability (failure rate<10/sup -6//hour) and availability (>0.999999). This paper proposes a novel approach, drawing on findings and methods that have been described individually but have never been combined, applied in the late testing phase or early operational phase, to quantify dependability for a category of critical software with such high requirements. The concepts that are integrated are: operational profile, rare conditions, importance sampling, stress testing, and measurement-based dependability evaluation. In the approach, importance sampling is applied on the operational profile to guide the testing of critical operations of the software, thereby accelerating the occurrence of rare conditions which have been shown to be a leading cause of failure in critical systems. The failure rates measured in the testing are then transformed to those that would occur in the normal operation by the likelihood ratio function of the importance sampling theory, and finally dependability for the tested software system is evaluated by using measurement-based dependability modeling techniques. When the acceleration factor is large (over 100), which is typical for a category of software of interest, it is possible to quantify a very high reliability or availability in a reasonable test duration. Some feasible methods to implement the approach are discussed based on real data.","PeriodicalId":170184,"journal":{"name":"Proceedings The Eighth International Symposium on Software Reliability Engineering","volume":"8 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1997-11-02","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127124615","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}

引用次数: 16

On the estimation of reliability of a software system using reliabilities of its components 用软件系统组件的可靠性来估计软件系统的可靠性

Proceedings The Eighth International Symposium on Software Reliability Engineering Pub Date : 1997-11-02 DOI: 10.1109/ISSRE.1997.630860

Saileshwar Krishnamurthy, A. Mathur

{"title":"On the estimation of reliability of a software system using reliabilities of its components","authors":"Saileshwar Krishnamurthy, A. Mathur","doi":"10.1109/ISSRE.1997.630860","DOIUrl":"https://doi.org/10.1109/ISSRE.1997.630860","url":null,"abstract":"We report an experiment to evaluate a method, known as component based reliability estimation (CBRE), for the estimation of reliability of a software system using reliabilities of its components. CBRE involves computing path reliability estimates based on the sequence of components executed for each test input. Path reliability estimates are averaged over all test runs to obtain an estimate of the system reliability. In the experiment reported, three components of a Unix utility were seeded with errors and the reliability of each component was measured. The faulty components were then introduced systematically into the utility, in various combinations, to produce several faulty versions of the utility. For each faulty version, test cases were drawn from an operational profile to measure the component-based reliability. The true reliability of the faulty version was estimated using the frequency count approach. The goodness of CBRE was assessed in terms of the accuracy and efficiency of the estimates with respect to the true reliability. Results from this experiment suggest that CBRE yields reasonably accurate results at an efficient rate. However, the accuracy and efficiency of CBRE is sensitive to the dependency among successive calls to a component.","PeriodicalId":170184,"journal":{"name":"Proceedings The Eighth International Symposium on Software Reliability Engineering","volume":"55 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1997-11-02","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122125689","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}

引用次数: 216