Reliability Issues in Computing System Design

ACM Computing Surveys (CSUR)

Volumn 10, Issue 2, 1978, Pages 123-165

  Randell, B ^a   Lee, P ^a   Treleaven, P C ^a  

^a NEWCASTLE UNIVERSITY   (United Kingdom)

Author keywords

error; failure; fault; fault avmdance; fault tolerance; hardware reliability; software reliability; system structure

Indexed keywords

COMPUTER PROGRAMMING - RELIABILITY;

COMPUTER SYSTEMS, DIGITAL;

EID: 0017983255     PISSN: 03600300     EISSN: 15577341     Source Type: Journal    
DOI: 10.1145/356725.356729     Document Type: Article

References (51)

1. Anderson, T.; and Kerr, R. “Recovery blocks in action: a system supporting high reliability,” in Proc. Int Conf. Software Engineering, 1976.
2. Anderson, T.; Lee, P. A.; and Shrivastava, S. K. A model of recoverability in multi-level systems, Tech. Rep 115, Computing Laboratory, Univ. Newcastle upon Tyne, UK, Nov. 1977. To appear in IEE Trans. Softw Eng.
3. Avizienis, A. et al. “The STAR (self testing and repairing) computer an investigation of the theory and practice of fault tolerant computer design,” IEEE Trans. Comput. C-20, 11 (Nov. 1971), 1312-1321.
4. Avizienis, A.; and Rennels, D. A. “Fault tolerance experiments with the JPL-STAR computer,” IEEE COMPCON 72, IEEE, New York, 1972, pp. 321-324.
5. Avizienis, A “Fault-tolerant systems.” IEEE Trans. Comput C-25, 12 (Dec. 1976), 1304-1312.
6. Baskin, H. B.; Borgerson, B. R.; and Roberts, R. “PRIME—a modular architecture for terminal-orientated systems,” in Proc. 1972 AFIPS Spring Jt. Computer Conf, Vol. 40, AFIPS Press, Montvale, N.J., pp. 431-437.
7. Bell Syst. Tech. J., (Sept. 1964).
8. Bell Syst. Tech. J., (Feb. 1977).
9. Bjork, L. A.; and Davies, C. T. The semantics of the preservation and recovery of integrity in a data system, Rep. TR 02.540, IBM, San Jose, Calif., Dec. 1972.
10. Bjork, L. A. Generalised audit trail (ledger) concepts for data base applications, Rep. TR 02.641, IBM, San Jose, Calif., Sept. 1974.
11. Borgerson, B. R. “A fail-softly system for timesharing use,” Digest of papers FTC-2, 1972, pp. 89-93.
12. Borgerson, B. R. “Spontaneous reconfiguration in a fail-softly computer utility,” Datafair (1973), 326-331.
13. Clement, C. F., and Toyer, R. D. “Recovery from faults in the No. 1A processor,” FTC-4, 1974, pp 5.2-5.7.
14. Davies, C. T. A recovery/integrity architecture for a data system, Rep. TR 02.528, IBM, San Jose, Calif., May 1972.
15. Denning, P. J. “Fault-tolerant operating systems,” Comput. Surv.8, 4 (Dec. 1976), 359-389.
16. Dijkstra, E. W. “The structure of the ‘THE’-multiprogramming system,” Commun. ACM 11, 5 (May 1968), 341-346.
17. Dijkstra, E. W. A discipline of programming, Prentice-Hall, Inc., Englewood Cliffs, N.J., 1976.
18. Edelberg, M. “Data base contamination and recovery,” in Proc. ACM SIG-MOD Workshop Data Description, Access and Control, 1974, ACM, New York, pp. 419-430.
19. Elspas, B.; Levitt, K. N., Waldinger, R J.; and Waksman, A “An assessment of techniques for proving program correctness,” Comput. Surv. 4, 2 (June 1972), 97-147.
20. Eswaran, K. P.; Gray, J. N., Lorie, R. A., and Traiger, I. L. “The notions of consistency and predicate locks in a database system,” Commun. ACM 19, 11 (Nov. 1976), 624-633.
21. Fabry, R S “Dynamic verification of operating system decisions,” Commun. ACM 16, 11 (Nov 1973), 659-668.
22. Fosdick, L. D., and Osterweil, L. J. “Data flow analysis in software reliability,” Comput. Surv.8, 3 (Sept. 1976), 305-330.
23. Goodenough, J. B. “Exception handling issues and a proposed notation,” Commun. ACM 18, 12 (Dec. 1975), 683-696.
24. Gray, J. N.; Lorie, R. A.; Putzolu, G. R.; and Traiger, L. L. Granularity of locks and degrees of consistency in a shared database, IBM Research Rep. RJ1654, Sept. 1975.
25. Gray, J. N. Private communication.
26. Hantler, S. L., and King, J. C. “An introduction to proving the correctness of programs,” Comput. Surv. 8, 3 (Sept. 1976), 331-353.
27. Heart, F. E.; Ornstein, S. M., Crowther, W. R., and Barker, W. B. “A new minicomputer/multiprocessor for the ARPA network,” in Proc. 1973 AFIPS Natl. Computer Conf, Vol 42, AFIPS Press, Montvale, N.J., pp. 529-537.
28. Horning, J.; Lauer, H C.; Melliar-Smith, P. M.; and Randell, B. “A program structure for error detection and recovery,” in Proc. Conf. Operating Systems; Theoretical and Practical Aspects. IRIA, 1974, pp. 177-193.
29. Horning, J.; Lauer, H C.; Melliar-Smith, P. M.; and Randell, B. “A program structure for error detection and recovery,” Lecture notes in computer science, Vol. 16, Springer-Verlag, New York.
30. Lampson, B.; and Sturgis, H. Crash recovery in a distributed data storage system, Computer Science Laboratory, Xerox Palo Alto Research Center, Palo Alto, Calif., 1976.
31. Levin, R. “Program structures for exception condition handling,” PhD Thesis, Carnegie-Mellon Univ., Pittsburgh, Pa, June 1977.
32. Lomet, D. B. “Process structuring, synchronisation and recovery using atomic actions,” in Proc. ACM Conf. Language Design for Reliable Software, SIGPLAN Notices 12, 3 (March 1977), 128-137.
33. London, R. L. “A view of program verification,” in Proc. Int. Conf. Reliable Software, 1975, ACM, New York, pp. 534-545.
34. McPhee, W S “Operating system integrity in OS/VS2,” IBM Syst. J. 13, 3 (1974), 230-252.
35. Melliar-Smith, P. M.; and Randell, B. “Software reliability: the role of programmed exception handling,” in Proc. ACM Conf. Language Design for Reliable Software, SIGPLAN Notices 12, 3 (March 1977), 95-100.
36. Merlin, P. M.; and Randell, B. Consistent state restoration in distributed systems, Tech. Rep. 113, Computing Laboratory, Univ. Newcastle upon Tyne, UK, Oct. 1977.
37. Naur, P. “Software reliability,” in Infotech State of the Art Conf. Reliable Software, 1977, Infotech International Ltd., Maidenhead, UK, pp. 7-13.
38. Neumann, P. G.; Goldberg, J.; Levitt, K. N.; and Wensley, J. H. A study of fault-tolerant computing, Stanford Research Inst., Menlo Park, Calif., July 1973.
39. Ornstein, S. M.; Crowther, W. R.; Kraley, M. F.; Bressler, R. D.; Michael, A., and Heart, F. E. “Pluribus a reliable multi-processor,” in Proc 1975 AFIPS Natl. Computer Conf., Vol. 44, AFIPS Press, Montvale, N.J., pp. 551-559.
40. Parnas, D. L.; and Wurges, H. “Response to undesired events in software systems,” in Proc. Int. Conf. Software Engineering, 1976, pp. 437-446.
41. Randell, B. “System structure for software fault tolerance,” IEEE Trans. Softw Eng. SE-1, 2 (June 1975), 220-232.
42. Randell, B., Lee, P. A.; and Treleaven, P. C. “Reliable computing systems,” to appear in Lecture notes in computer science, Springer-Verlag, New York.
43. Rohr, J. A. “Starex self-repair routines software recovery in the JPL-STAR computer”, Digest of papers FTC-3, 1973, pp. 11-16.
44. Russel, D. L. State restoration amongst communicating processes, Tech. Rep. 112, Digital Systems Laboratory, Stanford Univ., Stanford, Calif., June 1976.
45. Shooman, M. L. Probabilistic reliability; an engineering approach, McGraw-Hill, Inc, New York, 1968.
46. Shrivastava, S. K.; and Banatre, JP. “Reliable resource allocation between unreliable processes,” to appear in IEEE Trans. Softw Eng.(Also published as Tech. Rep. 99, Computing Laboratory, Univ Newcastle upon Tyne, UK, June 1977.
47. Verhofstad, J. S. M. “Recovery and crash resistance in a filing system,” in Proc. SIGMOD Conf., 1977, ACM, New York, pp. 158-167.
48. Verhofstad J. S. M. “The construction of recoverable multi-level systems,” PhD Thesis, Univ. Newcastle upon Tyne, UK, Aug. 1977.
49. Wasserman, A. I. Procedure-oriented exception handling, Medical Information Science, Univ. California, San Francisco, Calif., 1976.
50. Wensley, J. H. “SIFT software implemented fault tolerance,” in Proc. 1972 AFIPS Fall Jt. Computer Conf., Vol. 41, Part I, AFIPS Press, Montvale, N.J., pp. 243-253.
51. Wulf, W. A. “Reliable hardware-software architecture.” in Proc. Int. Conf. Reliable Software; SIGPLAN Notices 10, 6 (June 1975), 122-130.