On the Role of Fitness Dimensions in API Design Assessment

Next week, Imed Hammouda will present our joint work with Amir Zghidi and Brahim Hnich on API Design Assessment at the 1st International workshop on API Usage and Evolution, co-located with ICSE2017 in Buens Aires, Argentina. A pre-print of our paper is linked to this blog post.

This is clearly work in progress, based on our previous works on ecosystemability assessment and our realization that creating and maintaining suitable APIs is crucial for an organization’s ability to maintain a competitive edge in any software ecosystem. In particular, we distinguish technical and cognitive fitness dimensions, i.e. non-functional requirements that API Stakeholders may have. We anticipate that these fitness dimension will play an important role in the evolution of APIs, which we hope to support based on a continuous assessment method.

Title: On the Role of Fitness Dimensions in API Design Assessment – An Empirical Investigation

Abstract: In this paper we present a case study of applying fitness dimensions in API design assessment. We argue that API assessment is company specific and should take into consideration various stakeholders in the API ecosystem. We identified new fitness dimensions and introduced the notion of design considerations for fitness dimensions such as priorities, tradeoffs, and technical versus cognitive classification.

Reference: Zghidi, A.; Hammouda, I.; Hnich, B. & Knauss, E.: On the Role of Fitness Dimensions in API Design Assessment: An Empirical Investigation. In: Proceedings of 1st International Workshop on API Usage and Evolution (WAPI ’17), co-located with the 39th Int. Conf. on Software Engineering (ICSE 2017), 2017

Pre-print: Zghidi2017

Advertisements