Refine
Document Type
- Master's Thesis (7)
- Doctoral Thesis (3)
- Bachelor Thesis (1)
- Diploma Thesis (1)
Keywords
- API (1)
- API analysis (1)
- API-Analyse (1)
- Ad-hoc-Netz (1)
- Algorithmische Geometrie (1)
- Beaconless (1)
- Befahrbarkeit (1)
- Developer profiling (1)
- Dimension 3 (1)
- Distributed Algorithm (1)
- Drahtloses Sensorsystem (1)
- Drahtloses vermachtes Netz (1)
- Ebener Graph (1)
- Echtzeit-Interaktion (1)
- Entwickler Profil (1)
- Gelände (1)
- Geographic routing (1)
- Geometric spanner (1)
- Graph (1)
- Hindernis (1)
- Java. Programmiersprache (1)
- Klassifikation (1)
- Knowledge Engineering (1)
- Komplexität / Algorithmus (1)
- Laser (1)
- Local algorithm (1)
- MSR (1)
- Meteor (1)
- Mining Software Repositories (1)
- Nachbarschaftsgraph (1)
- Netzwerktopologie (1)
- Nutzerzufriedenheit (1)
- Planar graphs (1)
- Quasi unit disk graph (1)
- Reactive algorithm (1)
- Roboter (1)
- Routing (1)
- Software Engineering (1)
- Software Repositories (1)
- Straßenzustand (1)
- Technology Acceptance Model (1)
- Unit disk graph (1)
- Verteilter Algorithmus (1)
- Wahrscheinlichkeitsrechnung (1)
- Wireless sensor network (1)
- Zusammenhängender Graph (1)
- e-service quality (1)
Institute
- Institut für Informatik (12) (remove)
This thesis presents an analysis of API usage in a large corpus of Java software retrieved from the open source repositories hosted at SourceForge. Most larger software projects use software libraries, which offer a public "application programming interface" or API as an interface for the programmer. In order to facilitate the transition between different APIs, there are emerging research projects in the field of automated API migration. However, there is a lack of basic statistical background information about in-the-wild usage of APIs as such measurements have, until now, only been done on rather small corpora. We thus present an analysis method suitable for measurements with large corpora. First, we create a corpus of open source projects hosted on SourceForge, as well as a corpus of software libraries. Then, all projects in the corpus are compiled with an instrumented compiler. We use a compiler plugin for javac that gives detailed information about every method created by the compiler. This information is stored in a database and analyzed.