Pub Date : 2018-10-01DOI: 10.1109/ISSREW.2018.00017
G. Sena, Rivalino Matias
Numerous problems investigated in Software Aging and Rejuvenation (SAR) research are also of interest of other research communities. One of these problems is memory leak detection, which is one of the most recurrent topic in the SAR literature in its twenty-three years. Due to this major interest of SAR researchers on memory leak detection techniques, naturally a question emerges: how other areas deal with this problem? To answer this question we surveyed the main scientific digital libraries, from 1982 to 2017, looking for studies on memory-leak detection that were not originated in the SAR community. We found 105 papers that matched our inclusion and exclusion criteria. Our method was based on the systematic mapping review approach. The empirical findings revealed several intersections of SAR research with studies conducted in other areas, offering interesting insights on different research cooperation opportunities.
{"title":"A Systematic Mapping Review of Memory Leak Detection Techniques","authors":"G. Sena, Rivalino Matias","doi":"10.1109/ISSREW.2018.00017","DOIUrl":"https://doi.org/10.1109/ISSREW.2018.00017","url":null,"abstract":"Numerous problems investigated in Software Aging and Rejuvenation (SAR) research are also of interest of other research communities. One of these problems is memory leak detection, which is one of the most recurrent topic in the SAR literature in its twenty-three years. Due to this major interest of SAR researchers on memory leak detection techniques, naturally a question emerges: how other areas deal with this problem? To answer this question we surveyed the main scientific digital libraries, from 1982 to 2017, looking for studies on memory-leak detection that were not originated in the SAR community. We found 105 papers that matched our inclusion and exclusion criteria. Our method was based on the systematic mapping review approach. The empirical findings revealed several intersections of SAR research with studies conducted in other areas, offering interesting insights on different research cooperation opportunities.","PeriodicalId":321448,"journal":{"name":"2018 IEEE International Symposium on Software Reliability Engineering Workshops (ISSREW)","volume":" 45","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2018-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"120832414","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 : 2018-10-01DOI: 10.1109/ISSREW.2018.00-26
V. Mendiratta, L. Jagadeesan, R. Hanmer, M. Rahman
Software-Defined Networking (SDN) is a fundamental paradigm shift in communication networks, separating the network control and data planes. This separation enables the dynamic reconfiguration of the data plane at run-time through control plane software. The logically centralized control plane - the network brain - is typically realized in a distributed fashion to avoid a single point of failure, to provide redundancy of key control plane functions vis-a-vis the data plane and to provide horizontal scale-out. As SDN begins to be adopted as the underlying paradigm and platform for carrier-grade networks through the advent of open-source SDN controllers, a deep understanding of the reliability of SDNs is essential to satisfying carrier-grade requirements and fulfilling service-level agreements. To this end, we present a model of SDN reliability under control and data plane failures, that encompasses the distributed nature of the SDN control plane.
{"title":"How Reliable Is My Software-Defined Network? Models and Failure Impacts","authors":"V. Mendiratta, L. Jagadeesan, R. Hanmer, M. Rahman","doi":"10.1109/ISSREW.2018.00-26","DOIUrl":"https://doi.org/10.1109/ISSREW.2018.00-26","url":null,"abstract":"Software-Defined Networking (SDN) is a fundamental paradigm shift in communication networks, separating the network control and data planes. This separation enables the dynamic reconfiguration of the data plane at run-time through control plane software. The logically centralized control plane - the network brain - is typically realized in a distributed fashion to avoid a single point of failure, to provide redundancy of key control plane functions vis-a-vis the data plane and to provide horizontal scale-out. As SDN begins to be adopted as the underlying paradigm and platform for carrier-grade networks through the advent of open-source SDN controllers, a deep understanding of the reliability of SDNs is essential to satisfying carrier-grade requirements and fulfilling service-level agreements. To this end, we present a model of SDN reliability under control and data plane failures, that encompasses the distributed nature of the SDN control plane.","PeriodicalId":321448,"journal":{"name":"2018 IEEE International Symposium on Software Reliability Engineering Workshops (ISSREW)","volume":"20 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2018-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125906083","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 : 2018-10-01DOI: 10.1109/ISSREW.2018.000-2
Juliana Oliveira
The popularity of the Android platform can be attributed to their ability to run apps, end-user programs that leverage the many capabilities of mobile devices, potentially in unforeseen ways. Apps are in widespread use and App crashing is the most common cause of complaints about Android mobile phone apps according to recent studies. Android apps are usually written in the Java programming language. Java includes an exception handling mechanism that allows programs to signal the occurrence of errors by throwing exceptions and to handle these exceptions by catching them. All the Android-specific abstractions, such as activities and asynctasks, can throw exceptions when errors occur. When an app catches the exceptions that it or the libraries upon which it depends throw, it can resume its activity or, at least, fail in a graceful way. On the other hand, uncaught exceptions make the app crash. The exception handling mechanism for the Android platform has two liabilities: (1) the "Terminate ALL" approach and (2) a lack of a holistic view on exceptional behavior. This research investigates the relationship between Android abstractions and robustness of apps during evolution and proposes a new exception handling mechanism to tame exceptions in Android applications.
{"title":"Taming Exceptions in Android Applications","authors":"Juliana Oliveira","doi":"10.1109/ISSREW.2018.000-2","DOIUrl":"https://doi.org/10.1109/ISSREW.2018.000-2","url":null,"abstract":"The popularity of the Android platform can be attributed to their ability to run apps, end-user programs that leverage the many capabilities of mobile devices, potentially in unforeseen ways. Apps are in widespread use and App crashing is the most common cause of complaints about Android mobile phone apps according to recent studies. Android apps are usually written in the Java programming language. Java includes an exception handling mechanism that allows programs to signal the occurrence of errors by throwing exceptions and to handle these exceptions by catching them. All the Android-specific abstractions, such as activities and asynctasks, can throw exceptions when errors occur. When an app catches the exceptions that it or the libraries upon which it depends throw, it can resume its activity or, at least, fail in a graceful way. On the other hand, uncaught exceptions make the app crash. The exception handling mechanism for the Android platform has two liabilities: (1) the \"Terminate ALL\" approach and (2) a lack of a holistic view on exceptional behavior. This research investigates the relationship between Android abstractions and robustness of apps during evolution and proposes a new exception handling mechanism to tame exceptions in Android applications.","PeriodicalId":321448,"journal":{"name":"2018 IEEE International Symposium on Software Reliability Engineering Workshops (ISSREW)","volume":"16 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2018-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125284036","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 : 2018-10-01DOI: 10.1109/issrew.2018.00-56
{"title":"Message from the ISSRE 2018 Doctoral Symposium Chairs","authors":"","doi":"10.1109/issrew.2018.00-56","DOIUrl":"https://doi.org/10.1109/issrew.2018.00-56","url":null,"abstract":"","PeriodicalId":321448,"journal":{"name":"2018 IEEE International Symposium on Software Reliability Engineering Workshops (ISSREW)","volume":"26 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2018-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126656976","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 : 2018-10-01DOI: 10.1109/ISSREW.2018.00022
Matheus Torquato, M. Vieira
This paper presents a set of analytical models for availability evaluation of a virtualized system with VMM software rejuvenation enabled by VM migration schedule. The proposed models consider aspects of varying workload. We adopted the interacting models approach to reduce time and cost for models' evaluation. Our metrics of interest are steady-state availability and annual downtime. In our first case study, we compare the monolithic model and interacting models approach. Obtained results show a significant reduction in time for model evaluation in the interacting models approach. Our second case study presents a variety of scenarios with a varying workload. We consider the workload variation with two stages: i) peak - when the workload submitted is high; and ii) off-peak - when the workload submitted is low. The evaluation results comprise from systems without high workload demand (peakDuration = 0h per day) to systems with only high workload demand (peakDuration = 24h per day). For all considered scenarios, we present the best rejuvenation schedule to maximize system availability. In scenarios with a heavy workload, the downtime avoidance caused by software rejuvenation surpass three days.
{"title":"Interacting SRN Models for Availability Evaluation of VM Migration as Rejuvenation on a System under Varying Workload","authors":"Matheus Torquato, M. Vieira","doi":"10.1109/ISSREW.2018.00022","DOIUrl":"https://doi.org/10.1109/ISSREW.2018.00022","url":null,"abstract":"This paper presents a set of analytical models for availability evaluation of a virtualized system with VMM software rejuvenation enabled by VM migration schedule. The proposed models consider aspects of varying workload. We adopted the interacting models approach to reduce time and cost for models' evaluation. Our metrics of interest are steady-state availability and annual downtime. In our first case study, we compare the monolithic model and interacting models approach. Obtained results show a significant reduction in time for model evaluation in the interacting models approach. Our second case study presents a variety of scenarios with a varying workload. We consider the workload variation with two stages: i) peak - when the workload submitted is high; and ii) off-peak - when the workload submitted is low. The evaluation results comprise from systems without high workload demand (peakDuration = 0h per day) to systems with only high workload demand (peakDuration = 24h per day). For all considered scenarios, we present the best rejuvenation schedule to maximize system availability. In scenarios with a heavy workload, the downtime avoidance caused by software rejuvenation surpass three days.","PeriodicalId":321448,"journal":{"name":"2018 IEEE International Symposium on Software Reliability Engineering Workshops (ISSREW)","volume":"8 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2018-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129950521","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 : 2018-10-01DOI: 10.1109/ISSREW.2018.00-19
Wei Chen, Guoquan Wu, Jun Wei
Infrastructure as Code (IaC), which specifies system configurations in an imperative or declarative way, automates environment set up, system deployment and configuration. Despite wide adoption, developing and maintaining high-quality IaC artifacts is still challenging. This paper proposes an approach to handling the fine-grained and frequently occurring IaC code errors. The approach extracts code changes from historical commits and clusters them into groups, by constructing a feature model of code changes and employing an unsupervised machine learning algorithm. It identifies error patterns from the clusters and proposes a set of inspection rules to check the potential IaC code errors. In practice, we take Puppet code artifacts as subject objects and perform a comprehensive study on 14 popular Puppet artifacts. In our experiment, we get 41 cross-artifact error patterns, covering 42% crawled code changes. Based on these patterns, 30 rules are proposed, covering 60% identified error patterns, to proactively check IaC artifacts. The approach would be helpful in improving code quality of IaC artifacts.
{"title":"An Approach to Identifying Error Patterns for Infrastructure as Code","authors":"Wei Chen, Guoquan Wu, Jun Wei","doi":"10.1109/ISSREW.2018.00-19","DOIUrl":"https://doi.org/10.1109/ISSREW.2018.00-19","url":null,"abstract":"Infrastructure as Code (IaC), which specifies system configurations in an imperative or declarative way, automates environment set up, system deployment and configuration. Despite wide adoption, developing and maintaining high-quality IaC artifacts is still challenging. This paper proposes an approach to handling the fine-grained and frequently occurring IaC code errors. The approach extracts code changes from historical commits and clusters them into groups, by constructing a feature model of code changes and employing an unsupervised machine learning algorithm. It identifies error patterns from the clusters and proposes a set of inspection rules to check the potential IaC code errors. In practice, we take Puppet code artifacts as subject objects and perform a comprehensive study on 14 popular Puppet artifacts. In our experiment, we get 41 cross-artifact error patterns, covering 42% crawled code changes. Based on these patterns, 30 rules are proposed, covering 60% identified error patterns, to proactively check IaC artifacts. The approach would be helpful in improving code quality of IaC artifacts.","PeriodicalId":321448,"journal":{"name":"2018 IEEE International Symposium on Software Reliability Engineering Workshops (ISSREW)","volume":"33 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2018-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"123900126","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 : 2018-10-01DOI: 10.1109/ISSREW.2018.000-5
Madhusudan Srinivasan
A test oracle is essential for software testing. In certain complex systems, it is hard to distinguish between correct and incorrect behavior. Metamorphic testing is one of the solution to solve the test oracle problem. In metamorphic testing, metamorphic relations (MRs) are derived based on the properties exhibited by the program under test (PUT). These MRs play a major role in the generation of test data for conducting MT. The effectiveness of MRs can be determined based on the ability to detect considerable faults for the given PUT. Many metamorphic relations with different fault finding capability can be used to test the PUT and it is important to identify and prioritize the MRs based on its fault finding effectiveness. In order to answer this challenge, we propose to prioritize the MRs based on the diversity in the execution path of the source and follow-up test cases of the MRs. We propose four metrics to capture different levels of diversity in the execution behavior of the test cases for each of the derived MRs. The total weight calculated for each of the MRs using the metrics is used to prioritize the MRs.
{"title":"Prioritization of Metamorphic Relations Based on Test Case Execution Properties","authors":"Madhusudan Srinivasan","doi":"10.1109/ISSREW.2018.000-5","DOIUrl":"https://doi.org/10.1109/ISSREW.2018.000-5","url":null,"abstract":"A test oracle is essential for software testing. In certain complex systems, it is hard to distinguish between correct and incorrect behavior. Metamorphic testing is one of the solution to solve the test oracle problem. In metamorphic testing, metamorphic relations (MRs) are derived based on the properties exhibited by the program under test (PUT). These MRs play a major role in the generation of test data for conducting MT. The effectiveness of MRs can be determined based on the ability to detect considerable faults for the given PUT. Many metamorphic relations with different fault finding capability can be used to test the PUT and it is important to identify and prioritize the MRs based on its fault finding effectiveness. In order to answer this challenge, we propose to prioritize the MRs based on the diversity in the execution path of the source and follow-up test cases of the MRs. We propose four metrics to capture different levels of diversity in the execution behavior of the test cases for each of the derived MRs. The total weight calculated for each of the MRs using the metrics is used to prioritize the MRs.","PeriodicalId":321448,"journal":{"name":"2018 IEEE International Symposium on Software Reliability Engineering Workshops (ISSREW)","volume":"29 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2018-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127553705","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 : 2018-10-01DOI: 10.1109/ISSREW.2018.00028
Michael Fisher, Emily Collins, Louise Dennis, Matt Luckcuck, M. Webster, M. Jump, Vincent Pagé, C. Patchett, F. Dinmohammadi, D. Flynn, V. Robu, Xingyu Zhao
Autonomous systems are increasingly being used in safety-and mission-critical domains, including aviation, manufacturing, healthcare and the automotive industry. Systems for such domains are often verified with respect to essential requirements set by a regulator, as part of a process called certification. In principle, autonomous systems can be deployed if they can be certified for use. However, certification is especially challenging as the condition of both the system and its environment will surely change, limiting the effective use of the system. In this paper we discuss the technological and regulatory background for such systems, and introduce an architectural framework that supports verifiably-correct dynamic self-certification by the system, potentially allowing deployed systems to operate more safely and effectively.
{"title":"Verifiable Self-Certifying Autonomous Systems","authors":"Michael Fisher, Emily Collins, Louise Dennis, Matt Luckcuck, M. Webster, M. Jump, Vincent Pagé, C. Patchett, F. Dinmohammadi, D. Flynn, V. Robu, Xingyu Zhao","doi":"10.1109/ISSREW.2018.00028","DOIUrl":"https://doi.org/10.1109/ISSREW.2018.00028","url":null,"abstract":"Autonomous systems are increasingly being used in safety-and mission-critical domains, including aviation, manufacturing, healthcare and the automotive industry. Systems for such domains are often verified with respect to essential requirements set by a regulator, as part of a process called certification. In principle, autonomous systems can be deployed if they can be certified for use. However, certification is especially challenging as the condition of both the system and its environment will surely change, limiting the effective use of the system. In this paper we discuss the technological and regulatory background for such systems, and introduce an architectural framework that supports verifiably-correct dynamic self-certification by the system, potentially allowing deployed systems to operate more safely and effectively.","PeriodicalId":321448,"journal":{"name":"2018 IEEE International Symposium on Software Reliability Engineering Workshops (ISSREW)","volume":"22 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2018-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"133661277","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 : 2018-10-01DOI: 10.1109/ISSREW.2018.00-23
Megan Hickman, Dakota Fulp, Elisabeth Baseman, S. Blanchard, Hugh Greenberg, William M. Jones, Nathan Debardeleben
Supercomputers, high performance computers, and clusters are composed of very large numbers of independent operating systems that are generating their own system logs. Messages are generated locally on each host and usually are transferred to a central logging infrastructure which keeps a master record of the system as a whole. At Los Alamos National Laboratory (LANL) a collection of open source cloud tools are used which log over a hundred million system log messages per day from over a dozen such systems. Understanding what source code created those messages can be extremely useful to system administrators when they are troubleshooting these complex systems as it can give insight into a subsystem (disk, network, etc.) or even line numbers of source code. Oftentimes, debugging supercomputers is done in environments where open access cannot be provided to all individuals due to security concerns. As such, providing a means for conveying information between system log messages and source code lines allows for communication between system administrators and source developers or supercomputer vendors. In this work, we demonstrate a prototype tool which aims to provide such an expert system. We leverage capabilities from ElasticSearch, one of the open source cloud tools deployed at LANL, and with our own metrics develop a means for correctly matching source code lines as well as files with high confidence. We discuss confidence metrics and show that in our experiments 92% of syslog lines were correctly matched. For any future samples, we predict with 95% confidence that the correct file will be detected between 88.2% and 95.8% of the time. Finally, we discuss enhancements that are underway to improve the tool and study it on a larger dataset.
超级计算机、高性能计算机和集群由大量独立的操作系统组成,这些操作系统生成自己的系统日志。消息在每台主机上本地生成,通常被转移到中央日志基础设施,该基础设施保留了整个系统的主记录。在洛斯阿拉莫斯国家实验室(Los Alamos National Laboratory, LANL),使用了一组开源云工具,每天从十几个这样的系统中记录超过1亿条系统日志消息。当系统管理员对这些复杂的系统进行故障排除时,了解创建这些消息的源代码非常有用,因为它可以深入了解子系统(磁盘、网络等)甚至源代码的行数。通常,调试超级计算机是在由于安全考虑而不能向所有个人提供开放访问的环境中进行的。因此,提供在系统日志消息和源代码行之间传递信息的方法允许系统管理员和源代码开发人员或超级计算机供应商之间进行通信。在这项工作中,我们展示了一个原型工具,旨在提供这样一个专家系统。我们利用了ElasticSearch (LANL部署的开源云工具之一)的功能,并使用我们自己的指标开发了一种方法,可以高可信度地正确匹配源代码行和文件。我们讨论了置信度指标,并表明在我们的实验中,92%的syslog日志行是正确匹配的。对于任何未来的样本,我们以95%的置信度预测,在88.2%到95.8%的时间内将检测到正确的文件。最后,我们讨论了正在进行的改进,以改进工具并在更大的数据集上研究它。
{"title":"Enhancing HPC System Log Analysis by Identifying Message Origin in Source Code","authors":"Megan Hickman, Dakota Fulp, Elisabeth Baseman, S. Blanchard, Hugh Greenberg, William M. Jones, Nathan Debardeleben","doi":"10.1109/ISSREW.2018.00-23","DOIUrl":"https://doi.org/10.1109/ISSREW.2018.00-23","url":null,"abstract":"Supercomputers, high performance computers, and clusters are composed of very large numbers of independent operating systems that are generating their own system logs. Messages are generated locally on each host and usually are transferred to a central logging infrastructure which keeps a master record of the system as a whole. At Los Alamos National Laboratory (LANL) a collection of open source cloud tools are used which log over a hundred million system log messages per day from over a dozen such systems. Understanding what source code created those messages can be extremely useful to system administrators when they are troubleshooting these complex systems as it can give insight into a subsystem (disk, network, etc.) or even line numbers of source code. Oftentimes, debugging supercomputers is done in environments where open access cannot be provided to all individuals due to security concerns. As such, providing a means for conveying information between system log messages and source code lines allows for communication between system administrators and source developers or supercomputer vendors. In this work, we demonstrate a prototype tool which aims to provide such an expert system. We leverage capabilities from ElasticSearch, one of the open source cloud tools deployed at LANL, and with our own metrics develop a means for correctly matching source code lines as well as files with high confidence. We discuss confidence metrics and show that in our experiments 92% of syslog lines were correctly matched. For any future samples, we predict with 95% confidence that the correct file will be detected between 88.2% and 95.8% of the time. Finally, we discuss enhancements that are underway to improve the tool and study it on a larger dataset.","PeriodicalId":321448,"journal":{"name":"2018 IEEE International Symposium on Software Reliability Engineering Workshops (ISSREW)","volume":"110 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2018-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124303646","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 : 2018-10-01DOI: 10.1109/ISSREW.2018.000-8
Florian Hofer
The vision of a fourth industrial revolution lately strongly captured the attention of research. A Cyber-physical system (CPS) is one of the main drivers of this vision. Such system controls an underlying factory interacting with sensors, actuators and other systems creating systems-of-systems. A main point of interest is how these components are built and interconnected, i.e. the system's architecture, and how it might be improved to increase reliability and security. Unfortunately, a recently completed systematic mapping study has shown that security based research for CPS architectures is only weakly present. The target of this research is therefore to find generalized architectural models and patterns that improve reliability and security. The results will enable the improvement of reliability and security of cyber-physical systems in general, leading to a variety of application scenarios and possible use cases.
{"title":"Enhancing Security and Reliability for Smart- Systems' Architectures","authors":"Florian Hofer","doi":"10.1109/ISSREW.2018.000-8","DOIUrl":"https://doi.org/10.1109/ISSREW.2018.000-8","url":null,"abstract":"The vision of a fourth industrial revolution lately strongly captured the attention of research. A Cyber-physical system (CPS) is one of the main drivers of this vision. Such system controls an underlying factory interacting with sensors, actuators and other systems creating systems-of-systems. A main point of interest is how these components are built and interconnected, i.e. the system's architecture, and how it might be improved to increase reliability and security. Unfortunately, a recently completed systematic mapping study has shown that security based research for CPS architectures is only weakly present. The target of this research is therefore to find generalized architectural models and patterns that improve reliability and security. The results will enable the improvement of reliability and security of cyber-physical systems in general, leading to a variety of application scenarios and possible use cases.","PeriodicalId":321448,"journal":{"name":"2018 IEEE International Symposium on Software Reliability Engineering Workshops (ISSREW)","volume":"61 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2018-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"123584580","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}