The Experts below are selected from a list of 67098 Experts worldwide ranked by ideXlab platform
Michael R Lyu - One of the best experts on this subject based on the ideXlab platform.
-
a survey on automated log analysis for Reliability Engineering
ACM Computing Surveys, 2021Co-Authors: Zhuangbin Chen, Tianyi Yang, Michael R LyuAbstract:Logs are semi-structured text generated by logging statements in software source code. In recent decades, software logs have become imperative in the Reliability assurance mechanism of many software systems, because they are often the only data available that record software runtime information. As modern software is evolving into a large scale, the volume of logs has increased rapidly. To enable effective and efficient usage of modern software logs in Reliability Engineering, a number of studies have been conducted on automated log analysis. This survey presents a detailed overview of automated log analysis research, including how to automate and assist the writing of logging statements, how to compress logs, how to parse logs into structured event templates, and how to employ logs to detect anomalies, predict failures, and facilitate diagnosis. Additionally, we survey work that releases open-source toolkits and datasets. Based on the discussion of the recent advances, we present several promising future directions toward real-world and next-generation automated log analysis.
-
software Reliability Engineering a roadmap
International Conference on Software Engineering, 2007Co-Authors: Michael R LyuAbstract:Software Reliability Engineering is focused on Engineering techniques for developing and maintaining software systems whose Reliability can be quantitatively evaluated. In order to estimate as well as to predict the Reliability of software systems, failure data need to be properly measured by various means during software development and operational phases. Moreover, credible software Reliability models are required to track underlying software failure processes for accurate Reliability analysis and forecasting. Although software Reliability has remained an active research subject over the past 35 years, challenges and open questions still exist. In particular, vital future goals include the development of new software Reliability Engineering paradigms that take software architectures, testing techniques, and software failure manifestation mechanisms into consideration. In this paper, we review the history of software Reliability Engineering, the current trends and existing problems, and specific difficulties. Possible future directions and promising research subjects in software Reliability Engineering are also addressed.
-
an empirical study on testing and fault tolerance for software Reliability Engineering
International Symposium on Software Reliability Engineering, 2003Co-Authors: Michael R Lyu, Zubin Huang, S K S Sze, Xia CaiAbstract:Software testing and software fault tolerance are two major techniques for developing reliable software systems, yet limited empirical data are available in the literature to evaluate their effectiveness. We conducted a major experiment to engage 34 programming teams to independently develop multiple software versions for an industry-scale critical flight application, and collected faults detected in these program versions. To evaluate the effectiveness of software testing and software fault tolerance, mutants were created by injecting real faults occurred in the development stage. The nature, manifestation, detection, and correlation of these faults were carefully investigated. The results show that coverage testing is generally an effective means to detecting software faults, but the effectiveness of testing coverage is not equivalent to that of mutation coverage, which is a more truthful indicator of testing quality. We also found that exact faults found among versions are very limited. This result supports software fault tolerance by design diversity as a creditable approach for software Reliability Engineering. Finally we conducted domain analysis approach for test case generation, and concluded that it is a promising technique for software testing purpose.
Mehmet Aksit - One of the best experts on this subject based on the ideXlab platform.
-
software architecture Reliability analysis using failure scenarios
Journal of Systems and Software, 2008Co-Authors: Bedir Tekinerdogan, Hasan Sözer, Mehmet AksitAbstract:With the increasing size and complexity of software in embedded systems, software has now become a primary threat for the Reliability. Several mature conventional Reliability Engineering techniques exist in literature but traditionally these have primarily addressed failures in hardware components and usually assume the availability of a running system. Software architecture analysis methods aim to analyze the quality of software-intensive system early at the software architecture design level and before a system is implemented. We propose a Software Architecture Reliability Analysis Approach (SARAH) that benefits from mature Reliability Engineering techniques and scenario-based software architecture analysis to provide an early software Reliability analysis at the architecture design level. SARAH defines the notion of failure scenario model that is based on the Failure Modes and Effects Analysis method (FMEA) in the Reliability Engineering domain. The failure scenario model is applied to represent so-called failure scenarios that are utilized to derive fault tree sets (FTS). Fault tree sets are utilized to provide a severity analysis for the overall software architecture and the individual architectural elements. Despite conventional Reliability analysis techniques which prioritize failures based on criteria such as safety concerns, in SARAH failure scenarios are prioritized based on severity from the end-user perspective. SARAH results in a failure analysis report that can be utilized to identify architectural tactics for improving the Reliability of the software architecture. The approach is illustrated using an industrial case for analyzing Reliability of the software architecture of the next release of a Digital TV.
-
software architecture Reliability analysis using failure scenarios
IEEE IFIP International Conference on Software Architecture, 2005Co-Authors: Bedir Tekinerdogan, Mehmet AksitAbstract:We propose a Software Architecture Reliability Analysis (SARA) approach that benefits from both Reliability Engineering and scenario-based software architecture analysis to provide an early Reliability analysis of the software architecture. SARA makes use of failure scenarios that are prioritized with respect to the user-perception in order to provide a severity analysis for the software architecture and the individual components.
Bedir Tekinerdogan - One of the best experts on this subject based on the ideXlab platform.
-
software architecture Reliability analysis using failure scenarios
Journal of Systems and Software, 2008Co-Authors: Bedir Tekinerdogan, Hasan Sözer, Mehmet AksitAbstract:With the increasing size and complexity of software in embedded systems, software has now become a primary threat for the Reliability. Several mature conventional Reliability Engineering techniques exist in literature but traditionally these have primarily addressed failures in hardware components and usually assume the availability of a running system. Software architecture analysis methods aim to analyze the quality of software-intensive system early at the software architecture design level and before a system is implemented. We propose a Software Architecture Reliability Analysis Approach (SARAH) that benefits from mature Reliability Engineering techniques and scenario-based software architecture analysis to provide an early software Reliability analysis at the architecture design level. SARAH defines the notion of failure scenario model that is based on the Failure Modes and Effects Analysis method (FMEA) in the Reliability Engineering domain. The failure scenario model is applied to represent so-called failure scenarios that are utilized to derive fault tree sets (FTS). Fault tree sets are utilized to provide a severity analysis for the overall software architecture and the individual architectural elements. Despite conventional Reliability analysis techniques which prioritize failures based on criteria such as safety concerns, in SARAH failure scenarios are prioritized based on severity from the end-user perspective. SARAH results in a failure analysis report that can be utilized to identify architectural tactics for improving the Reliability of the software architecture. The approach is illustrated using an industrial case for analyzing Reliability of the software architecture of the next release of a Digital TV.
-
software architecture Reliability analysis using failure scenarios
IEEE IFIP International Conference on Software Architecture, 2005Co-Authors: Bedir Tekinerdogan, Mehmet AksitAbstract:We propose a Software Architecture Reliability Analysis (SARA) approach that benefits from both Reliability Engineering and scenario-based software architecture analysis to provide an early Reliability analysis of the software architecture. SARA makes use of failure scenarios that are prioritized with respect to the user-perception in order to provide a severity analysis for the software architecture and the individual components.
Hasan Sözer - One of the best experts on this subject based on the ideXlab platform.
-
software architecture Reliability analysis using failure scenarios
Journal of Systems and Software, 2008Co-Authors: Bedir Tekinerdogan, Hasan Sözer, Mehmet AksitAbstract:With the increasing size and complexity of software in embedded systems, software has now become a primary threat for the Reliability. Several mature conventional Reliability Engineering techniques exist in literature but traditionally these have primarily addressed failures in hardware components and usually assume the availability of a running system. Software architecture analysis methods aim to analyze the quality of software-intensive system early at the software architecture design level and before a system is implemented. We propose a Software Architecture Reliability Analysis Approach (SARAH) that benefits from mature Reliability Engineering techniques and scenario-based software architecture analysis to provide an early software Reliability analysis at the architecture design level. SARAH defines the notion of failure scenario model that is based on the Failure Modes and Effects Analysis method (FMEA) in the Reliability Engineering domain. The failure scenario model is applied to represent so-called failure scenarios that are utilized to derive fault tree sets (FTS). Fault tree sets are utilized to provide a severity analysis for the overall software architecture and the individual architectural elements. Despite conventional Reliability analysis techniques which prioritize failures based on criteria such as safety concerns, in SARAH failure scenarios are prioritized based on severity from the end-user perspective. SARAH results in a failure analysis report that can be utilized to identify architectural tactics for improving the Reliability of the software architecture. The approach is illustrated using an industrial case for analyzing Reliability of the software architecture of the next release of a Digital TV.
Xia Cai - One of the best experts on this subject based on the ideXlab platform.
-
an empirical study on testing and fault tolerance for software Reliability Engineering
International Symposium on Software Reliability Engineering, 2003Co-Authors: Michael R Lyu, Zubin Huang, S K S Sze, Xia CaiAbstract:Software testing and software fault tolerance are two major techniques for developing reliable software systems, yet limited empirical data are available in the literature to evaluate their effectiveness. We conducted a major experiment to engage 34 programming teams to independently develop multiple software versions for an industry-scale critical flight application, and collected faults detected in these program versions. To evaluate the effectiveness of software testing and software fault tolerance, mutants were created by injecting real faults occurred in the development stage. The nature, manifestation, detection, and correlation of these faults were carefully investigated. The results show that coverage testing is generally an effective means to detecting software faults, but the effectiveness of testing coverage is not equivalent to that of mutation coverage, which is a more truthful indicator of testing quality. We also found that exact faults found among versions are very limited. This result supports software fault tolerance by design diversity as a creditable approach for software Reliability Engineering. Finally we conducted domain analysis approach for test case generation, and concluded that it is a promising technique for software testing purpose.
