Resourceful Systems for Fault Tolerance, Reliability, and Safety

ACM Computing Surveys (CSUR)

Volumn 22, Issue 1, 1990, Pages 35-68

  Abbott, Russell J ^a  

^a AEROSPACE CORPORATION   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

COMPUTER PROGRAMMING;

LOGIC PROGRAMMING; N-VERSION PROGRAMMING; OBJECT-ORIENTED PROGRAMMING; RESOURCEFUL SYSTEMS; SOFTWARE FAULT TOLERANCE; SOFTWARE SAFETY;

COMPUTER SOFTWARE;

EID: 0025402475     PISSN: 03600300     EISSN: 15577341     Source Type: Journal    
DOI: 10.1145/78949.78951     Document Type: Article

References (54)

1. ABBOTT, R. J. 1986. An Integrated Approach to Software Development. John Wiley & Sons, New York.
2. AGRE, P. E., AND CHAPMAN, D. 1987. Pengi: An implementation of a theory of activity. In Proceedings of AAAI 87. American Association for Artificial Intelligence, pp. 268-272.
3. ANDERSON, T. 1985. Resilient Computing Systems, vol. I. John Wiley & Sons, New York.
4. ANDERSON, T., AND LEE, P. A. 1981. Fault Tolerance Principles and Practice. Prentice/Hall International, London.
5. AVIZIENIS, A. 1985a. Fault-tolerant computer systems. Class notes. Univ. of California, Los Angeles.
6. AVIZIENIS, A. 1985b. The N-version approach to fault-tolerant software. IEEE Trans. Softw. Eng. SE-11, 12 (Dec.), 1491-1501.
7. AVIZIENIS, A., AND KELLY, N. J. 1984. Fault Tolerance by design diversity:Concepts and experiments. IEEE Comput. 17, 8 (Aug.), 67-80.
8. AVIZIENIS, A., AND LAPRIE, J. C. 1986. Dependable computing: From concepts to design diversity. Proc. IEEE 74, 5 (May), 629-638.
9. BARSTOW, D. R. 1985. Domain-specific automatic programming. IEEE Trans. Softw. Eng. SE-11, 11 (Nov.), 1321-1336.
10. BASTANI, F. B., AND YEN, I. L. 1985. Analysis of an inherently fault tolerant program. In Proceedings of COMPSAC 85. IEEE Computer Society, pp. 428-436.
11. BERLINER, H. 1980. Computer backgammon. Scientific American (June).
12. BISHOP, P. G., ESP, D. G., AND BARNES, M., HUMPHREYS, P., DAHLL, G., AND LAHTI, J. 1986. PODS: A project on diverse software. IEEE Trans. Softw. Eng. SE-12, 9 (Sept.), 929-940.
13. BOLOGNA, S., AND LEVESON, N. G. 1986. Special issue on reliability and safety in real-time process control. IEEE Trans. Softw. Eng. SE-12, 9 (Sept.), 877-996.
14. BOWEN, T. P., WIGLE, G. B., AND TSAI, J. T. 1985. Specification of software quality attributes. Tech. Rep. RADC-TR-85-37, Rome Air Development Center.
15. BROOKS, F. P., JR. 1987. No silver bullet: Essence and accidents of software engineering. IEEE Comput. 20, 4 (Apr.), 10-19.
16. CHA, S. D., KNIGHT, J. C., LEVESON, N. G., AND SHIMEALL, T. J. 1987. An empirical study of software error detection using self-checks. In Digest of Papers FTCS-17:17th Annual Symposium on Fault Tolerant Computing. IEEE Computer Society, (July 1987), pp. 156-161.
17. CHAPMAN, D. 1985. Planning for conjunctive goals. Tech. Rep. TR 802, MIT Artificial Intelligence Laboratory.
18. DALE, C. J. 1982. Software reliability evaluation methods. Tech. Rep. ST-26750, British Aerospace Dynamics Group.
19. DENNING, P. J. 1976. Fault-tolerant operating systems. Comput. Surv. 8, 4 (Dec.), 359-389.
20. FLOYD, R. W. 1967. Assigning meaning to programs. In Proceedings of the Symposia on Applied Mathematics (Providence, R.I.), vol. 19, American Mathematics Society, pp. 19-32.
21. FREY, P. W. 1977. Chess Skill in Man and Machine. Springer-Verlag, Berlin.
22. GEORGEFF, M. P., AND LANSKY, A. L. 1987. Reactive reasoning and planning. In Proceedings of AAAI 87. American Association for Artificial Intelligence, pp. 677-682.
23. GILLEY, G. C. 1987. Architectural design methods of transient fault protection. In Proceedings of AIAA Computers in Aerospace VI Conference. AIAA, pp. 78-82.
24. GOEL, A. L. 1985. Software reliability models: Assumptions, limitations, and applicability. IEEE Trans. Softw. Eng. SWE-11, 12 (Dec.), 1411-1423.
25. GOEL, A. L., AND BASTANI, F. B. 1985. Special issue on software and reliability. IEEE Trans. Softw. Eng. SE-11, 1 (Dec.), 1490-1577.
26. GOEL, A. L., AND BASTANI, F. B. 1986. Special issue on software reliability. IEEE Trans. Softw. Eng. SE-12, 12 (Jan.), 1-182.
27. GRAY, J. 1986. Why do computers stop and what can be done about it? In Proceedings of the 5th Symposium on Reliability and Distributed Software and Database Systems. IEEE Computer Society, pp. 3-12.
28. HAMMING, R. W.1950. Error detecting and error correcting codes. Bell Syst. Tech. J. 26, 4 (Apr.), 147-160.
29. HECHT, H. 1976. Fault-tolerant software for real-time applications. Comput. Surv. 8, 4 (Dec.), 391-409.
30. HORNING, J. J. ET AL. 1974. A program structure for error detection and recovery. In Lecture Notes in Computer Science 16, E. Gelenbe and C. Kaiser, Eds. Springer-Verlag, Berlin, pp. 171-187.
31. JELINSKI, Z., AND MORANDA, P. B. 1972. Software reliability research. In Statistical Computer Performance Evaluation, Freiberger, Ed. Academic Press, New York, pp. 485-502.
32. KEILLER, P. A., LITTLEWOOD, B., MILLER, D. R., AND SOFER, A. 1983. Comparison of software reliability predictions. In Digest of the 13th International Symposium on Fault-Tolerant Computing, IEEE Computer Society, pp. 128-143.
33. KNIGHT, J. C., AND LEVESON, N. G. 1986. An experimental evaluation of the assumption of independence in multiversion programming. IEEE Trans. Softw. Eng. SE-12, 1 (Jan.), 96-109.
34. KOVED, L., AND WALDBAUM, G. 1986. Improving availability of software subsystems through online error detection. IBM Syst. J. 25, 1 (Jan.), 96-109.
35. LEVESON, N. G. 1986. Software safety: Why, what and how. Computing Surveys 18, 2 (June), 125-163.
36. LINDEN, T. A. 1976. Operating system structures to support security and reliable software. Comput. Surv. 8, 4 (Dec.), 409-445.
37. LITTLEWOOD, B., AND VERRLL, J. L. 1973. A Bayesian reliability growth model for computer software. J. Roy. Stat. Soc. C 22 (Sept.), 332-346.
38. LUCKHAM, D., AND VON HENKE, E. W. 1984. An overview of Anna, a specification language for Ada. Tech. Rep. 84-265, Stanford Computer Systems Laboratory.
39. MOSTOW, J. Ed. 1985. Special issue on artificial intelligence and software engineering. IEEE Trans. Softw. Eng. SE-11, 11 (Nov.), 1257-1351.
40. MUSA, J. D. 1975. A theory of software reliability and its application. IEEE Trans. Softw. Eng., SE-1, 9 (Sept.), 312-327.
41. NEUMANN, P. G. 1986. On hierarchical design of computer systems for critical applications. IEEE Trans. Softw. Eng. SE-12, 9 (Sept.), 905-920.
42. NILSSON, N. J. 1980. Principles of Artificial Intelligence. Tioga, Palo Alto.
43. PARTSCH, H., AND STEINBRUGGEN, R. 1983. Program transformation systems. ACM Comput. Surv. 15, 3 (Sept.), 199-236.
44. RANDELL, B. 1977. System structuring for software fault tolerance. In Current Trends in Programming Methodology, R. T. Yeh, Ed. Prentice-Hall, Englewood Cliffs, N.J., pp. 195-219.
45. RENNELS, D. A. 1984. Fault-tolerant computing-Concepts and examples. IEEE Trans. Comput. C-33, 12 (Dec.), 1116-1129.
46. SEVIORA, R. E. 1987. Knowledge-based program debugging systems. IEEE Softw. 4, 3 (May), 20-32.
47. SHOOMAN, M. 1973. Operational testing and software reliability during program development. In Proceedings of the IEEE Symposium on Computer Software Reliability (New York), IEEE Computer Society, pp. 51-57.
48. STERLING, L., AND SHAPIRO, E. 1986. The Art of Prolog. MIT Press, Cambridge, Mass.
49. STOTT, C. B. 1987. Review of resilient computing systems: vol. I. IEEE Computer 20, 6 (June), 117-118.
50. STROM, R. E., AND YEMINI, S. 1986. Typestate: A programming language concept for enhancing software reliability. IEEE Trans. Softw. Eng. SE-12, 1 (Jan.), 157-171.
51. TAYLOR, J. R. 1982. An integrated approach to the treatment of design and specification errors in
52. TAYLOR, D. J., AND BLACK, J. P. 1982. Principles of data structure error correction. IEEE Trans. Comput. C-31, 7 (July), 602-608.
53. TAYLOR, D. J., AND SEGER, C.-J. H. 1986. Robust storage structures for crash recovery. IEEE Trans. Comput. C-35, 4 (Apr.), 288-295.
54. TAYLOR, D. J., MORGAN, D. E., AND BLACK, J. P. 1980. Redundancy in data structures: Improving software fault tolerance. IEEE Trans. Softw. Eng. SE-6, 1 (Nov.), 585-594.