API Design Matters.

The article discusses application programming interfaces (API) used in the software engineering industry. An API is a set of routines, data structures, object classes or protocols provided by libraries and operating system services in order to support the building of applications. A good API, the au...

Descripción completa

Detalles Bibliográficos
Publicado en:Communications of the ACM Vol. 52; no. 5; pp. 46 - 57
Autor principal: HENNING, MICHI
Formato: Artículo
Publicado: Association for Computing Machinery May2009
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=39363005&site=ehost-live
header:
  @attributes:
    shortDbName: hlh
    uiTerm: 39363005
    longDbName: Humanities International Complete
    uiTag: AN
  controlInfo:
    bkinfo:
    jinfo:
      jid:
        00010782
        ACM
      jtl: Communications of the ACM
      issn: 00010782
      maglogo: N
    pubinfo:
      dt: May2009
      vid: 52
      iid: 5
      pid: 68
      pub: Association for Computing Machinery
    artinfo:
      ui:
        39363005
        10.1145/1506409.1506424
      ppf: 46
      ppct: 11
      formats:
      tig:
        atl: API Design Matters.
      aug:
        au: HENNING, MICHI
      su:
        Application program interfaces
        Software engineering
        Application software
        Computer operating systems
        Electronic file management
        Computer science
      sug:
        subj:
          Application program interfaces
          Software engineering
          Application software
          Computer operating systems
          Electronic file management
          Computer science
      ab: The article discusses application programming interfaces (API) used in the software engineering industry. An API is a set of routines, data structures, object classes or protocols provided by libraries and operating system services in order to support the building of applications. A good API, the author states, works without friction and deals correctly with boundary conditions. Topics include the different ways one can design an API incorrectly, the inherent difficulty in designing a good API, and the collateral damage that occurs when minor, isolated design flaws interact with each other.
      pubtype: Periodical
      doctype: Article
      src: R
    language: English
    refInfo:
    copyright:
      @attributes:
        flag: Y
      dt:
        @attributes:
          year: 2009
    holdings:
      @attributes:
        islocal: N