Today more and more software operates in a software ecosystem where software products and services are shared over a common technological platform between business actors. In such a setting, a software platforms’ API becomes the interface between the platform and its owner(s) on the one side and other actors and their extensions on the other side. In such ecosystem context, platform API fitness for application development has a huge impact on the success of the ecosystem. However, software ecosystems are usually evolving at a high pace given their dynamic structure and the continuously changing business strategies of ecosystem actors. The design of APIs for software ecosystems therefore has to co-evolve. In this position paper, we propose a continuous (re-)assessment method for platform APIs that takes into account ecosystem needs. We illustrate the method with insights from ongoing case studies.

Länka till denna publikation

Dela på webben

Skapa referens, olika format (klipp och klistra)

BibTeX @conference{Hammouda2015,author={Hammouda, Imed and Knauss, Eric and Costantini, Leonardo},title={Continuous API-Design for Software Ecosystems},booktitle={Proceedings of 2nd International Workshop on Rapid and Continuous Software Engeering (RCoSE '15 @ ICSE)},abstract={Today more and more software operates in a software ecosystem where software products and services are shared over a common technological platform between business actors. In such a setting, a software platforms’ API becomes the interface between the platform and its owner(s) on the one side and other actors and their extensions on the other side. In such ecosystem context, platform API fitness for application development has a huge impact on the success of the ecosystem. However, software ecosystems are usually evolving at a high pace given their dynamic structure and the continuously changing business strategies of ecosystem actors. The design of APIs for software ecosystems therefore has to co-evolve. In this position paper, we propose a continuous (re-)assessment method for platform APIs that takes into account ecosystem needs. We illustrate the method with insights from ongoing case studies.},year={2015},keywords={API Design, Software Ecosystem, Continuous Software Engineering},}

RefWorks RT Conference ProceedingsSR PrintID 217433A1 Hammouda, ImedA1 Knauss, EricA1 Costantini, LeonardoT1 Continuous API-Design for Software EcosystemsYR 2015T2 Proceedings of 2nd International Workshop on Rapid and Continuous Software Engeering (RCoSE '15 @ ICSE)AB Today more and more software operates in a software ecosystem where software products and services are shared over a common technological platform between business actors. In such a setting, a software platforms’ API becomes the interface between the platform and its owner(s) on the one side and other actors and their extensions on the other side. In such ecosystem context, platform API fitness for application development has a huge impact on the success of the ecosystem. However, software ecosystems are usually evolving at a high pace given their dynamic structure and the continuously changing business strategies of ecosystem actors. The design of APIs for software ecosystems therefore has to co-evolve. In this position paper, we propose a continuous (re-)assessment method for platform APIs that takes into account ecosystem needs. We illustrate the method with insights from ongoing case studies.LA engOL 30