Operational profiles in software-reliability engineering

Musa, Donald

doi:10.1109/52.199724

Cited by 644 publications

(364 citation statements)

References 3 publications

Supporting

Mentioning

360

Contrasting

Unclassified

Order By: Relevance

“…The Markov usage model (UM) can describe software usage scenario easily, its definition can be found in [7,8,9]. Researchers have proposed many kinds of methods of structuring usage model, which can be summarized to the following methods [9,10,11]: Musa's Method, based on expert experiences, historical data and complex software model.…”

Section: Usage Models 21 Structuring the Usage Modelmentioning

confidence: 99%

“…Researchers have proposed many kinds of methods of structuring usage model, which can be summarized to the following methods [9,10,11]: Musa's Method, based on expert experiences, historical data and complex software model. Musa's method is only a guiding thought of structuring usage model and lacks a specific implementation.…”

Section: Usage Models 21 Structuring the Usage Modelmentioning

confidence: 99%

“…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. Researchers have proposed many kinds of methods of structuring usage model, which can be summarized to the following methods: Musa's Method [9], based on expert experiences [11], historical data and complex software model [16]. Musa's method is only a guiding thought of structuring usage model lacking a specific implementation.…”

Section: Relation Work 51 the Construction Of Software Usage Modelmentioning

confidence: 99%

“…Musa's method is only a guiding thought of structuring usage model lacking a specific implementation. The method of [9] is quite simple and cannot be applied to complex software. The method of [11] cannot reflex calling relation and constraint relation among modules.…”

Section: Relation Work 51 the Construction Of Software Usage Modelmentioning

confidence: 99%

See 3 more Smart Citations

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

Section: Usage Models 21 Structuring the Usage Modelmentioning

confidence: 99%

Section: Usage Models 21 Structuring the Usage Modelmentioning

confidence: 99%

Section: Relation Work 51 the Construction Of Software Usage Modelmentioning

confidence: 99%

Section: Relation Work 51 the Construction Of Software Usage Modelmentioning

confidence: 99%

See 2 more Smart Citations

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

2017

View full text Add to dashboard Cite

show abstract

“…In software reliability engineering (SRE), subdomains are used in a way that is close to the present purpose. In SRE, functional subdomains are assigned empirical usage probabilities, thus defining a coarse usage profile for a system [39]. Imagining that such a profile will be applied to a component-based system, part of the component-testing dilemma is resolved.…”

Section: Dilemma Of Varying Software Behaviormentioning

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

Which Software Modules have Faults which will be Discovered by Customers?

Khoshgoftaar¹,

Allen²,

Jones³

et al. 1999

J. Softw. Maint: Res. Pract.

View full text Add to dashboard Cite

Software is the medium for implementing increasingly sophisticated features during the maintenance phase as successive releases are developed. Software quality models can predict which software modules are likely to have faults that will be discovered by customers. Such models are key components of a system such as Enhanced Measurement for Early Risk Assessment of Latent Defects (EMERALD). It is a sophisticated system of decision support tools used by software designers and managers at Nortel to assess risk and improve software quality and reliability of legacy software systems. This paper reports an approach to software quality modelling that is suitable for industrial systems such as EMERALD. We conducted a case study of a large legacy telecommunications system in the maintenance phase to predict whether each module will be considered fault‐prone. The case study is distinctive in the following respects. (1) Fault‐prone modules were defined in terms of faults discovered by customers, which represent only a small fraction of the modules in the system. (2) We developed models based on software product and process metrics that can make useful predictions at the end of the coding phase and at the time of release. (3) The modelling approach is suitable for very large systems. We anticipate that refinements of this case study's models will be incorporated into EMERALD. A similar approach could be taken for other systems. Copyright © 1999 John Wiley & Sons, Ltd.

show abstract

Operational profiles in software-reliability engineering

Cited by 644 publications

References 3 publications

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

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

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

Which Software Modules have Faults which will be Discovered by Customers?

Contact Info

Product

Resources

About