Free Access
RAIRO-Oper. Res.
Volume 19, Number 1, 1985
Page(s) 87 - 104
Published online 06 February 2017
  • 1. L. J. BAIN, Statistical Analysis of Reliability and Life-Testing Models, Marcel Dekker, Inc., New York, 1978. [MR: 515724] [Zbl: 0419.62076] [Google Scholar]
  • 2. L. H. CROW, On Tracking Reliability Growth, Proc. 1975 Annu. Reliability and Maintainability Symp., 1975, pp. 438-443. [Google Scholar]
  • 3. J. T. DUANE, Learning Curve Approach to Reliability Monitoring, I.E.E.E. Trans. Aerosp., Vol. 2, 1964, pp. 563-566. [Google Scholar]
  • 4. A. L. GOEL, Software Error Detection Model with Applications, J. Syst. Software, Vol. 1, 1980, pp. 243-249. [Google Scholar]
  • 5. A. L. GOEL and K. OKUMOTO, Time-Dependent Error-Detection Rate Model for Software Reliability and Other Performance Measures, I.E.E.E. Trans. Reliab., Vol. R-28, 1979, pp. 206-211. [Zbl: 0409.68009] [Google Scholar]
  • 6. Z. JELINSKI and P. B. MORANDA, Software Reliability Research, in Statistical Computer Performance Evaluation, W. FREIBERGER, Ed., Academic Press, New York, 1972, pp. 465-484. [Google Scholar]
  • 7. W. KREMER, Birth-Death and Bug Counting, I.E.E.E. Trans. Reliab., Vol R-32, 1983, pp. 37-47. [Zbl: 0511.60087] [Google Scholar]
  • 8. B. LITTLEWOOD, Theories of Software Reliability: How Good Are They and How Can They Be Improved?, I.E.E.E. Trans. Software Eng., Vol. SE-6, 1980, pp. 489-500. [Google Scholar]
  • 9. P. B. MORANDA, Event-Altered Rate Models for General Reliability Analysis, I.E.E.E. Trans. Reliab., Vol.R-28, 1979, p. 376-381. [Zbl: 0418.62081] [Google Scholar]
  • 10. J. D. MUSA, Software Reliability Measurement, J. Syst. Software, Vol. 1, 1980, p. 223-241. [Zbl: 1160.68348] [Google Scholar]
  • 11. W. NELSON, Applied Life Data Analysis, John Wiley and Sons, Inc., New York, 1982. [MR: 646615] [Zbl: 1054.62109] [Google Scholar]
  • 12. M. OHBA and M. KAJIYAMA, Inflection S-shaped Software ReiiabUity Growth Model (in Japanese), I.RS.-Japan Proc. W.G.S.E. Meeting, Vol. 28, 1983. [Google Scholar]
  • 13. C. V. RAMAMOORTHY and F. B. BASTANI, Software Reliability - Status and Perspectives, I.E.E.E. Trans. Software Eng., Vol. SE-8, 1982, p. 354-371. [Google Scholar]
  • 24. S. M. Ross, Stochastic Processes, John Wiley and Sons, Inc., New York, 1983. [MR: 683455] [Zbl: 0888.60002] [Google Scholar]
  • 15. G. J. SCHICK and R. W. WOLVERTON, An Analysis of Competing Software Reliability Models, I.E.E.E. Trans. Software Eng., Vol. SE-4, 1978, pp. 104-120. [Zbl: 0381.68036] [Google Scholar]
  • 16. J. G. SHANTHIKUMAR, A State- and Time-Dependent Error Occurrence-Rate Software Reliability Model with Imperfect Debugging, Proc. 1981 Nat. Comput. Conf., 1981, pp. 311-315. [Google Scholar]
  • 17. M. L. SHOOMAN, Software Reliability: Measurement and Models, Proc. 1975 Annu. Reliability and Maintainability Symp., 1975, pp. 485-491. [Zbl: 1160.68348] [Google Scholar]
  • 18. W. A. Jr. THOMPSON, On The Foundations of Reliability, Technometrics, Vol. 23 1981, pp. 1-13. [MR: 604905] [Zbl: 0459.60077] [Google Scholar]
  • 19. S. YAMADA and S. OSAKI, Software Reliability Growth Models and Their Comparisons (in Japanese), Trans. I.E.C.E. Japan, Vol. J65-D, 1982, pp. 906-912; also Systems. Computers. Controls, Vol. 13, 1982, pp. 42-49. [Google Scholar]
  • 20. S. YAMADA and S. OSAKI, Reliability Growth Models for Hardware and Software Systems Based on Nonhomogeneous Poisson Processes: A Survey, Microelectron. Reliab., Vol. 23, 1983, pp. 91-112. [Google Scholar]
  • 21. S. YAMADA and S. OSAKI, S-shaped Software Reliability Growth Models with Four Types of Software Error Data, Int.J. Systems Sci., Vol. 14, 1983, pp. 683-692. [Zbl: 0506.62081] [Google Scholar]

Current usage metrics show cumulative count of Article Views (full-text article views including HTML views, PDF and ePub downloads, according to the available data) and Abstracts Views on Vision4Press platform.

Data correspond to usage on the plateform after 2015. The current usage metrics is available 48-96 hours after online publication and is updated daily on week days.

Initial download of the metrics may take a while.