research-article

Free Access

API design matters

Author:
Michi Henning

ZeroC

ZeroC
View Profile

Authors Info & Claims

Communications of the ACM Volume 52 Issue 5May 2009pp 46–56https://doi.org/10.1145/1506409.1506424

Published:01 May 2009Publication History

Check for updates on crossmark

Communications of the ACM

Abstract

Bad application programming interfaces plague software engineering. How do we get things right?

Index Terms

API design matters
1. Software and its engineering
  1. Software creation and management
    1. Designing software
      1. Software implementation planning
        Software design techniques
    2. Software development process management
  2. Software notations and tools
    1. General programming languages
      1. Language types
        Functional languages

Recommendations

API: Design Matters: Why changing APIs might become a criminal offense.
API Design

After more than 25 years as a software engineer, I still find myself underestimating the time it will take to complete a particular programming task. Sometimes, the resulting schedule slip is caused by my own shortcomings: as I dig into a problem, I ...
Read More
How to design a good API and why it matters
OOPSLA '06: Companion to the 21st ACM SIGPLAN symposium on Object-oriented programming systems, languages, and applications
In lieu of a traditional , I've tried to distill the essence of the talk into a collection of maxims:
- All programmers are API designers. Good programs are modular, and intermodular boundaries define APIs. Good modules get reused.
- APIs can be among your ...
Read More
Eclipse API usage: the good and the bad

Today, when constructing software systems, many developers build their systems on top of frameworks. Eclipse is such a framework that has been in existence for over a decade. Like many other evolving software systems, the Eclipse platform has both ...
Read More

Comments

Login options

Check if you have access through your login credentials or your institution to get full access on this article.

Full Access

Get this Article

Published in

Communications of the ACM Volume 52, Issue 5
Security in the Browser
May 2009
132 pages
ISSN:0001-0782
EISSN:1557-7317
DOI:10.1145/1506409
Issue’s Table of Contents

Copyright © 2009 ACM
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]
Sponsors
In-Cooperation
Publisher
Association for Computing Machinery
New York, NY, United States
Publication History
- Published: 1 May 2009
Permissions
Request permissions about this article.
Request Permissions

Check for updates
Qualifiers
- research-article
- Popular
- Refereed
Conference
Funding Sources
Other Metrics
View Article Metrics

Article Metrics
- 34
  Total Citations
  View Citations
- 62,908
  Total Downloads
- Downloads (Last 12 months)5,142
- Downloads (Last 6 weeks)47
Other Metrics
View Author Metrics
Cited By
View all

PDF Format

View or Download as a PDF file.

eReader

View online with eReader.

HTML Format

View this article in HTML Format .

View HTML Format

View Issue’s Table of Contents