Unsafe Standardization.

The article discusses safety standards for software. Safety cannot be measured in isolation, but only in the context of actual operating environments. A systems approach to safety focuses on three key areas. First, any safety claims must be explicit with respect to the claim made and operating envir...

Descripción completa

Detalles Bibliográficos
Publicado en:Computer (00189162) Vol. 40; no. 11; pp. 109 - 112
Autor principal: Thomas, Martyn
Formato: Artículo
Publicado: IEEE Nov2007
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=27506996&site=ehost-live
header:
  @attributes:
    shortDbName: hlh
    uiTerm: 27506996
    longDbName: Humanities International Complete
    uiTag: AN
  controlInfo:
    bkinfo:
    jinfo:
      jid:
        00189162
        PUT
      jtl: Computer (00189162)
      issn: 00189162
      maglogo: N
    pubinfo:
      dt: Nov2007
      vid: 40
      iid: 11
      pid: 13605
      pub: IEEE
    artinfo:
      ui:
        27506996
        10.1109/MC.2007.407
      ppf: 109
      ppct: 3
      formats:
      tig:
        atl: Unsafe Standardization.
      aug:
        au: Thomas, Martyn
        affil: Fellow, Royal Academy of Engineering
      su:
        Computer software safety measures
        Software engineering
        Software architecture
        Computer software development
        Software measurement
        Computer software usability
      sug:
        subj:
          Computer software safety measures
          Software engineering
          Software architecture
          Computer software development
          Software measurement
          Computer software usability
      ab: The article discusses safety standards for software. Safety cannot be measured in isolation, but only in the context of actual operating environments. A systems approach to safety focuses on three key areas. First, any safety claims must be explicit with respect to the claim made and operating environment assumed. Next, claims must be supported by solid evidence, not just general-purpose recommendations. Finally, software design should avail itself of the industry's collective safety-related expertise.
      pubtype: Academic Journal
      doctype: Article
      src: R
    language: English
    refInfo:
    copyright:
      @attributes:
        flag: Y
      dt:
        @attributes:
          year: 2007
    holdings:
      @attributes:
        islocal: N