Software reliability-engineered testing

• Published in: Computer (Long Beach, Calif.) Vol. 29; no. 11; pp. 61 - 68
• Main Author: Musa, J.D.
• Format: Journal Article
• Language: English
• Published: New York IEEE 01.11.1996; The Institute of Electrical and Electronics Engineers, Inc. (IEEE)
• Subjects: Application software; Automatic testing; Certification; Hardware; Life testing; Product testing; Reliability engineering; Software; Software systems; Software testing; System testing; Systems engineering and theory
• ISSN: 0018-9162; 1558-0814
• DOI: 10.1109/2.544239

Software testing often results in delays to market and high cost without assuring product reliability. Software reliability engineered testing (SRET), an AT&T best practice, carefully engineers testing to overcome these weaknesses. The article describes SRET in the context of an actual project at AT&T, which is called Fone Follower. The author selected this example because of its simplicity; it in no way implies that SRET is limited to telecommunications systems. SRET is based on the AT&T Best Current Practice of Software Reliability Engineering, approved in May 1991. Qualification as an AT&T best current practice requires use on typically eight to 10 projects with documented large benefit/cost ratios, as well as a probing review by two boards of high level managers. Some 70 project managers also reviewed this particular practice. Standards for approval as a best current practice are high; only five of 30 proposed best current practices were approved in 1991.