[11] P. Jalote and Y. R. Muralidhara, “A coverage based model for software reliability estimation,”

Proceedings of First International Conference on Software Testing, Reliability and Quality Assurance,

1994, pp. 6 –10 (IEEE)

[JM94] There exist many models for estimating and predicting the reliability of software systems, most

of which consider a software system as a black box and predict the reliability based on the failure data

observed during testing. In this paper a reliability model based on the software structure is proposed.

The model uses the number of times a particular module is executed as the main input. A software

system is modeled as a graph, and the reliability of a node is assumed to be a function of the number of

times it gets executed during testing – the larger the number of times a node gets executed, the higher

its reliability. The reliability of the software system is then computed through simulation by using the

reliabilities of the individual nodes.

Question: Method/Means

Result: Technique

Validation: Analysis

18

Question: Method/Means:

Result: Technique

Validation: Analysis

[15] S. Redwine & W. Riddle, “Software technology maturation,” Proceedings of the Eighth International

Conference on Software Engineering, May 1985, pp. 189-200

[RR85] In this paper, a variety of software technologies are reviewed. The technology maturation

process by which a piece of technology first gets the idea formulated and preliminarily used, then is

developed and extended into a broader solution, and finally is enhanced to product-quality applications

and marketed to the public. The time required for a piece of technology to mature is studied, and the

actions that can accelerate the maturation process are addressed. This paper serves as a very good

framework for technology maturation study.

Question: Characterization

Result: Empirical Model

Validation: Analysis

[16] S. Rapps and E. J. Weyuker, “Selecting Software Test Data Using Data Flow Information,” IEEE