Deprecated: $wgMWOAuthSharedUserIDs=false is deprecated, set $wgMWOAuthSharedUserIDs=true, $wgMWOAuthSharedUserSource='local' instead [Called from MediaWiki\HookContainer\HookContainer::run in /var/www/html/w/includes/HookContainer/HookContainer.php at line 135] in /var/www/html/w/includes/Debug/MWDebug.php on line 372
A new software reliability growth model: multigeneration faults and a power-law testing-effort function - MaRDI portal

A new software reliability growth model: multigeneration faults and a power-law testing-effort function (Q1793776)

From MaRDI portal





scientific article; zbMATH DE number 6953767
Language Label Description Also known as
English
A new software reliability growth model: multigeneration faults and a power-law testing-effort function
scientific article; zbMATH DE number 6953767

    Statements

    A new software reliability growth model: multigeneration faults and a power-law testing-effort function (English)
    0 references
    0 references
    0 references
    12 October 2018
    0 references
    Summary: Software reliability growth models (SRGMs) based on a nonhomogeneous Poisson process (NHPP) are widely used to describe the stochastic failure behavior and assess the reliability of software systems. For these models, the testing-effort effect and the fault interdependency play significant roles. Considering a power-law function of testing effort and the interdependency of multigeneration faults, we propose a modified SRGM to reconsider the reliability of open source software (OSS) systems and then to validate the model's performance using several real-world data. Our empirical experiments show that the model well fits the failure data and presents a high-level prediction capability. We also formally examine the optimal policy of software release, considering both the testing cost and the reliability requirement. By conducting sensitivity analysis, we find that if the testing-effort effect or the fault interdependency was ignored, the best time to release software would be seriously delayed and more resources would be misplaced in testing the software.
    0 references

    Identifiers