Pub Date : 2013-12-19DOI: 10.1109/ISSREW.2013.6688887
G. Walia, Jeffrey C. Carver
Problem Definition: To help ensure high-quality software artifacts, researchers and practitioners have developed various techniques for identifying and repairing problems early in the software lifecycle (e.g., requirements and design documents). Most of these techniques are fault-based, and have been empirically validated. However, results show that even when developers faithfully apply these techniques, they are not able to identify all types of problems and that 40-50% of effort is spent on fixing these early problems later in the development process. The studies have revealed the inadequacy of fault-based approaches, which treats the symptoms of software defects, not their underlying causes. Prior research that only analyzed a sample of faults to determine their causes and suggest process improvements (e.g., RCA, ODC) overlooked many errors due to a lack of underlying cognitive theory. Proposed Solution: Our solution applies results from human error research to address the defects made during development. Human error research focuses on the psychological processes that produce errors in human behavior. The process of applying human error research to software development begins by collecting data about errors, finding common failures, and interpreting those errors in light of human information processing limitations and known error patterns. A taxonomy of errors can be used to make developers more effective during the software inspection process to catch costly mistakes early.
{"title":"Using error information to improve software quality","authors":"G. Walia, Jeffrey C. Carver","doi":"10.1109/ISSREW.2013.6688887","DOIUrl":"https://doi.org/10.1109/ISSREW.2013.6688887","url":null,"abstract":"Problem Definition: To help ensure high-quality software artifacts, researchers and practitioners have developed various techniques for identifying and repairing problems early in the software lifecycle (e.g., requirements and design documents). Most of these techniques are fault-based, and have been empirically validated. However, results show that even when developers faithfully apply these techniques, they are not able to identify all types of problems and that 40-50% of effort is spent on fixing these early problems later in the development process. The studies have revealed the inadequacy of fault-based approaches, which treats the symptoms of software defects, not their underlying causes. Prior research that only analyzed a sample of faults to determine their causes and suggest process improvements (e.g., RCA, ODC) overlooked many errors due to a lack of underlying cognitive theory. Proposed Solution: Our solution applies results from human error research to address the defects made during development. Human error research focuses on the psychological processes that produce errors in human behavior. The process of applying human error research to software development begins by collecting data about errors, finding common failures, and interpreting those errors in light of human information processing limitations and known error patterns. A taxonomy of errors can be used to make developers more effective during the software inspection process to catch costly mistakes early.","PeriodicalId":332420,"journal":{"name":"2013 IEEE International Symposium on Software Reliability Engineering Workshops (ISSREW)","volume":"79 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2013-12-19","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125021460","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}
Pub Date : 2013-12-19DOI: 10.1109/ISSREW.2013.6688907
H. Okamura, C. Luo, T. Dohi
This paper considers the estimation algorithm for response time distribution of a server application under the environment where software aging occurs. We develop the continuous-time Markov chain (CTMC) model to represent the degradation level of server and then show that the response time distribution can be represented by a Markov-modulated compound Poisson process (MMCPP). The estimation algorithm for the response time distribution is given by the EM algorithm for MMCPP. In a numerical example, we demonstrate the response time estimation for the experimental data of MySQL server.
{"title":"Estimating response time distribution of server application in software aging phenomenon","authors":"H. Okamura, C. Luo, T. Dohi","doi":"10.1109/ISSREW.2013.6688907","DOIUrl":"https://doi.org/10.1109/ISSREW.2013.6688907","url":null,"abstract":"This paper considers the estimation algorithm for response time distribution of a server application under the environment where software aging occurs. We develop the continuous-time Markov chain (CTMC) model to represent the degradation level of server and then show that the response time distribution can be represented by a Markov-modulated compound Poisson process (MMCPP). The estimation algorithm for the response time distribution is given by the EM algorithm for MMCPP. In a numerical example, we demonstrate the response time estimation for the experimental data of MySQL server.","PeriodicalId":332420,"journal":{"name":"2013 IEEE International Symposium on Software Reliability Engineering Workshops (ISSREW)","volume":"15 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2013-12-19","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115350785","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}
Pub Date : 2013-12-19DOI: 10.1109/ISSREW.2013.6688891
Steven Davies, M. Roper
Many approaches have been proposed to address the problem of bug localisation - taking a bug report and recommending to developers the possible locations of the bug in the project. However, these can often require significant up-front work from developers, and are not widely adopted. Furthermore, those techniques which do not require this up-front investment are often far from accurate, and do not take advantage of all of the information that they could. We propose a technique for combining information from multiple, novel sources of information about a project and a bug, and use this to recommend bug locations to developers. We also identify how this technique could be used to create a low-effort tool for bug localisation, with the aim of increasing developer adoption. We evaluate the technique on 1143 bugs in three open-source projects, and find that it can be used to increase the number of bugs where the first relevant method recommended to developers is the top result from 98 to 132 and in the top-10 from 271 to 322.
{"title":"Bug localisation through diverse sources of information","authors":"Steven Davies, M. Roper","doi":"10.1109/ISSREW.2013.6688891","DOIUrl":"https://doi.org/10.1109/ISSREW.2013.6688891","url":null,"abstract":"Many approaches have been proposed to address the problem of bug localisation - taking a bug report and recommending to developers the possible locations of the bug in the project. However, these can often require significant up-front work from developers, and are not widely adopted. Furthermore, those techniques which do not require this up-front investment are often far from accurate, and do not take advantage of all of the information that they could. We propose a technique for combining information from multiple, novel sources of information about a project and a bug, and use this to recommend bug locations to developers. We also identify how this technique could be used to create a low-effort tool for bug localisation, with the aim of increasing developer adoption. We evaluate the technique on 1143 bugs in three open-source projects, and find that it can be used to increase the number of bugs where the first relevant method recommended to developers is the top result from 98 to 132 and in the top-10 from 271 to 322.","PeriodicalId":332420,"journal":{"name":"2013 IEEE International Symposium on Software Reliability Engineering Workshops (ISSREW)","volume":"16 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2013-12-19","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114222777","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}
Pub Date : 2013-12-19DOI: 10.1109/ISSREW.2013.6688901
R. Adler, S. Kemmann, D. D. M. C. Filho, José Augusto Oliveira Neto
Argumentation-based safety assurance is a promising approach for the development of safe software-intensive medical devices. However, one challenge is safety assessment by an independent authority. This article presents an approach that enables argumentation-based safety development on the one hand, while providing means for assessing the product's safety afterwards on the other hand. We combine a generic safety case with an engineering model, which results in specific quality questions for assessors and provides a generic argumentation structure for manufacturers.
{"title":"Safety assessment of software-intensive medical devices: Introducing a safety quality model approach","authors":"R. Adler, S. Kemmann, D. D. M. C. Filho, José Augusto Oliveira Neto","doi":"10.1109/ISSREW.2013.6688901","DOIUrl":"https://doi.org/10.1109/ISSREW.2013.6688901","url":null,"abstract":"Argumentation-based safety assurance is a promising approach for the development of safe software-intensive medical devices. However, one challenge is safety assessment by an independent authority. This article presents an approach that enables argumentation-based safety development on the one hand, while providing means for assessing the product's safety afterwards on the other hand. We combine a generic safety case with an engineering model, which results in specific quality questions for assessors and provides a generic argumentation structure for manufacturers.","PeriodicalId":332420,"journal":{"name":"2013 IEEE International Symposium on Software Reliability Engineering Workshops (ISSREW)","volume":"44 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2013-12-19","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115625849","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}
Pub Date : 2013-12-19DOI: 10.1109/ISSREW.2013.6688883
Sandipan Dey, Kandathil K. Jacob, J. López, Kishor S. Trivedi
With ever-growing complexity of computer systems, proactive failure management is turning out to be an effective and essential approach for enhancing availability. Several techniques have been proposed to develop failure prediction models [3]. In this paper we have concentrated on the process to build up a failure prediction model based on the failure reports (service ticket logs) from hardware storage devices.
{"title":"Failure data analytics to build failure prediction mechanisms","authors":"Sandipan Dey, Kandathil K. Jacob, J. López, Kishor S. Trivedi","doi":"10.1109/ISSREW.2013.6688883","DOIUrl":"https://doi.org/10.1109/ISSREW.2013.6688883","url":null,"abstract":"With ever-growing complexity of computer systems, proactive failure management is turning out to be an effective and essential approach for enhancing availability. Several techniques have been proposed to develop failure prediction models [3]. In this paper we have concentrated on the process to build up a failure prediction model based on the failure reports (service ticket logs) from hardware storage devices.","PeriodicalId":332420,"journal":{"name":"2013 IEEE International Symposium on Software Reliability Engineering Workshops (ISSREW)","volume":"62 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2013-12-19","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"123357573","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}
Pub Date : 2013-12-19DOI: 10.1109/ISSREW.2013.6688900
Y. Sakai, S. Shirasaka, Y. Nishi
It is difficult to assess the risk of software-intensive medical devices. An extended notation of FTA recognizes the risk class before and after the risk control measure and the software in the system affects the top event of FTA.
{"title":"An extended notation of FTA for risk assessment of software-intensive medical devices.: Recognition of the risk class before and after the risk control measure","authors":"Y. Sakai, S. Shirasaka, Y. Nishi","doi":"10.1109/ISSREW.2013.6688900","DOIUrl":"https://doi.org/10.1109/ISSREW.2013.6688900","url":null,"abstract":"It is difficult to assess the risk of software-intensive medical devices. An extended notation of FTA recognizes the risk class before and after the risk control measure and the software in the system affects the top event of FTA.","PeriodicalId":332420,"journal":{"name":"2013 IEEE International Symposium on Software Reliability Engineering Workshops (ISSREW)","volume":"23 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2013-12-19","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125055860","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}
Pub Date : 2013-12-19DOI: 10.1109/ISSREW.2013.6688870
Hrishikesh Dewan, Raksha B. Nayak
Summary form only given. Numerical Optimization is an integral part of most engineering, scientific work and is a computationally intensive job. Most optimization frameworks developed so far executes numerical algorithms in a single processor or in a dedicated cluster of machines. A single system based optimizer is plagued by the resources and a dedicated high performance computational cluster is extremely cost prohibitive. Further with the increase in dimensions of the decision / objective space variables / functions, it is difficult to foresee and plan a computation cluster ahead of time. A peer-to-peer system provides a viable alternative to this problem. A peer-to-peer (P2P) system has no central co-ordination and is generally a loose union of a set of non-dedicated machines glued via a logical network for fast dissemination of information. The advantage to cost-effectiveness and elasticity with a P2P system however comes with a price. A P2P system lacks trust and malicious nodes can jeopardize the application to a significant extent. The nodes/communication links are prone to failure of various types such a fail-stop, omission, timing (value) and response (value). As a result there is no guarantee of completion of an optimization job. Furthermore, if a certain section of nodes are susceptible to Byzantine faults, it could lead to a misleading front in the objective space where there is absolute un-certainty of reaching a global minimum. Redundancy, failure detection and recovery are an essential part in the design of such a system. In essence, since in a large scale distributed system “Failure is not an exception but a norm”, dependability in design of the system is not just a choice but an absolute requirement. In this presentation, we would like to put forth the challenges of designing such a P2P system together with the algorithms that has been used, designed and developed by us in creating a P2P optimization framework. The presentation is divided into three sections: firstly in identifying the challenges, secondly, the solutions to mitigate the challenges and thirdly the results that we have obtained by applying the solutions to the problem sets.
{"title":"Design of a dependable peer-to-peer system for numerical optimization","authors":"Hrishikesh Dewan, Raksha B. Nayak","doi":"10.1109/ISSREW.2013.6688870","DOIUrl":"https://doi.org/10.1109/ISSREW.2013.6688870","url":null,"abstract":"Summary form only given. Numerical Optimization is an integral part of most engineering, scientific work and is a computationally intensive job. Most optimization frameworks developed so far executes numerical algorithms in a single processor or in a dedicated cluster of machines. A single system based optimizer is plagued by the resources and a dedicated high performance computational cluster is extremely cost prohibitive. Further with the increase in dimensions of the decision / objective space variables / functions, it is difficult to foresee and plan a computation cluster ahead of time. A peer-to-peer system provides a viable alternative to this problem. A peer-to-peer (P2P) system has no central co-ordination and is generally a loose union of a set of non-dedicated machines glued via a logical network for fast dissemination of information. The advantage to cost-effectiveness and elasticity with a P2P system however comes with a price. A P2P system lacks trust and malicious nodes can jeopardize the application to a significant extent. The nodes/communication links are prone to failure of various types such a fail-stop, omission, timing (value) and response (value). As a result there is no guarantee of completion of an optimization job. Furthermore, if a certain section of nodes are susceptible to Byzantine faults, it could lead to a misleading front in the objective space where there is absolute un-certainty of reaching a global minimum. Redundancy, failure detection and recovery are an essential part in the design of such a system. In essence, since in a large scale distributed system “Failure is not an exception but a norm”, dependability in design of the system is not just a choice but an absolute requirement. In this presentation, we would like to put forth the challenges of designing such a P2P system together with the algorithms that has been used, designed and developed by us in creating a P2P optimization framework. The presentation is divided into three sections: firstly in identifying the challenges, secondly, the solutions to mitigate the challenges and thirdly the results that we have obtained by applying the solutions to the problem sets.","PeriodicalId":332420,"journal":{"name":"2013 IEEE International Symposium on Software Reliability Engineering Workshops (ISSREW)","volume":"241 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2013-12-19","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"134034285","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}
Pub Date : 2013-12-19DOI: 10.1109/ISSREW.2013.6688849
D. Falessi, L. Layman
NASA anomaly databases are rich resources of software failure data in the field. These data are often captured in natural language that is not appropriate for trending or statistical analyses. This fast abstract describes a feasibility study of applying 60 natural language processing techniques for automatically classifying anomaly data to enable trend analyses.
{"title":"Automated classification of NASA anomalies using natural language processing techniques","authors":"D. Falessi, L. Layman","doi":"10.1109/ISSREW.2013.6688849","DOIUrl":"https://doi.org/10.1109/ISSREW.2013.6688849","url":null,"abstract":"NASA anomaly databases are rich resources of software failure data in the field. These data are often captured in natural language that is not appropriate for trending or statistical analyses. This fast abstract describes a feasibility study of applying 60 natural language processing techniques for automatically classifying anomaly data to enable trend analyses.","PeriodicalId":332420,"journal":{"name":"2013 IEEE International Symposium on Software Reliability Engineering Workshops (ISSREW)","volume":"30 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2013-12-19","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"134367863","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}
Pub Date : 2013-12-19DOI: 10.1109/ISSREW.2013.6688872
Lakshmankumar Mukkavilli
Unit testing is recognized as an important part of software development. There are several frameworks to facilitate unit testing. All these frameworks provide support for executing various functions in the unit under test. Our analysis of customer found defects indicated that most of the unit test escapes were a result of execution of sequences of API's. None of the frameworks we looked provided explicit support for execution of API sequences. We designed and implemented a unit testing framework where we provided direct support for specification of API sequences. Each unit test is specified as a directed graph. Each edge corresponds to execution of an API and nodes are used for validation. The framework generates various paths through the graph. Various traversal policies like random, all nodes/edges, every adjacent edge pair etc. are supported. We rewrote unit tests for four features using the new framework. Each unit under test is about 2000 lines of code. Directed graph model helped uncover about 6 new bugs/feature. Automatic path generation has helped explore various API sequences that are very difficult to test manually. Code coverage increased on the average by about 6%. The framework is in production use and is able to uncover various API sequence bugs that are not easily uncovered by traditional unit testing tools. After initial training, engineers are eager to model their tests as directed graphs.
{"title":"Directed graph as a model for unit testing","authors":"Lakshmankumar Mukkavilli","doi":"10.1109/ISSREW.2013.6688872","DOIUrl":"https://doi.org/10.1109/ISSREW.2013.6688872","url":null,"abstract":"Unit testing is recognized as an important part of software development. There are several frameworks to facilitate unit testing. All these frameworks provide support for executing various functions in the unit under test. Our analysis of customer found defects indicated that most of the unit test escapes were a result of execution of sequences of API's. None of the frameworks we looked provided explicit support for execution of API sequences. We designed and implemented a unit testing framework where we provided direct support for specification of API sequences. Each unit test is specified as a directed graph. Each edge corresponds to execution of an API and nodes are used for validation. The framework generates various paths through the graph. Various traversal policies like random, all nodes/edges, every adjacent edge pair etc. are supported. We rewrote unit tests for four features using the new framework. Each unit under test is about 2000 lines of code. Directed graph model helped uncover about 6 new bugs/feature. Automatic path generation has helped explore various API sequences that are very difficult to test manually. Code coverage increased on the average by about 6%. The framework is in production use and is able to uncover various API sequence bugs that are not easily uncovered by traditional unit testing tools. After initial training, engineers are eager to model their tests as directed graphs.","PeriodicalId":332420,"journal":{"name":"2013 IEEE International Symposium on Software Reliability Engineering Workshops (ISSREW)","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2013-12-19","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116117796","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}
Pub Date : 2013-12-19DOI: 10.1109/ISSREW.2013.6688913
T. Saruwatari, Shuichiro Yamamoto, Y. Matsuno
Recently, serious failures of complex IT systems are becoming social problems. Assurance case has been attracted as the technique of assuring the dependability of critical systems in such a situation. We have proposed d*framework which is an extended assurance case notation based on the network of dependable actors. In this paper, we show the result of a case study to evaluate the effectiveness of d*framework as follows. First, an assurance case of GSN is translated equivalently into d*framework. Then, experiments are designed to compare effectiveness of GSN and d*framework. Finally, experimental hypotheses are evaluated by the results. An extended version of D-Case Editor is also used to describe GSN and d*framework assurance case in case study.
{"title":"A comparative study of d∗framework and GSN","authors":"T. Saruwatari, Shuichiro Yamamoto, Y. Matsuno","doi":"10.1109/ISSREW.2013.6688913","DOIUrl":"https://doi.org/10.1109/ISSREW.2013.6688913","url":null,"abstract":"Recently, serious failures of complex IT systems are becoming social problems. Assurance case has been attracted as the technique of assuring the dependability of critical systems in such a situation. We have proposed d*framework which is an extended assurance case notation based on the network of dependable actors. In this paper, we show the result of a case study to evaluate the effectiveness of d*framework as follows. First, an assurance case of GSN is translated equivalently into d*framework. Then, experiments are designed to compare effectiveness of GSN and d*framework. Finally, experimental hypotheses are evaluated by the results. An extended version of D-Case Editor is also used to describe GSN and d*framework assurance case in case study.","PeriodicalId":332420,"journal":{"name":"2013 IEEE International Symposium on Software Reliability Engineering Workshops (ISSREW)","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2013-12-19","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130993347","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}
京公网安备 11010802042870号
京ICP备2023020795号-1
扫码关注我们
求助内容：
应助结果提醒方式：