API Management Challenges in Ecosystems

  • Sebastien AndreoEmail author
  • Jan Bosch
Conference paper
Part of the Lecture Notes in Business Information Processing book series (LNBIP, volume 370)


The API has become a cornerstone of software ecosystems, providing ways to drive innovation inside and outside the organization. Because of this criticality, we should manage APIs. The purpose of this study is to identify and classify the challenges that organizations evolving into internal ecosystems are facing as they have to deal with APIs. We performed a qualitative research study on three Siemens internal ecosystems with different sizes, technologies, and age. The results reveal that even if we are talking about the API economy, organizations are struggling with different aspects of API management related to Business, Architecture, Process, and Organization. The challenges identified in this paper provide a basis for future research.


API API management Case study 


  1. 1.
    Parnas, D.L.: On the criteria to be used in decomposing systems into modules. Commun. ACM 15(12), 1053–1058 (1972). Scholar
  2. 2.
    Bloch, J.: How to design a good API and why it matters. In: Companion to the 21st ACM SIGPLAN Conference on Object-Oriented Programming Systems, Languages, and Applications - OOPSLA 06 (2006)Google Scholar
  3. 3.
  4. 4.
    Schultis, K.-B., Elsner, C., Lohmann, D.: Architecture challenges for internal software ecosystems: a large-scale industry case study. In: Proceedings of the 22Nd ACM SIGSOFT International Symposium on Foundations of Software Engineering, FSE 2014, pp. 542–552. ACM, New York (2014).
  5. 5.
    van der Linden, F.J., Schmid, K., Rommes, E.: Software Product Lines in Action: The Best Industrial Practice in Product Line Engineering. Springer, Heidelberg (2007). Scholar
  6. 6.
    Eisenhardt, K.M.: Building theories from case study research. Acad. Manag. Rev. 14(4), 532 (1989)CrossRefGoogle Scholar
  7. 7.
    Walsham, G.: Interpretive case studies in is research: nature and method. Eur. J. Inf. Syst. 4(2), 74–81 (1995). Scholar
  8. 8.
    Sawant, A.A., Aniche, M., van Deursen, A., Bacchelli, A.: Understanding developers’ needs on deprecation as a language feature. In: Proceedings of the 40th International Conference on Software Engineering, ICSE 2018, pp. 561–571. ACM, New York (2018).
  9. 9.
    Hora, A., Robbes, R., Valente, M.T., Anquetil, N., Etien, A., Ducasse, S.: How do developers react to API evolution? A large-scale empirical study. Softw. Qual. J. 26(1), 161–191 (2018). Scholar
  10. 10.
    Medjaoui, M., Wilde, E., Mitra, R., Amundsen, M.: Continuous API Management: Making the Right Decisions in An Evolving Landscape. OReilly, Sebastopol (2018)Google Scholar
  11. 11.
    Hammouda, I., Knauss, E., Costantini, L.: Continuous API design for software ecosystems. In: 2015 IEEE/ACM 2nd International Workshop on Rapid Continuous Software Engineering, pp. 30–33, May 2015Google Scholar
  12. 12.
    Lindman, J., Horkoff, J., Hammouda, I., Knauss, E.: Emerging perspectives of API strategy. IEEE Softw., 1 (2018) Google Scholar
  13. 13.
    Brito, A., Xavier, L., Hora, A., Valente, M.T.: APIDiff: detecting API breaking changes. In: 2018 IEEE 25th International Conference on Software Analysis, Evolution and Reengineering (SANER), pp. 507–511, March 2018Google Scholar

Copyright information

© Springer Nature Switzerland AG 2019

Authors and Affiliations

  1. 1.Siemens AG Corporate TechnologyErlangenGermany
  2. 2.Department of Computer Science and EngineeringChalmers University of TechnologyGöteborgSweden

Personalised recommendations