The Real Software Crisis: Repeatability as a Core Value.

The authors argue that where appropriate, research papers in computer programming should be accompanied by software artifacts that let others test the repeatability of researchers' claims. The authors summarize results of an artifact evaluation process begun on an experimental basis at conferences o...

Descripción completa

Detalles Bibliográficos
Publicado en:Communications of the ACM Vol. 58; no. 3; pp. 34 - 37
Autores principales: Krishnamurthi, Shriram, Vitek, Jan
Formato: Opinion
Publicado: Association for Computing Machinery Mar2015
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=101119727&site=ehost-live
header:
  @attributes:
    shortDbName: hlh
    uiTerm: 101119727
    longDbName: Humanities International Complete
    uiTag: AN
  controlInfo:
    bkinfo:
    jinfo:
      jid:
        00010782
        ACM
      jtl: Communications of the ACM
      issn: 00010782
      maglogo: N
    pubinfo:
      dt: Mar2015
      vid: 58
      iid: 3
      pid: 68
      pub: Association for Computing Machinery
    artinfo:
      ui:
        101119727
        10.1145/2658987
      ppf: 34
      ppct: 3
      formats:
      tig:
        atl: The Real Software Crisis: Repeatability as a Core Value.
      aug:
        au:
          Krishnamurthi, Shriram
          Vitek, Jan
        affil:
          Professor of computer science, Brown University in Providence, RI
          Professor of computer science, Northeastern University, Boston, MA
      su:
        Programming languages
        Scholarly publishing
        Computer science research
        Association for Computing Machinery
        Science publishing
        Computer software
      sug:
        subj:
          Programming languages
          Scholarly publishing
          Computer science research
          Association for Computing Machinery
          Science publishing
          Computer software
      ab: The authors argue that where appropriate, research papers in computer programming should be accompanied by software artifacts that let others test the repeatability of researchers' claims. The authors summarize results of an artifact evaluation process begun on an experimental basis at conferences of the Association of Computing Machinery, and provide commentary the mechanics of evaluating artifacts, who the evaluators should be, and the benefits of the evaluation process. Consideration is also given to whether artifacts should be published.
      pubtype: Periodical
      doctype: Opinion
      src: R
    language: English
    refInfo:
    copyright:
      @attributes:
        flag: Y
      dt:
        @attributes:
          year: 2015
    holdings:
      @attributes:
        islocal: N