Managing complexity.

This article asks if the failure of most software projects to meet their goals can be fixed by giving developers better tools. On September 14th, the radios in an air-traffic control centre in Palmdale, California shut down, grounding hundreds of flights in southern California and Nevada, and leadi...

Descripción completa

Detalles Bibliográficos
Publicado en:Economist Vol. 373; no. 8403; pp. 71 - 74
Formato: Artículo
Publicado: Economist Newspaper Limited 11/27/2004
Materias:
Acceso en línea:Ver este registro en EBSCOhost
fields @attributes:
  recordID: 1
pdfLink:
plink: https://search.ebscohost.com/login.aspx?direct=true&db=hlh&AN=15205327&site=ehost-live
header:
  @attributes:
    shortDbName: hlh
    uiTerm: 15205327
    longDbName: Humanities International Complete
    uiTag: AN
  controlInfo:
    bkinfo:
    jinfo:
      jid:
        00130613
        ECO
      jtl: Economist
      issn: 00130613
      maglogo: N
    pubinfo:
      dt: 11/27/2004
      vid: 373
      iid: 8403
      pid: 161
      pub: Economist Newspaper Limited
    artinfo:
      ui: 15205327
      ppf: 71
      ppct: 3
      formats:
      tig:
        atl: Managing complexity.
      aug:
      su:
        Computer software development
        Computer software industry
        Computer software
        Barclays Global Investors NA
        Computer programmers
        Software failures
      sug:
        subj:
          Computer software development
          Computer software industry
          Computer software
          Barclays Global Investors NA
          Computer programmers
          Software failures
      ab: This article asks if the failure of most software projects to meet their goals can be fixed by giving developers better tools. On September 14th, the radios in an air-traffic control centre in Palmdale, California shut down, grounding hundreds of flights in southern California and Nevada, and leading to five mid-air encounters between aircraft unable to talk to the ground controllers. A glitch in the software running the system meant the computers had to be re-booted every 30 days, and somebody forgot to do so. But software running a mission-critical system should not have to be restarted every month. At least Palmdale's software worked some of the time.The same cannot be said of an $4 billion write-off that America's Internal Revenue Service (IRS) had to swallow when a multi-year effort to overhaul its computer system failed completely in 1997. As software has become more and more pervasive in business and government, and more complicated, the impact of poor software design has been steadily growing.
      pubtype: Periodical
      doctype: Article
      src: R
    language: English
    refInfo:
    copyright:
      @attributes:
        flag: Y
      dt:
        @attributes:
          year: 2004
    holdings:
      @attributes:
        islocal: N