Software reliability-engineered testing

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.