Pub Date : 2022-10-01DOI: 10.1109/issre55969.2022.00005
K. Goseva-Popstojanova, B. Cukic
{"title":"Message from the General Co-Chairs: ISSRE 2022","authors":"K. Goseva-Popstojanova, B. Cukic","doi":"10.1109/issre55969.2022.00005","DOIUrl":"https://doi.org/10.1109/issre55969.2022.00005","url":null,"abstract":"","PeriodicalId":369133,"journal":{"name":"IEEE International Symposium on Software Reliability Engineering","volume":"58 11","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2022-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"120815754","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 : 2021-10-01DOI: 10.1109/issre52982.2021.00007
F. Pastore, Ling-yong Zhang
{"title":"Message from the Program Co-Chairs: ISSRE 2022","authors":"F. Pastore, Ling-yong Zhang","doi":"10.1109/issre52982.2021.00007","DOIUrl":"https://doi.org/10.1109/issre52982.2021.00007","url":null,"abstract":"","PeriodicalId":369133,"journal":{"name":"IEEE International Symposium on Software Reliability Engineering","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2021-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129838280","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-11-01DOI: 10.1109/ISSRE.2013.6698876
B. Boehm, G. Holzmann
Is quality really free? Often, but not in many situations. Are organizations getting the best value for their investments in reliability? Frequently not. If different stakeholders are relying on the system and software for different properties, is there a single reliability metric to manage to? Frequently not. Is reliability affected by decisions on other system and software ilities? Often quite seriously. This talk will review a number of data sources, case studies, calibrated models, and recent research on systems and software ility tradeoffs to suggest ways that can help improve an organization's return on investments in more reliable systems and software.
{"title":"Keynote speaker 1: The economics of systems and software reliability","authors":"B. Boehm, G. Holzmann","doi":"10.1109/ISSRE.2013.6698876","DOIUrl":"https://doi.org/10.1109/ISSRE.2013.6698876","url":null,"abstract":"Is quality really free? Often, but not in many situations. Are organizations getting the best value for their investments in reliability? Frequently not. If different stakeholders are relying on the system and software for different properties, is there a single reliability metric to manage to? Frequently not. Is reliability affected by decisions on other system and software ilities? Often quite seriously. This talk will review a number of data sources, case studies, calibrated models, and recent research on systems and software ility tradeoffs to suggest ways that can help improve an organization's return on investments in more reliable systems and software.","PeriodicalId":369133,"journal":{"name":"IEEE International Symposium on Software Reliability Engineering","volume":"108 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2013-11-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132492613","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}
P. Bishop, R. Bloomfield, Ilir Gashi, Vladimir Stankovic
We have previously reported [1] the results of an exploratory analysis of the potential gains in detection capability from using diverse AntiVirus products. The analysis was based on 1599 malware samples collected from a distributed honey pot deployment over a period of 178 days. The malware samples were sent to the signature engines of 32 different AntiVirus products hosted by the Virus Total service. The analysis suggested significant gains in detection capability from using more than one AntiVirus product in a one-out-of-two intrusion-tolerant setup. In this paper we present new analysis of this dataset to explore the detection gains that can be achieved from using more diversity (i.e. more than two AntiVirus products), how diversity may help to reduce the "at risk time" of a system and a preliminary model-fitting using the hyper-exponential distribution.
{"title":"Diversity for Security: A Study with Off-the-Shelf AntiVirus Engines","authors":"P. Bishop, R. Bloomfield, Ilir Gashi, Vladimir Stankovic","doi":"10.1109/ISSRE.2011.15","DOIUrl":"https://doi.org/10.1109/ISSRE.2011.15","url":null,"abstract":"We have previously reported [1] the results of an exploratory analysis of the potential gains in detection capability from using diverse AntiVirus products. The analysis was based on 1599 malware samples collected from a distributed honey pot deployment over a period of 178 days. The malware samples were sent to the signature engines of 32 different AntiVirus products hosted by the Virus Total service. The analysis suggested significant gains in detection capability from using more than one AntiVirus product in a one-out-of-two intrusion-tolerant setup. In this paper we present new analysis of this dataset to explore the detection gains that can be achieved from using more diversity (i.e. more than two AntiVirus products), how diversity may help to reduce the \"at risk time\" of a system and a preliminary model-fitting using the hyper-exponential distribution.","PeriodicalId":369133,"journal":{"name":"IEEE International Symposium on Software Reliability Engineering","volume":"16 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-11-29","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122984201","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}
Teachers can learn many lessons by examining experiences in teaching SRE to software practitioners and analyzing their feedback. I have taught several thousand participants over 15 years in a wide variety of organizations and applications. Participants included software developers, testers, reliability and quality control staff, and managers. Most of what I've learned applies to any course and is not SRE-specific. It also applies to the practitioners of the future, university students
{"title":"Teaching SRE to Software Practitioners","authors":"J. Musa","doi":"10.1109/ISSRE.2005.43","DOIUrl":"https://doi.org/10.1109/ISSRE.2005.43","url":null,"abstract":"Teachers can learn many lessons by examining experiences in teaching SRE to software practitioners and analyzing their feedback. I have taught several thousand participants over 15 years in a wide variety of organizations and applications. Participants included software developers, testers, reliability and quality control staff, and managers. Most of what I've learned applies to any course and is not SRE-specific. It also applies to the practitioners of the future, university students","PeriodicalId":369133,"journal":{"name":"IEEE International Symposium on Software Reliability Engineering","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2005-11-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130320726","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}
Software reliability has progressively become critical issues due to the number and the nature of the fields invaded. Software development companies need to be provided with the capability to improve their software development process and decrease its related costs. The Software Reliability Engineering Curriculum and in particular a graduate level software reliability modeling course at the University of Maryland was created to respond to this need. In this paper, the contents of the course in the context of a particularly diverse environment are discussed
{"title":"Teaching SRE in a Diverse Graduate Student Context","authors":"C. Smidts","doi":"10.1109/ISSRE.2005.42","DOIUrl":"https://doi.org/10.1109/ISSRE.2005.42","url":null,"abstract":"Software reliability has progressively become critical issues due to the number and the nature of the fields invaded. Software development companies need to be provided with the capability to improve their software development process and decrease its related costs. The Software Reliability Engineering Curriculum and in particular a graduate level software reliability modeling course at the University of Maryland was created to respond to this need. In this paper, the contents of the course in the context of a particularly diverse environment are discussed","PeriodicalId":369133,"journal":{"name":"IEEE International Symposium on Software Reliability Engineering","volume":"43 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2005-11-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122084318","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}
The purpose of the panel is to provide an open exchange of how software reliability engineering is taught in universities and professional courses and how practitioners think it should be taught. Through the panel, educators can learn more about what other educators teach, how they teach it, and what resources they have to share. Practitioners (both panelists and audience) can provide insight into what they feel should be taught based upon practical application of software reliability concepts for product development.
{"title":"How Should Software Reliability Engineering Be Taught?","authors":"J. Musa, L. Williams","doi":"10.1109/ISSRE.2005.22","DOIUrl":"https://doi.org/10.1109/ISSRE.2005.22","url":null,"abstract":"The purpose of the panel is to provide an open exchange of how software reliability engineering is taught in universities and professional courses and how practitioners think it should be taught. Through the panel, educators can learn more about what other educators teach, how they teach it, and what resources they have to share. Practitioners (both panelists and audience) can provide insight into what they feel should be taught based upon practical application of software reliability concepts for product development.","PeriodicalId":369133,"journal":{"name":"IEEE International Symposium on Software Reliability Engineering","volume":"145 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2005-11-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127309395","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}
To maximize business value, commercial software organizations need to apply software reliability engineering (SRE) using a distributed model where key practices are performed by different roles in the organization. SRE practitioners need to understand the landscape of software development in order to define a program that is effective at moving the organization towards higher reliability
{"title":"Designing an SRE Program for Commercial Software Organizations","authors":"W. Snipes, J. Hudepohl","doi":"10.1109/ISSRE.2005.17","DOIUrl":"https://doi.org/10.1109/ISSRE.2005.17","url":null,"abstract":"To maximize business value, commercial software organizations need to apply software reliability engineering (SRE) using a distributed model where key practices are performed by different roles in the organization. SRE practitioners need to understand the landscape of software development in order to define a program that is effective at moving the organization towards higher reliability","PeriodicalId":369133,"journal":{"name":"IEEE International Symposium on Software Reliability Engineering","volume":"20 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2005-11-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114796038","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}
A large percentage of software development costs are spent on software reliability and testing. However, many practicing software engineers and graduate students in computer science have never taken a course in software reliability or software testing. A graduate-level software engineering course at North Carolina State University provides instruction in these topics to better prepare current and future software engineers for the software reliability and testing challenges. The course takes place in a laboratory setting such that students can learn testing and reliability theory and apply this theory immediately
{"title":"Teaching an Active-Participation University Course in Software Reliability and Testing","authors":"L. Williams","doi":"10.1109/ISSRE.2005.41","DOIUrl":"https://doi.org/10.1109/ISSRE.2005.41","url":null,"abstract":"A large percentage of software development costs are spent on software reliability and testing. However, many practicing software engineers and graduate students in computer science have never taken a course in software reliability or software testing. A graduate-level software engineering course at North Carolina State University provides instruction in these topics to better prepare current and future software engineers for the software reliability and testing challenges. The course takes place in a laboratory setting such that students can learn testing and reliability theory and apply this theory immediately","PeriodicalId":369133,"journal":{"name":"IEEE International Symposium on Software Reliability Engineering","volume":"484 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2005-11-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"133697364","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}
Today's software development environment requires tools and techniques for accurate, efficient evaluation of product reliability. To be successful, SRE must address the common, yet complex issues facing companies when assessing their product's reliability, such as the large number of customer usage scenarios, limited reliability evaluation times, and comparisons with competing products
{"title":"Software Development SRE Needs","authors":"M. Garzia","doi":"10.1109/ISSRE.2005.38","DOIUrl":"https://doi.org/10.1109/ISSRE.2005.38","url":null,"abstract":"Today's software development environment requires tools and techniques for accurate, efficient evaluation of product reliability. To be successful, SRE must address the common, yet complex issues facing companies when assessing their product's reliability, such as the large number of customer usage scenarios, limited reliability evaluation times, and comparisons with competing products","PeriodicalId":369133,"journal":{"name":"IEEE International Symposium on Software Reliability Engineering","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2005-11-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129667724","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
扫码关注我们
求助内容：
应助结果提醒方式：