{"title":"Extending fault trees with an AND-THEN gate","authors":"P. G. Wijayarathna, M. Maekawa","doi":"10.1109/ISSRE.2000.885879","DOIUrl":"https://doi.org/10.1109/ISSRE.2000.885879","url":null,"abstract":"Fault trees have been used for software safety analysis in various safety critical systems. The PRIORITY-AND gate was proposed because the conventional AND gate cannot be used to represent the sequential order of the events. The paper shows that even PRIORITY-AND gate is not expressive enough to represent the relative temporal order of the events precisely. We extend the fault trees with an AND-THEN gate that is the corresponding gate of the logical connective TAND. This increases the expressive power of the fault trees. The AND-THEN gate can represent relative temporal relations precisely.","PeriodicalId":322009,"journal":{"name":"Proceedings 11th International Symposium on Software Reliability Engineering. ISSRE 2000","volume":"209 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2000-10-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124705664","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":"Software reliability and maintenance concept used for automatic call distributor MEDIO ACD","authors":"M. Popovic, V. Kovacevic, M. Skrbic","doi":"10.1109/ISSRE.2000.885884","DOIUrl":"https://doi.org/10.1109/ISSRE.2000.885884","url":null,"abstract":"The authors present the software reliability and maintenance concept, which is used in the software development, testing, and maintenance process, for automatic call distributor MEDIO ACD. The concept has been successfully applied on systems, which are installed and fully operational in Moscow and Saint Petersburg, Russia. The authors concentrate on two main issues: (i) set of fault-tolerant mechanisms needed for the system exploitation (error logging, checkpoint-restart, overload protection and tandem configuration support); (ii) MEDIO ACD software maintenance concept, in which the quality of the new software update is predicted on the basis of the current update's metrics and quality, and the new update's metrics. This forecast aids software maintenance efficiency, and cost reduction.","PeriodicalId":322009,"journal":{"name":"Proceedings 11th International Symposium on Software Reliability Engineering. ISSRE 2000","volume":"56 6 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2000-10-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114531341","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":"Formal semantics of models for computational engineering: a case study on dynamic fault trees","authors":"D. Coppit, K. Sullivan, J. Dugan","doi":"10.1109/ISSRE.2000.885878","DOIUrl":"https://doi.org/10.1109/ISSRE.2000.885878","url":null,"abstract":"Computational modeling tools are critical to engineering. In the absence of a sufficiently complete, mathematically precise, abstract specification of the semantics of the modeling framework supported by such a tool, rigorous validation of the framework and of models built using it is impossible; there is no sound basis for program implementation, verification or documentation; the scientific foundation of the framework remains weak; and significant conceptual errors in framework definition and implementation are likely. Yet such specifications are rarely defined. We present an approach based on the use of formal specification and denotational semantics techniques from software engineering and programming language design. To illustrate the approach, we present elements of a formal semantics for a dynamic fault tree framework that promises to aid reliability analysis. No such specification of the meaning of dynamic fault trees has been defined previously. The approach revealed important shortcomings in the previous, informal definitions of the framework, and thus led to significant improvements, suggesting that formally specifying framework semantics is critical to effective framework design.","PeriodicalId":322009,"journal":{"name":"Proceedings 11th International Symposium on Software Reliability Engineering. ISSRE 2000","volume":"72 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2000-10-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126257106","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":"ATACOBOL-a COBOL test coverage analysis tool and its applications","authors":"Sam K. S. Sze, Michael R. Lyu","doi":"10.1109/ISSRE.2000.885883","DOIUrl":"https://doi.org/10.1109/ISSRE.2000.885883","url":null,"abstract":"A coverage testing tool ATACOBOL (Automatic Test Analysis for COBOL) that applies a data flow coverage technique is developed for software development on an IBM System/390 mainframe. We show that the data flow coverage criteria can identify possible problematic paths that map to the actual testing semantic required by Y2K compliance software testing. However, the mainframe environment lacks testing tools that equip the data flow coverage measure. Up to the current implementation, ATACOBOL is able to perform block coverage, decision coverage and all-uses measures. We extend the rules of data flow coverage criteria to adapt data structures that modern high-level languages usually employ.","PeriodicalId":322009,"journal":{"name":"Proceedings 11th International Symposium on Software Reliability Engineering. ISSRE 2000","volume":"10 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2000-10-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124523683","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":"Ranking software engineering measures related to reliability using expert opinion","authors":"Ming Li, C. Smidts, R. Brill","doi":"10.1109/ISSRE.2000.885876","DOIUrl":"https://doi.org/10.1109/ISSRE.2000.885876","url":null,"abstract":"The field of software engineering measurement appears to the unfamiliar eye as a chaotic environment lacking unifying principles and rigor. The number of software engineering measures developed over the years is stupefying and keeps increasing. Software engineering measures relate to multiple aspects of the software development process and product. Software development organizations typically select a small number of such software engineering measures to manage their development processes and products. The research presented in this paper is an attempt to help software development organizations identify the software engineering measures that are best predictors of software reliability. The research is based on the top 30 measures identified in an earlier study carried out by Lawrence Livermore National Laboratory (J.D. Lawrence et al., Technical Report UCRL-ID-136035, 1998). The set of ranking criteria was modified to fit the needs of the study. The score of each measure for each ranking criterion was elicited through expert opinion and then aggregated into a single score using multi-attribute utility theory. The basic aggregation scheme selected was a linear additive scheme. A comprehensive sensitivity analysis was carried out. The sensitivity analysis included variation of levels, variation of weights and variation of aggregation schemes.","PeriodicalId":322009,"journal":{"name":"Proceedings 11th International Symposium on Software Reliability Engineering. ISSRE 2000","volume":"91 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2000-10-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115078111","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":"On the repeatability of metric models and metrics across software builds","authors":"N. Schneidewind","doi":"10.1109/ISSRE.2000.885875","DOIUrl":"https://doi.org/10.1109/ISSRE.2000.885875","url":null,"abstract":"We have developed various software metrics models over the years: Boolean discriminate functions (BDFs); the Kolmogorov-Smirnov distance; derivative calculations for assessing achievable quality; a stopping rule; point and confidence interval estimates of quality; relative critical value deviation metrics; and nonlinear regression functions. We would like these models and metrics to be repeatable across the n builds of a software system. The advantage of repeatability is that models and metrics only need to be developed and validated once on build, and then applied n-1 times without modification to subsequent builds, with considerable savings in analysis and computational effort. In practical terms, this approach involves using the same model parameters that were validated and applying them unchanged on subsequent builds. The disadvantage is that the quality and metrics data of builds 2, ..., n, which varies across builds, is not utilized. We make a comparison of this approach with one that involves validating models and metrics on each build i and applying them only on build i+1, and then repeating the process. The advantage of this approach is that all available data are used in the models and analysis but at considerable cost in effort. We report on experiments involving large sets of discrepancy reports and metrics data on the Space Shuttle flight software, where we compare the predictive accuracy and effort of the two approaches for BDFs, critical values, derivative quality and inspection calculations, and the stopping rule.","PeriodicalId":322009,"journal":{"name":"Proceedings 11th International Symposium on Software Reliability Engineering. ISSRE 2000","volume":"10 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2000-10-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128733262","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":"Planner based error recovery testing","authors":"A. Andrews, M. Scheetz, E. Dahlman, A. Howe","doi":"10.1109/ISSRE.2000.885871","DOIUrl":"https://doi.org/10.1109/ISSRE.2000.885871","url":null,"abstract":"Error recovery testing is an important part of software testing, especially for safety-critical systems. We show how an AI planning system and the concepts of mutation testing can be combined to generate error recovery tests for software. We identify a set of mutation operations on the representation that the planner uses when generating test cases. These mutations cause error recovery test cases to be generated. The paper applies these concepts to the testing of a large tape storage system.","PeriodicalId":322009,"journal":{"name":"Proceedings 11th International Symposium on Software Reliability Engineering. ISSRE 2000","volume":"15 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2000-10-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126822269","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":"Quantitative software reliability modeling from testing to operation","authors":"Chin-Yu Huang, S. Kuo, J. Lo, Michael R. Lyu","doi":"10.1109/ISSRE.2000.885862","DOIUrl":"https://doi.org/10.1109/ISSRE.2000.885862","url":null,"abstract":"We first describe how several existing software reliability growth models based on nonhomogeneous Poisson processes (NHPPs) can be derived based on a unified theory for NHPP models. Under this general framework, we can verify existing NHPP models and derive new NHPP models. The approach covers a number of known models under different conditions. Based on these approaches, we show a method of estimating and computing software reliability growth during the operational phase. We can use this method to describe the transitions from the testing phase to operational phase. That is, we propose a method of predicting the fault detection rate to reflect changes in the user's operational environments. The proposed method offers a quantitative analysis on software failure behavior in field operation and provides useful feedback information to the development process.","PeriodicalId":322009,"journal":{"name":"Proceedings 11th International Symposium on Software Reliability Engineering. ISSRE 2000","volume":"73 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2000-10-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"123153642","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":"Software Black Box: an alternative mechanism for failure analysis","authors":"Sebastian G. Elbaum, J. Munson","doi":"10.1109/ISSRE.2000.885887","DOIUrl":"https://doi.org/10.1109/ISSRE.2000.885887","url":null,"abstract":"Learning from software failures is an essential step towards the development of more reliable software systems and processes. However, as more intricate software systems are developed, determining the nature and causes of a software failure becomes a great challenge. Although many existing techniques can help in understanding the nature of the failure, they are limited in some of the following aspects. First, they work only within controlled environments. Second, they have a major impact on the target system behavior. Third, they assume that a failure can be reproduced. Fourth, they lack enough support to carry out a structured failure analysis. The authors present the Software Black Box (SBB) as an alternative mechanism for failure investigation. The SBB is different from its predecessors in that it was specifically designed to be embedded in a target system and assist in the investigation of failures by reconstructing the events that lead to the failure. The SBB architecture is discussed, and a set of failure scenarios that reveal the SBB potential in assisting failure investigation is presented.","PeriodicalId":322009,"journal":{"name":"Proceedings 11th International Symposium on Software Reliability Engineering. ISSRE 2000","volume":"78 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2000-10-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125009414","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":"Structural testing of Web applications","authors":"Chien-Hung Liu, D. Kung, P. Hsia, Chih-Tung Hsu","doi":"10.1109/ISSRE.2000.885863","DOIUrl":"https://doi.org/10.1109/ISSRE.2000.885863","url":null,"abstract":"In recent years, Web applications have become prevalent around the world. Many companies have developed or integrated their mission-critical applications using Web technologies. As Web applications become more complex, testing Web applications becomes crucial. We extend data flow testing techniques to Web applications. Several data flow issues for analyzing HTML and eXtensible Markup Language (XML) documents in Web applications are discussed. An approach to supporting data flow testing for Web applications is presented. In our approach, the structural test artifacts of a Web application are captured in a Web Application Test Model (WATM) where each component of the Web application is treated as an object. The elements of an HTML or XML document are considered as structured variables within an object. Data flow test cases for Web applications are derived from flow graphs in five levels according to the types of definition-use chains for the variables of interest.","PeriodicalId":322009,"journal":{"name":"Proceedings 11th International Symposium on Software Reliability Engineering. ISSRE 2000","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2000-10-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"134157582","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}