API Fluency

Robbes, Romain; Lungu, Mircea; Janes, Andrea

doi:10.1109/icse-nier.2019.00033

Cited by 3 publications

(2 citation statements)

References 13 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…PScout [11] has established mapping relationships between permissions and APIs, this provides us a basis to identify the APIs need to be extracted. In the website of PScout, there are 10 different versions.…”

Section: A Initializing Relationships Between Feature Framework and mentioning

confidence: 99%

“…Second, to solve the problem that the permissions of Apps are stated for the whole product rather than functionalities, we use the Application Programming Interfaces (APIs) [11] to bridge the gap between features and permissions. We extract the APIs used in the Apps from the APK files, and establish the relationships between them and the feature framework by calculating two parameters: one is ''term frequency, TF'', aiming at analyzing the APIs often used by the Apps contain a certain functionality reflected by one node in the framework; the other is ''inverse document frequency, IDF'', focusing on analyzing the APIs used especially for a certain functionality.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Recommending Security Requirements for the Development of Android Applications Based on Sensitive APIs

Liu

et al. 2020

IEEE Access

View full text Add to dashboard Cite

App stores allow anyone to sell his products to millions of potential users. However, limited by the resources and time, some developers often focus on the functionalities of their Apps without wellrounded considering security problems, which are more and more important for a successful product. In this paper, we propose an approach to help developers elicit security requirements by recommending related information gained from existing Apps in the marketplace. Firstly, we construct a feature framework to summarize functionalities of Apps by mining their descriptions with the method proposed in our previous work. Then, the sensitive APIs used in these Apps are extracted from their APK files and mapped with App features. Finally, we establish relationships between permissions and functionalities by taking sensitive APIs as a bridge, and design a recommendation framework to show information according to developers' demands from two aspects: the security requirements for the whole App and the ones for the given functionality. We evaluate our approach with 580 Apps from 5 categories on Google Play. The results confirm the usefulness of our approach, especially it can help new developers without experience initialize the security requirements and give mature developers supplementary information to elicit security requirements completely.

show abstract

Section: A Initializing Relationships Between Feature Framework and mentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%