{"title":"Software Error Data Collection and Analysis in Industry","authors":"M. Ohba","doi":"10.1109/ISSRE.1995.497666","DOIUrl":"https://doi.org/10.1109/ISSRE.1995.497666","url":null,"abstract":"","PeriodicalId":408394,"journal":{"name":"Proceedings of Sixth International Symposium on Software Reliability Engineering. ISSRE'95","volume":"2 2 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1995-10-24","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126436804","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":"A test coverage notion for logic programming","authors":"F. Belli, Oliver Jack","doi":"10.1109/ISSRE.1995.497651","DOIUrl":"https://doi.org/10.1109/ISSRE.1995.497651","url":null,"abstract":"Reliability determination for software is closely related to software testing. Testing delivers important data for software reliability models. Two important tasks of software testing are test case generation and determination of test coverage. Because of its declarative paradigm, all the well-known approaches to the above mentioned tasks are not applicable to logic programming. Implementation based testing is an approach to tackle the test problem for logic programming. We focus on test coverage aspects for logic programming. Analog to the coverage notion for conventional programming, e.g., path coverage on the control flow graph, we define a coverage measure on an abstract model of the logic program to be tested. Our abstract model is the set of goal-induced instances of program clauses. This is motivated by the computational model of resolution calculus for first-order predicate logic. Anti-unification is utilized to define the coverage measure via least upper bounds of this set. We give an algorithm for test cover determination which is prepared for coverage oriented test input generation, e.g., by declarative program instrumentation or non goal-oriented execution of logic programs using a fair interpreter. We describe syntactic and semantic aspects of our testing approach with respect to the properties of logic programming.","PeriodicalId":408394,"journal":{"name":"Proceedings of Sixth International Symposium on Software Reliability Engineering. ISSRE'95","volume":"87 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1995-10-24","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122826292","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}
M. Hlady, R. Kovacevic, J. J. Li, B. Pekilis, D. Prairie, T. Savor, R. Seviora, D. Simser, A. Vorobiev
{"title":"An approach to automatic detection of software failures","authors":"M. Hlady, R. Kovacevic, J. J. Li, B. Pekilis, D. Prairie, T. Savor, R. Seviora, D. Simser, A. Vorobiev","doi":"10.1109/ISSRE.1995.497672","DOIUrl":"https://doi.org/10.1109/ISSRE.1995.497672","url":null,"abstract":"The focus of this paper is on an approach to the automatic failure detection of reactive software systems called specification-based supervision. Assumed is that the software is specified in a formalism based on communicating extended finite state machines (CEFSMs). The major difficulty in supervising such systems is that the supervisor must account for all possible behaviors that are permissible under the non-determinism present in the specification. An approach to the automatic detection of failures based on the theory of beliefs is presented. This theory was developed to deal with the nondeterminism present in CEFSM based formalisms. The specification language SDL, standardized by the International Telecommunication Union, is used as a concrete example. In the theory of beliefs, each behavioral alternative is represented as a separate belief of one or more specification CEFSMs. Beliefs are combined into consistent belief sets that represent legitimate external behaviors. A consistent belief set representing a behavior that does not match the actually observed behavior is terminated. If all consistent belief sets have been terminated, the observed behavior is not legitimate and is reported as a failure of the target software system. A prototype implementation of a belief-based supervisor was developed. The implementation was used to monitor execution of a small telephone exchange. Both the supervisor and exchange were emulated on a workstation. Statistics characterizing the number of consistent belief sets are presented.","PeriodicalId":408394,"journal":{"name":"Proceedings of Sixth International Symposium on Software Reliability Engineering. ISSRE'95","volume":"142 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1995-10-24","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115970454","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":"An experiment in determining software reliability model applicability","authors":"A. Nikora, Michael R. Lyu","doi":"10.1109/ISSRE.1995.497671","DOIUrl":"https://doi.org/10.1109/ISSRE.1995.497671","url":null,"abstract":"Most reported experience with software reliability models is from a project's testing phases, during which researchers have little control over the failure data. Since failure data can be noisy and distorted, reported procedures for determining model applicability may be incomplete. To gain additional insight into this problem, we generated forty sets of data by drawing samples from two distributions, which were used as inputs to six different software reliability models. We used several different methods to analyze the applicability of the models. We expected that a model would perform best on the data sets created to comply with the model's assumptions, but initially found that this was not always the case. More detailed examination showed that a model using a data set created to satisfy its assumptions tended to have better prequential likelihood bias, and bias trend measures, although the Kolmogorov-Smirnov test might not be a reliable indicator of the best model. These results indicate that more than one measure should be used to determine model applicability, and that for greater accuracy they be evaluated in sequence rather than simultaneously.","PeriodicalId":408394,"journal":{"name":"Proceedings of Sixth International Symposium on Software Reliability Engineering. ISSRE'95","volume":"11 18 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1995-10-24","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116133351","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":"An assessment of software quality in a C++ environment","authors":"R. M. Szabo, T. Khoshgoftaar","doi":"10.1109/ISSRE.1995.497663","DOIUrl":"https://doi.org/10.1109/ISSRE.1995.497663","url":null,"abstract":"In this experience report, we discuss the application of a three group discriminant model to an object oriented software system. The model is used to classify software modules as high, medium, or low risk with respect to the number of faults. To our knowledge, this is among the first empirical validations of a true three group software quality model. Two models are presented. One model incorporates only traditional measures while the other model includes both traditional and object oriented measures. We show that for this system, the addition of the object oriented measures enhances the model by reducing the overall misclassification rate and significantly reducing the misclassification in the medium group.","PeriodicalId":408394,"journal":{"name":"Proceedings of Sixth International Symposium on Software Reliability Engineering. ISSRE'95","volume":"28 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1995-10-24","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126505877","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":"Dependability of safety-critical systems: contribution of the synchronous approach","authors":"D. Pérez","doi":"10.1109/ISSRE.1995.497670","DOIUrl":"https://doi.org/10.1109/ISSRE.1995.497670","url":null,"abstract":"In order to develop \"critical\" programmed protection systems, dedicated development tools are needed. The formalisms used should guarantee a high level of safety for the process being considered. The synchronous approach has numerous advantages which help it meet this target. This article presents the synchronous approach from an industrial point of view. This is the point of view behind the industrial development strategy for critical software within Schneider-Electric's Safety Electronics and Systems department. The article gives a historical outline and a simple definition of the synchronous approach, followed by a very simple example of an application which demonstrates the advantages of the synchronous approach. It does not give a detailed description of the techniques for proving operational safety, but rather aims to describe as simply as possible, the characteristics of the synchronous approach related to operational safety.","PeriodicalId":408394,"journal":{"name":"Proceedings of Sixth International Symposium on Software Reliability Engineering. ISSRE'95","volume":"15 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1995-10-24","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116745069","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":"An experience report on requirements reliability engineering using formal methods","authors":"David Hamilton, R. Covington, Alice T. Lee","doi":"10.1109/ISSRE.1995.497643","DOIUrl":"https://doi.org/10.1109/ISSRE.1995.497643","url":null,"abstract":"Studies show that early stages of the system development life cycle are especially prone to errors. Problems which originate in early stages can have a lasting influence on the reliability, safety, and cost of a system. The National Aeronautics and Space Administration (NASA) is investigating the use and effectiveness of Formal Methods (FM) in trial projects to improve the quality of software and system requirements. The study reports on the application of FM to the Failure Detection, Isolation, and Recovery (FDIR) system for the Space Station. Abstraction, type checking formal specification, and proof were used to assess the adequacy of several related views of the FDIR requirements. Results indicate that abstraction revealed underlying conceptual simplicity that was hard to recognize in the original description. Furthermore, the use of automated formal methods tools permitted rapid and comprehensive consistency checks which would have been impractical manually. We believe the analysis methodology outlined in the paper is a cost effective way to help ensure that requirements will be interpreted correctly by system designers.","PeriodicalId":408394,"journal":{"name":"Proceedings of Sixth International Symposium on Software Reliability Engineering. ISSRE'95","volume":"104 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1995-10-24","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124826036","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":"System testing with an AI planner","authors":"R. Mraz, A. Howe, A. Andrews, Li Li","doi":"10.1109/ISSRE.1995.497648","DOIUrl":"https://doi.org/10.1109/ISSRE.1995.497648","url":null,"abstract":"System testing of software with command language interfaces can be automated using grammar based test generation or through generating tests from an application domain specification. When viewing test case generation as constructing a sequence of commands to achieve a testing goal, AI planning systems show promise. We report on automated test generation with an AI planning system and compare results to tests generated by Sleuth, a tool for automated application domain testing.","PeriodicalId":408394,"journal":{"name":"Proceedings of Sixth International Symposium on Software Reliability Engineering. ISSRE'95","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1995-10-24","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128912785","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":"Test generation for Boolean expressions","authors":"A. Paradkar, K. Tai","doi":"10.1109/ISSRE.1995.497649","DOIUrl":"https://doi.org/10.1109/ISSRE.1995.497649","url":null,"abstract":"We propose a new strategy for generating test cases for Boolean expressions. In the past, we reported the BOR (Boolean Operator) strategy for generating test cases for predicates which are singular: which contain only one occurrence of each constituent Boolean variable. We also reported results of the empirical studies that were carried out to study the effectiveness of the strategy, but the BOR algorithm did not work well with non-singularities: multiple occurrences of constituent Boolean variables. The solution we propose for the problem is a combination of the original BOR strategy and the MI (Meaning Impact) strategy reported elsewhere. Our approach is to divide a Boolean expression into components that do not have common variables, apply the MI strategy to non-singular components, and the BOR strategy to singular components, and then apply the BOR strategy to combine the test sets generated for all component. Our empirical results indicate that our hybrid approach produces fewer tests for a Boolean expression than the MI strategy. The fault detection capability of our proposed approach has also been found to be comparable to that of the MI strategy. Our test generation strategy can be used to improve the reliability and safety of a program.","PeriodicalId":408394,"journal":{"name":"Proceedings of Sixth International Symposium on Software Reliability Engineering. ISSRE'95","volume":"142 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1995-10-24","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124527874","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":"Telecommunications network operations systems: experiences in software reliability engineering","authors":"D. Kropfl, W. K. Ehrlich","doi":"10.1109/ISSRE.1995.497676","DOIUrl":"https://doi.org/10.1109/ISSRE.1995.497676","url":null,"abstract":"Describes our practical experiences in applying software reliability engineering (SRE) technology to telecommunications network operations systems. These are real-time, high-availability systems used to provision, maintain and restore AT&T's backbone telecommunications transport network. In this paper, we describe how we used SRE to ensure the quality and high reliability of three such systems prior to production. Key steps in applying SRE are: deriving an operational profile, developing a simulator test environment, and executing load, stress and stability tests. To reduce test intervals and increase system reliability, we apply accelerated testing and experimental design. In addition, our SRE program also incorporates customer-focused techniques such as operational scenario testing.","PeriodicalId":408394,"journal":{"name":"Proceedings of Sixth International Symposium on Software Reliability Engineering. ISSRE'95","volume":"58 8","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1995-10-24","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"120886690","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}