[go: up one dir, main page]
More Web Proxy on the site http://driver.im/ skip to main content
article
Free access

Computer system reliability and nuclear war

Published: 01 February 1987 Publication History

Abstract

Given the devastating consequences of nuclear war, it is appropriate to look at current and planned uses of computers in nuclear weapons command and control systems, and to examine whether these systems can fulfill their intended roles.

References

[1]
Adams, }.A. and Fischetti, M.A. *STAR WARS*-SDI: The grand experiment. IEEE Spectrum 22, 9 (Sept. 1985), 34-64.
[2]
Ad&n, W.R., Bran&d. M.A., and Cherniavsky, J.C. Validation, verification, and testing of computer software. ACM Comput. SWV. 14,2 (June 1982). 159-192.
[3]
Albright. J. False missile alert required 3 minutes to cancel. San Jose Mercury (June 15. 1980), 1 H.
[4]
American Academy of Arts and Sciences. Weapons in space. Vol. I: Concepts and technologies. Daedalus 114, 2 (Spring 1985), 9-189.
[5]
Anderson, T., and Randell, B. Eds. Computing Systems Reliability: An Advanced Course. Cambridge University Press, Cambridge, Mass., 1979.
[6]
Angus, I.E. The application of software reliability models to a major C31 system. In Proceedings of the Am~al Reliability and Mainfainabilify Symposium (San Francisco, Calif., Ian. 24-26). IEEE Press. New York, 1984. pp. 268-274.
[7]
Arkin, W.M. Nuclear weapon command, control, and communications. In World Armanrenrs and Disarmament: SIPRI Yearbook 1984, F. Blackaby. Ed. Taylor and Francis, London, 1984, pp. 455-516.
[8]
Association for Computing Machinery. Proceedings of VERkshop III-A formal verification workshop. Sofno. Eng. Notes 10, 4 (1985).
[9]
Ball. Il. Can nuclear war be controlled? Adelphi Pap. 169. International Institute for Strategic Studies, London. 1981.
[10]
Ball, Il. The Soviet strategic C31 system. In C31 Handbook. EW Communications, Palo Alto, Calif. 1986. pp. 206-216.
[11]
Balzer, R., Cheatham. T.E. and Green, C. Software technology in the 1990's: Using a new paradigm. Cornpurer 16, 11 (Nov. 1983). 39-45.
[12]
Barstow. D.R., Shrobe. H.E., and Sandewall. E. Eds. Interactive Programming Environments. McGraw-Hill, New York, 1984.
[13]
Barstow. D.R. Domain-specific automatic programming. IEEE Trans. Softw. Eng. SE-II. 11 (Nov. 1985), 1321-1336.
[14]
Benzel, T.C.V., and Tavilla, D.A. Trusted software verification: A case study. In Proceedings of the 1985 Symposium on Security and Privacy (Oakland, Calif., Apr. 22-24). IEEE Press, New York, 1985, pp. 14-31.
[15]
Bereanu. B. Self-activation of the world nuclear weapons system. 1. Peace Res. 20, 1 (1983), 49-57.
[16]
Berkeley. EC. The Computer Revolution. Doubleday, New York, 1962.
[17]
Blair, B.G. Strategic Command and Control. Brookings Institution, Washington, D.C. 1985.
[18]
Bloomfield, L.P. Nuclear crisis and human frailty. Bull. At. Sci. 41. 9 (Oct. 1985). 26-30.
[19]
Boehm. B.W. Software Engineering Economics. Prentice-Hall, Englewood Cliffs. N.}., 1981.
[20]
Boyer, R.S., and Moore, IS., Eds. The Correctness Problem in Computer Science. Academic Press. New York, 1981.
[21]
Bracken, P. The Command and Control of Nuclear Forces. Yale University Press, New Haven. Corm., 1983.
[22]
Broad, W.J. Computers and the US. military don't mix. Science 207, 4436 {Mar. 14.1980). 1183-1187.
[23]
Broad, W.J. Nuclear pulse (I): Awakening to the chaos factor. Science 212,4498 (May 29, 1981). 1009-1012.
[24]
Broad, W.J. Nuclear pulse (II): Ensuring delivery of the doomsday signal. Science 212,4499 (June 5. 1981). 1116-1120.
[25]
Broad, W.J. Nuclear pulse (III): Playing a wild card. Science 212, 4500 (June 12.1981). 1248-1251.
[26]
Brooks, 1. NORAD computer systems are dangerously obsolete. House Rep. 97-449, Committee on Government Operations, United States House of Representatives, Washington, DC, Mar. 8, 1982.
[27]
Brown, H. Thinking about National Security: Defense and Foreign Policy itI a Dangerous World. Westview Press, Boulder, Cola., 1983.
[28]
Bunn. M., and Tsipis. K. The uncertainties of a preemptive nuclear attack. Sci. Am. 249, 5 (Nov. 19831, 38-47.
[29]
Burt, R. False nuclear alarms spur urgent effort to find faults. New York Times (june 13. 1980), A16
[30]
Carter, A.B. The command and control of nuclear war. Sci. Am. 252, 1 (Jan. 1985), 32-39.
[31]
Carter, W.C. Hardware fault tolerance. In Computing Systems Reliability: An Advanced Course, T. Anderson and B. Randell, Eds. Cambridge University Press, Cambridge, Mass., 1979. Chap. 6, pp. 211- 263.
[32]
Cockburn. A. The Threat: Amide the Soviet Military Machine. Random House, New York, 1983.
[33]
Comptroller General of the United States. The world wide military command and control system-Major changes needed in its automated data processing management apd direction. Rep. LCD-80-22, Comptroller General of the United Stales, Washington, DC., Dec. 14, 1979.
[34]
Comptroller General of the United States. NORAD's Missile Warning Syslem: What Went Wrottg? United States General Accounting Office, Washington, D.C., May 15. 1981.
[35]
Cooper, R.S. Letter to the editor. Bull. At. Sci. 41, 1 (ran. 1985). 54-5s.
[36]
Currit, P.A., Dyer, M. and Mills, H.D. Certifying the reliability of software. IEEE Trans. Sojtw. Eng. SE-12, 1 (Jan. 1986). 3-11.
[37]
Davis, N.C., and Goodman, S.E. The Soviet bloc's unified system of computers. ACM Compuf. Surv. 20, 2 (June 1978). 93-122.
[38]
Defense Advanced Research Projects Agency. Strategic Computing- New-Generafioo Conrpufilrg Technology: A Strategic Plan for its Development and Applicatzov to Critical Problems i,l Defeuse. U.S. Department of Defense, Arlington, Va. Oct. 28. 1983.
[39]
Defense Nuclear Agency. EMP Awareness Handbook. Defense Nuclear Agency, Washington, D.C., 1971.
[40]
Deutsch. MS. Software Verificafiorl and Validation: Realistic Project Approaches. Prentice-Hall, Englewood Cliffs. N.J., 1982
[41]
Doder. D. Soviets said to consider faster nuclear missile launch in crisis. Washington Post (Apr. 11. 19821, A5.
[42]
Doder. D. Kremlin defense official warns of policy shift to quicken nuclear response. Washington Post (July 13. 1982). Ala.
[43]
Druffel. L.E. Redwino. ST. and Riddle, W.E. The STARS program: Overview and rationale. Compufer 16, 11 (Nov. 19831, 21-29.
[44]
Dumas, L.J. Human fallibility dnd weapons. Bull. At. Sci. 36. 9 (Nov. 1980). 15-20.
[45]
Eastport Study Group. Summer Study 1985: A Keport to the Director, Strategic Defense Initiative Orgmlization. Strategic Defense Initiative Organization. Dec. 1985.
[46]
Emelyanov. VS. The possibility of an accidental nuclear war. In The Arms Race at a Time of Decision, J. Rotblat and A. Pascolini, Eds. Macmillan, New York, 1984. Chap. 9. pp. 73-79.
[47]
Fairley, R.E. Soffware Engineering Concepts. McGraw-Hill, New York, 1985.
[48]
Ford, D. The Bunon. Simon and Schuster, New York, 1985.
[49]
Fox, R. Sofnoare and Ifs Developme~~t. Prentice-Hall, Englewood Cliffs, N.J. 1982.
[50]
Frei, D. Risks of Uninte,~tiorml Nuclear War. Allanheld. Osmun and Co., Totowa, k.J., 1983.
[51]
Garman. J.R. The "bug" heard 'round the world. Sofrw. Eng. Notes 6, 5 (Oct. 1981). 3-10.
[52]
Garwin. R. Launch under attack to redress minuteman vulnerability? Inf. Sccur. 4. 3 (Winter 1979), 117-139.
[53]
Gelb, L.H. Soviet marshal warns the U.S. on its missiles. New York Times (Mar. 17. 1983). Al.
[54]
George, A., and Smoke, R. Deterrence in American Foreign Policy. Columbia University Press, New York, 1974.
[55]
Glasstone. S. and Dolan. P.J. The Effects of Nuclear Weapons. U.S. Department of Defense, Washington, D.C., 1977.
[56]
Goodman. SE. Computing and the development ot the Soviet cconomy. A Compendium of Papers Submitted to the Joint Economic Committee of the Congress of the United States, Washington. DC. Oct. 10, 1979.
[57]
Gray, C.S. and Payne, K. Victory is possible. Foreign Policy 39 (Summer 1980). 14-27.
[58]
Gumble, B. Air Force upgrading defenses at NORAD. Def. Electron. 17,8 (Aug. 1985). 86-108.
[59]
Halloran. R. U.S. aides recount moments of false missile alert. Nctv York Times (Dec. 16. 1979), 25.
[60]
Halloran. R. Computer error falsely indicates a Soviet attack. New York Times (June 6. 1980). 14.
[61]
Halloran. R. Pentagon draws up first strategy for fighting a long nuclear war. New York Times (May 30, 1982). 1:l.
[62]
Halloran. R. Weinberger confirms new strategy on atom war. New York Times (June 4. 1982). AlO.
[63]
Halloran, R. Shift of strategy on missile attack hinted by Weinberger and Vessey. New York Times (May 6, 1983), 1: 1.
[64]
Hart, G. and Goldwater. B. Recent False Alerts from the Nation's Missile Attack WarGg Sysfmr. United States Senate, Committee on Armed Services, Washington, D.C. lY80.
[65]
Hayes-Roth, F. Waterman, D., and Lenat. D. Building Expert Sysfems. Addison-Wesley, Reading, Mass., 1983.
[66]
Henderson. P., Ed. Proceedings of the ACM SIGSOFT/SIGPLAN Software Engineeritlg Symposium on Practical Soflwarr Developme? Environmtwts. ACM, New York. 1984.
[67]
Howard, M. On fighting a nuclear war. lnf. Sccur. 5.4 (Spring 1981), 3-17.
[68]
Howden. W.E. Validation of scientific programs. ACM Compur. Sure. 14,2 (June 1982). 193-227.
[69]
Hubbell, J.C. You are under attack! The strange incident of Octoher 5. Reader's Dig. 78, 468 (Apr. 1961), 37-41.
[70]
international Institute for Strategic Studies. The Military Balame 1983-1984. International Institute for Strategic Studies, London, 1983.
[71]
Jensen, R.W., and Ton&. CC. Software E?lgi,teeri?lg. Prenlice-Hall. Englewood Cliffs, N.J. 1979.
[72]
Kahn, H. 011 Thermonuclear War. Princeton University Press, Princeton, N.}. 1960.
[73]
Kaplan, F. The Wizards ofArmageddon. Simon and Schuster, New York, 1983.
[74]
Kissinger, H.A. Nuclear Weapons a,ld Foreign Policy. Harper, New York, 1~57.
[75]
Kling. R. Defining the boundaries of computing across complex organizations. In Crifical Issues in Information Sysfems Research, R. Boland and R. Hirschheim, Eds. Wiley, New York, 1987.
[76]
Lerner, E.J. Electronics and the nuclear battlefield. IEEE Spectrum 19, 10 (Oct. 1982). 64-65.
[77]
Leveson. NC. Software safety: Why, what, and how. Rep. 86-04, Dept. of Information and Computer Science, Univ. of California. Irvine. Feb. 1986.
[78]
Lieblein. E. The Department of Dellnse Software Initiative-A status report. Commun. ACM 29,8 (Aug. 1986), 734-744.
[79]
Lin, H. Software for ballistic missile defense. Rep. C/85-2, Center for International Studies, MIT, Cambridge, Mass. June 1985.
[80]
Martin, R. Stopping the unthinkable: C31 dimensions of terminating a "limited" nuclear war. Rep. P-82-3, Center for Information Policy Research, Harvard Univ., Cambridge, Mass., Apr. 1982.
[81]
Meyers. C.J. Software Reliability: Principles and Practices. Wiley, New York. 1976.
[82]
Meyers, G.J. The Art of Software Testing. Wiley, New York, 1979.
[83]
Miller, GE. Existing systems of command and control. In The Dangers of Nuclear War, Griffiths, Franklyn, and Polanyi. Eds. University of Toronto Press, Toronto, Ontario, 1979. pp. 50-66.
[84]
MITRE Corp. National security issues symposium: Strategic nuclear policies, weapons, and the C3 connection. Dot. M82-30, MITRE Corp., Bedford. Mass., 1982.
[85]
Morgan, P.M. Deferruxe: A Conrrpfual Analysis. 2nd ed. Sage, Beverley Hills, Calif., 1983.
[86]
Nelson, G. and Redell. D. The Star Wars computer systems. Abacus 3, 2 (Winter 1986). 8-20.
[87]
Neumann. PG. An editorial on software correctness and the social process. Soffm. Eng. Notes 4. 2 (Apr. 1979), 3-4.
[88]
Neumann. P.G. Letter from the editor. Softw. Eng. Notes 10, 1 (Jan. 1985). 3-11.
[89]
New York Times. Moon stirs scare of missile attack. NPW York Times (Dec. 8. 1960). 71:Z.
[90]
New York Times. False alarm on atlack sends fighters into sky. New York Times (Nov. 10, 1979), 21.
[91]
NPW York Times. Missile alerts traced to 46 cent item. New York Times (June 18, 1980), 16.
[92]
New York Times. Nevada governor says errors led to flooding. New York Times (July 4. 1983). I-10.
[93]
Nye. J.S. Allison, G.T., and Carneaale. A. Analytic conclusions: Hawks, doves, and owls. In Hawks, Doves, and Owls. G.T. Allison, A. Carnesale, and 1.:;. Nye. Eds. Norton, New York, 1985. Chap. 8. pp. 206-222.
[94]
Office of Technology Assessment. MX missile basing-Launch under attack. Office of Technology Assessment, Washington, D.C., 1981.
[95]
Omstein, S. Smith, B.C., and Suchman. L. Strategic computing: An assessment. Bull. At. Sri. 40, 10 (Dec. 1984), 11-15.
[96]
Parnas, D.L., Clements, P.C., and Weiss, D.M. The modular structure of complex syst.ems. In Proceedings of the 7th international Conference on Software Engineering (Orlando, Fla. Mar. 26-29). IEEE Press, New York, 1984. pp. 408-417.
[97]
Parnas, D.L. Software aspects of strategic defense systems. Am. Sci. 73, 5 (Sept.-Oct. 1985). 432-440.
[98]
Parnas. D.L. SDI: A violation of professional responsibility. Abacus 4. 2 (Winter 19871, 46-52.
[99]
Partsch. H., and Steinbruggen. R. Program transformation systems. ACM Comput. Sure. 15. 3 (Sept. 19133), 199-236.
[100]
Perrow, C. Normal accident at Three Mile Island. Society 18, 5 (July-Aug. 1981). 17-26.
[101]
Perrow, C. Normal Accidents: Living with High-Risk Technologies. Basic Books. New York, 1984.
[102]
Pollack, A. Trust in computers raising risk of errors and sabotage. New York Times (Aug. 22. 1983). 1.
[103]
Pringle, P. and Arkin. W. S.I.O.P.: The Secret U.S. Plan for Nuclear War. Norton, New York, 1983.
[104]
Ricketts. L.W. Fundnmentals of Nuclear Hardening of Electronic Equipment. Wiley, New York, 1972.
[105]
Ricketts. L.W. Bridges, J.E. and Miletta, J. EMP Radiatiorl and Profecfive Techniques. Wiley, New York. 1976.
[106]
Rogovin. M., and Frampton. G.T. Three Mile Island: A Report fo the Commissioners and to the Public. Nuclear Regulatory Commission Special Inquiry Group. U.S. Nuclear Regulatory Commission, Washington. D.C., 1980.
[107]
Rosen, E. Vulnerabilities of netwclrk control protocols: An example. Softru. Eng. Notes 6, 1 (Jan. 1981). 6-8.
[108]
Scowcroft, B. C3 systems for the president and military commanders. In Nafionrd Security Issues Symposium: Strategic Nuclear Policies, Weapons, and the C3 Connection, D.M. Ace, Ed. MITRE Corp., Bedford, Mar:s. 1982. pp. 93-97.
[109]
Scowcroft, B. Reporf of the President's Commission on Sfrafegic Forces. U.S. Department of Defense, Washington, D.C. Apr. 1983.
[110]
Seattle Post-l~rtelligertcer. Russia puts more N-arms off U.S. Coast. Seaftle Post-Intelligencer (May 21, 1984). AZ.
[111]
Siewiorek. D.P., and Swan, R.S. The Theory aad Practice of Reliable Sysfenl Design. Digital Press. Bedford, Mass., 1982.
[112]
Silverman. J.M. Reflections on the verification of the security of an operating system. In Proceedings of fhe 9th ACM Symposium on Operating Systems Principles (Oct.). ACM, New York, 1983, pp. 143-154.
[113]
Smith, B.C. The limits of correctness. ACM SIGCAS NewsI. 14,4 and 1.5, l-3 (Winter-Fall 1985), 18-26.
[114]
Sokolovskiy. V.D. Soviet Military Strafegy. Edited, with an analysis and commentary, by H. Fast Scott. Crane, Russak and Co., New York, 1975.
[115]
Sommerville, 1. Soffware Engineering. Addison-Wesley, Reading, Mass. 1982.
[116]
Stefik, M. Strategic computing at DARPA: Overview and assessment. Commun. ACM 28, 7 (July 1985). 690-704.
[117]
Stefik, M., Aikins, J., Balzer, R., Benoit, J., Birnbaum, L., Hayes- Roth, F. and Sacerdoti. E. The organization of expert systems, a tutorial. Artif. Intell. 18, 2 (Mar. 1982), 135-173.
[118]
Stein, D.L. Electromagnetic pulse-The uncertain certainty. Bull. At. Sci. 39, 3 (Mar. 1983), 52-56.
[119]
Steinbruner. J.D. Nuclear decapitation. Foreign Policy 45 (Winter 1981-1982)' 16-28.
[120]
Steinbruner. J.D. Launch under attack. Sci. Am. 250, 1 (Jan. 1984), 37-47.
[121]
Stevens, R.T. Testing the NORAD command and control system. IEEE Trans. Syst. Sci. Cybem. SSC-4, 1 (Mar. 1968), 47-51.
[122]
Stockholm International Peace Research Institute. World Armamenfs and Disarmament: SlPRI Yearbook 1983. Taylor and Francis, London, 1983.
[123]
Stockholm International Peace Research Institute. World Armaments and Disarmament: SIPRJ Yearbook 1984. Taylor and Francis. London, 1984.
[124]
Tasky. K. Soviet technology gap and dependence on the west: The case of computers. A Compendium of Papers Submitted to the Joint Economic Committee of the Congress of the United States, Washington, D.C., Oct. 10, 1979.
[125]
U.S. Department of Defense. Military Standardization Handbook: Reliability Prediction of Electronic Equipment. MIL-STD.HDBK-217C. Notice 1 ed. U.S. Department of Defense. Washington, DC., 1980.
[126]
U.S. Department of Defense. Modernization of the WWMCCS Information System (WIS). The Assistant Secretary of Defense (CCCI) with the assistance of the WWMCCS System Engineer (DCA). U.S. Department of Defense, Washington. D.C. July 31, 1982.
[127]
U.S. Department of Defense. Soviet Military Power. 2nd ed. U.S. Government Printing Office, Washington, D.C., 1983.
[128]
U.S. Department of Defense. Software technology for adaptable, reliable systems. Softw. Eng. Notes 8, 2 (Apr. 1983), 55-64.
[129]
U.S. Department of Defense. Soviet Military Power. 3rd ed. U.S. Government Printing Office, Washington, DC., 1984.
[130]
U.S. Department of Defense. Report of the Sfudy on Eliminating the Threat Posed by Nuclear Ballistic Missiles. Vol. 5, Bntfle Management, Communications, and Data Processing. U.S. Department of Defense, Washington, D.C. Feb. 1984.
[131]
U.S. Department of Defense. DOD-STD.2167: Military Standard Defense Sysfem Soffware Development U.S. Department of Defense, Washington, DC., 1985.
[132]
US. House of Representatives. Failures of fhe North American Aerospace Defense Command's OVORADJ Attack Warning System. Hearings before a Subcommittee of the Committee on Government Operations, U.S. House of Representatives, 97th Congress, 1st session, May 19 and 20.1981.
[133]
U.S. House of Representatives. Hearings, Department of Defense Appropriafions for 1985. Committee on Appropriations, Subcommittee on the Department of Defense, U.S. Government Printing Office, Washington, DC., 1984.
[134]
U.S. House of Representatives. Our Nation's Nuclear Warning Sysfern: Will It Work 1j We Need If? Hearings before a Subcommittee of the Committee on Government Operations. U.S. House of Representatives. 99th Congress, 1st session, Sept. 26. 1985.
[135]
U.S. Senate Committee on Armed Services. Hearings, Department of Defense Authorization for Appropriations for N 1982, Part 7. U.S. Government Printing Office, Washington, D.C., 1981.
[136]
U.S. Senate Committee on Armed Services. Hearings, Department of Defense Aufhorizafion for Appropriations for FY 1984, Parf 5. U.S. Government Printing Office, Washington, D.C. 1983.
[137]
Van Evera, S. The cult of the offensive and the origins of the First World War. Int. Secur. 9, 1 (Summer 19841, 58-107.
[138]
Waltz, E.L. Data fusion for C31 systems. In CsI Handbook. EW Communications. Palo Alto, Calif. 1986, pp. 217-226.
[139]
Washirtgtm Post. Computer again gives signal of false Soviet attack. Washington Posf (June 8, 1980). A7.
[140]
Washingfon Posf. Soviet warns of automatic retalialion against new U.S. missiles. Washingfon Post (May 18, 1983), A12.
[141]
Weinberger, C.W. Reporf of fhe Secrefq of Defense fo fhe Congress on fhe FY 1985 Budget, J?' 1986 Authorization Request and N 1985-89 Defew Programs. U.S. Government Printing Office, Washington, D.C. 1984.
[142]
Zraket. CA. Strategic command, control. communications, and intelligence. Scimce 224, 4655 (June 22, 1984), 1306-1311.

Cited By

View all

Recommendations

Reviews

Dennis Roy Thompson

At the onset, the author of this paper states, “Portions of a preliminary version of this article were presented at the Fourth Congress of the International Physicians for the Prevention of Nuclear War. . . ” This information is footnoted on the first page of this highly biased paper. Borning's prime question is, “How dependent should society be on computer systems and computer decision making__?__” especially “. . . in the use of computers in command and control systems for nuclear weapons. . .” He concludes that “The fundamental problems are due to untestability, limits of human decision making during high tension and crisis, and our inability to think through all the things that might happen in a complex and unfamiliar situation. We must recognize the limits of technology. The threat of nuclear war is a political problem, and it is in the political, human realm that solutions must be sought.” Everything in between the beginning and conclusion is a biased discussion of many important issues. Borning's references (which run to a total of 142) are also biased, for I see no poignant countervailing references like [1]. Some of the arguments he presents leave off other possibilities: “A continuing trend in the arms race has been the deployment of missiles with greater and greater accuracies. This trend is creating increasing pressure to consider launch-on-warning strategy. . . .” He does not mention that with increasing accuracy we need smaller and smaller warheads that may eventually use nonnuclear warheads. Borning presents the “false alert” of June 3, 1980, when the Strategic Air Command mistakenly reported a Soviet missile coming toward the US, and continues: “It is quite possible that some of these preparations were observed by the Soviet Union.” There is no factual evidence for this, just a presumed possibility, yet he argues that “World War I following the assassination of the archduke in Sarajevo, in which the alerts and mobilizations of the European powers interacted in just this way, is a historical precedent for this possibility. . . .” Even if World War I can be ascribed to this kind of chain reaction, this is shoddy, dishonest reasoning. If one is a slave to history, one is bound to repeat it. SDI is represented as totally unworkable owing to its complexity, both in hardware and software, which echoes the author's conclusion that we must recognize the limits of technology. We cannot have automatic systems because of the reliability problems, conceptual problems, and strategic problems. We cannot have reliable computerized systems because of human operator problems. And we cannot have humans making decisions under conditions of stress. What then is the answer if neither machines nor men (whether they be generals, privates, or politicians) can function__?__ I posit the answer—we must not recognize the limits of either technology or man. Though this is an extremely biased paper and I wonder if it should not have appeared in some political journal, it should be read; it does contain a detailed discussion of many crucial issues. The following are the major section headings: False Alerts, Tightly Coupled Nuclear Forces, Launch-on-Warning, The Reliability of Complex Systems, Limited or Protracted Nuclear War, Future Computer-Controlled Military Systems, and Conclusions.

Access critical reviews of Computing literature here

Become a reviewer for Computing Reviews.

Comments

Please enable JavaScript to view thecomments powered by Disqus.

Information & Contributors

Information

Published In

cover image Communications of the ACM
Communications of the ACM  Volume 30, Issue 2
Feb. 1987
70 pages
ISSN:0001-0782
EISSN:1557-7317
DOI:10.1145/12527
Issue’s Table of Contents
Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. Copyrights for components of this work owned by others than ACM must be honored. Abstracting with credit is permitted. To copy otherwise, or republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee. Request permissions from [email protected]

Publisher

Association for Computing Machinery

New York, NY, United States

Publication History

Published: 01 February 1987
Published in CACM Volume 30, Issue 2

Permissions

Request permissions for this article.

Check for updates

Qualifiers

  • Article

Contributors

Other Metrics

Bibliometrics & Citations

Bibliometrics

Article Metrics

  • Downloads (Last 12 months)167
  • Downloads (Last 6 weeks)24
Reflects downloads up to 11 Dec 2024

Other Metrics

Citations

Cited By

View all
  • (2022)Cybersecurity of nuclear weapon systemsCybersecurity and Law10.35467/cal/1464696:2(91-101)Online publication date: 7-Feb-2022
  • (2022)Accidental Insecure BehaviorProceedings of the 2022 Computers and People Research Conference10.1145/3510606.3550208(1-4)Online publication date: 2-Jun-2022
  • (2020)Computing and AccountabilityThe Ethics of Information Technologies10.4324/9781003075011-26(351-358)Online publication date: 23-Jul-2020
  • (2020)From closed world discourse to digital utopianism: the changing face of responsible computing at Computer Professionals for Social Responsibility (1981–1992)Internet Histories10.1080/24701475.2020.17258514:1(6-31)Online publication date: 2-Mar-2020
  • (2018)ReferencesMilitary Nuclear Accidents10.1002/9781119572558.refs(215-246)Online publication date: 12-Dec-2018
  • (2015)Managing risk, the state and political economy in historical perspectiveInternational Politics10.1057/ip.2015.252:4(408-425)Online publication date: 20-Mar-2015
  • (2014)Getting there from here. Remembering the future of digital humanities: Roberto Busa Award lecture 2013Literary and Linguistic Computing10.1093/llc/fqu02229:3(283-306)Online publication date: 19-May-2014
  • (2014)Getting There from HereAdvancing Digital Humanities10.1057/9781137337016_19(291-321)Online publication date: 2014
  • (2010)Other Ways of Making Plants FriendlierProcess Plants10.1201/9781439804568-c9(171-191)Online publication date: 13-Jul-2010
  • (2009)Computer Reliability and Public Policy: Limits of Knowledge of Computer-Based SystemsSocial Philosophy and Policy10.1017/S026505250000353813:2(229-266)Online publication date: 13-Jan-2009
  • Show More Cited By

View Options

View options

PDF

View or Download as a PDF file.

PDF

eReader

View online with eReader.

eReader

Login options

Full Access

Media

Figures

Other

Tables

Share

Share

Share this Publication link

Share on social media