Software reliability analysis: a systems development model

  • Authors:
  • Bahador Ghahramani

  • Affiliations:
  • Information Systems and Quantitative Analysis, College of Information Science and Technology, University of Nebraska at Omaha, Omaha, NE

  • Venue:
  • Computers and Industrial Engineering - Special issue: Selected papers from the 25th international conference on computers & industrial engineering in New Orleans, Louisiana
  • Year:
  • 2003

Quantified Score

Hi-index 0.00

Visualization

Abstract

Implementation and utilization of the software reliability analysis model (SRAM) provides analysts, software engineers, and systems analysts and developers (SA&D) the means to predict, estimate, and measure rate-of-failure occurrences in software (including firmware). Rate-of-failure measures are understandable to system users. By implementing the SRAM in the content of software engineering, SA&D can: (1) analyze, manage, and improve the reliability of their systems; (2) balance users' needs for competitive price, product reliability, and timely delivery; (3) determine when the software is ready to be released to the users, thereby minimizing the risks of releasing software with serious problems; and (4) avoid excessive time-to-market of the system due to system overtesting. Although the SRAM uses sophisticated statistical concepts, available software tools allow SA&D and developers to readily apply the model without difficulties.