Reliability prediction for component-based software architectures

Reussner, Ralf; Schmidt, Heinz; Poernomo, Iman

doi:10.1016/s0164-1212(02)00080-8

Cited by 230 publications

(151 citation statements)

References 10 publications

Supporting

Mentioning

151

Contrasting

Order By: Relevance

“…Based on CDG, a reliability analysis algorithm is developed to analyze the reliability of the system as a function of reliabilities of its architectural constituents. Reussner et al [10] and Brosch et al [11], [12] introduced reliability prediction approach for componentbased software architectures that considers the relevant architectural factors of software systems by explicitly modeling the system usage profile and execution environment. Rodrigues et al [13] further considers the influence that the concurrency of component-based software systems has on system reliability.…”

Section: Related Workmentioning

confidence: 99%

Using Hierarchical Scenarios to Predict the Reliability of Component-Based Software

Hou

Chen

2018

IEICE Trans. Inf. & Syst.

View full text Add to dashboard Cite

SUMMARYSystem scenarios that derived from system design specification play an important role in the reliability engineering of componentbased software systems. Several scenario-based approaches have been proposed to predict the reliability of a system at the design time, most of them adopt flat construction of scenarios, which doesn't conform to software design specifications and is subject to introduce state space explosion problem in the large systems. This paper identifies various challenges related to scenario modeling at the early design stages based on software architecture specification. A novel scenario-based reliability modeling and prediction approach is introduced. The approach adopts hierarchical scenario specification to model software reliability to avoid state space explosion and reduce computational complexity. Finally, the evaluation experiment shows the potential of the approach.

show abstract

Section: Related Workmentioning

confidence: 99%

Using Hierarchical Scenarios to Predict the Reliability of Component-Based Software

Hou

Chen

2018

IEICE Trans. Inf. & Syst.

View full text Add to dashboard Cite

show abstract

“…We assume that the χ 2 is the maximum value of χ 2 and there is the poorest correlation with reality. χ 2 means the ideal condition (having the best correlation with reality).…”

Section: Testing Data Evaluatingmentioning

confidence: 99%

“…Reliability is defined here as the probability of the failurefree operation of a software system for a specified period in a specified environment [2,3]. Software reliability test (SRT) is to test software with the purpose of verifying whether the software achieves reliability requirements and evaluating software reliability level based on the operational profile which acquires failure data to estimate the reliability of a software product in quantifiable terms [4,5].…”

Section: Introductionmentioning

confidence: 99%

Large scale software test data generation based on collective constraint and weighted combination method

2017

View full text Add to dashboard Cite

Original scientific paper Software reliability test is to test software with the purpose of verifying whether the software achieves reliability requirements and evaluating software reliability level. Statistical-based software reliability testing generally includes three parts: building usage model, test data generation and testing. The construction of software usage model should reflect user's real use as far as possible. A huge number of test cases are required to satisfy the probability distribution of the actual usage situation; otherwise, the reliability test will lose its original meaning. In this paper, we first propose a new method of structuring software usage model based on modules and constraint-based heuristic method. Then we propose a method for the testing data generation in consideration of the combination and weight of the input data, which reduces a large number of possible combinations of input variables to a few representative ones and improves the practicability of the testing method. To verify the effectiveness of the method proposed in this paper, four groups of experiments are organized. The goodness of fit index (GFI) shows that the proposed method is closer to the actual software use; we also found that the method proposed in this paper has a better coverage by using Java Pathfinder to analyse the four sets of internal code coverage.Keywords: constraint; data generation; GFI; software reliability testing; usage model; weighted combination Generiranje ispitnih podataka za softver zasnovano na kolektivnom ograničenju i ponderiranoj metodi kombinacijeIzvorni znanstveni članak Ispitivanje pouzdanosti softvera znači ispitivanje softvera kako bi se provjerilo da li udovoljava zahtjevima pouzdanosti i kako bi se procijenio njegov stupanj pouzdanosti. Statistički temeljeno ispitivanje pouzdanosti softvera općenito uključuje tri dijela: izgradnju modela, generiranje ispitnih podataka i ispitivanje. Stvaranje modela upotrebe softvera treba što je više moguće odražavati korisnikovu stvarnu primjenu. Potreban je ogroman broj ispitivanih slučajeva da bi se zadovoljila distribucija vjerojatnoće u slučaju stvarne upotrebe; inače će ispitivanje pouzdanosti izgubiti originalno značenje. U ovom radu najprije predlažemo novu metodu strukturiranja modela primjene softvera zasnovanu na modulima i heurističkoj metodi koja se temelji na ograničenjima. Zatim predlažemo metodu za generiranje podataka za ispitivanje uzimajući u obzir kombinaciju i težinu ulaznih podataka što smanjuje veliki broj mogućih kombinacija ulaznih varijabli na samo nekoliko reprezentativnih i povećava praktičnost primjene ispitne metode. U svrhu provjere učinkovitosti metode predložene u ovom radu, organizirane su četiri grupe eksperimenata. Ispravnost odgovarajućeg indeksa (GFI-goodness of fit index) pokazuje da je predložena metoda bliža upotrebi aktualnog softvera; također smo ustanovili da ima bolju pokrivenost kod uporabe Java Pathfinder-a za analizu četiri niza pokrivenosti internog koda.

show abstract

“…Bertrand Meyer proposed 'design by contract' [37] as the form appropriate to reusable components. A version specifically directed at components-based system design and the possible need to modify the pre-and post-conditions of contracts is being investigated by Reussner and Schmidt [42,44].…”

Section: Proof-based and Analytical Theoriesmentioning

confidence: 99%

Software component composition: a subdomain‐based testing‐theory foundation

Hamlet

2007

Software Testing Verif & Rel

View full text Add to dashboard Cite

Composition of software elements into assemblies (systems) is a fundamental aspect of software development. It is an important strength of formal mathematical specification that the descriptions of elements can be precisely composed into the descriptions of assemblies. Testing, on the other hand, is usually thought to be "non-compositional." Testing provides information about any executable software element, but testing descriptions have not been combined to describe assemblies of elements. The underlying reason for the compositional deficiency of testing is that tests are samples. When two elements are composed, the input samples (test points) for the first lead to an output sample, but it does not match the input test points of the second, following element.The current interest in software components and component-based software development (CBSD) provides an ideal context for investigating elements and assemblies. In CBSD, the elements (components) are analyzed without knowledge of the system(s) to be later assembled. A fundamental testing theory of component composition must use measured component properties (test results) to predict system properties.This paper proposes a testing-based theory of software component composition based on subdomains. It shows how to combine subdomain tests of components into testing predictions for arbitrarily complex assemblies formed by sequence, conditional, and iteration constructions. The basic construction of the theory applies to functional behavior, but the theory can also predict system non-functional properties from component subdomain tests. Compared to the alternative of actually building and testing a system, the theoretical predictions are computationally more efficient. The theory can also be described as an exercise in modeling. Components are replaced by abstractions derived from testing them, and these models are manipulated to model system behavior.

show abstract

Reliability prediction for component-based software architectures

Cited by 230 publications

References 10 publications

Using Hierarchical Scenarios to Predict the Reliability of Component-Based Software

Using Hierarchical Scenarios to Predict the Reliability of Component-Based Software

Large scale software test data generation based on collective constraint and weighted combination method

Software component composition: a subdomain‐based testing‐theory foundation

Contact Info

Product

Resources

About