Gestão de API Realmente Melhora a Relação com Desenvolvedores?
Resumo
O desenvolvimento de Application Programming Interface (APIs) possui diversos entraves, entre eles está a aceitção por parte dos desenvolvedores. Isto é, desenvolvedores podem adotar ou não uma API. Diversas causas podem estar atreladas a este problema, incluindo a falta de documentação sobre uma API, a dificuldade no aprendizado da mesma, o baixo número de desenvolvedores em comunidades, etc. Para tanto, a gestão de APIs visa tratar alguns destes problemas. Ela visa facilitar o engajamento dos desenvolvedores que é considerado como um dos fatores de risco em uma API.
Referências
Bloch, J. (2006). How to design a good api and why it matters. In Companion to the 21st ACM SIGPLAN Symposium on Object-oriented Programming Systems, Languages, and Applications, OOPSLA ’06, pages 506–507, New York, NY, USA. ACM.
Bogart, C., K¨astner, C., Herbsleb, J., and Thung, F. (2016). How to break an api: cost negotiation and community values in three software ecosystems. In Proceedings of the 2016 24th ACM SIGSOFT International Symposium on Foundations of Software Engineering, pages 109–120. ACM.
Brajesh, D. (2017). API Management, pages 15–28. Apress, Berkeley, CA.
Brito, G., Hora, A., Valente, M. T., and Robbes, R. (2016). Do developers deprecate apis with replacement messages? a large-scale analysis on java systems. In 2016 IEEE 23rd International Conference on Software Analysis, Evolution, and Reengineering (SANER), volume 1, pages 360–369.
Cataldo, M. and d. Souza, C. R. B. (2014). Exploring the impact of api complexity on failure-proneness. In 2014 IEEE 9th International Conference on Global Software Engineering, pages 36–45.
Ellis, B., Stylos, J., and Myers, B. (2007). The factory pattern in api design: A usability evaluation. In Proceedings of the 29th International Conference on Software Engineering, ICSE ’07, pages 302–312, Washington, DC, USA. IEEE Computer Society.
Komssi, M., Pichlis, D., Raatikainen, M., Kindstr¨om, K., and J¨arvinen, J. (2015). What are hackathons for? IEEE Software, 32(5):60–67.
Linares-V´asquez, M., Bavota, G., Bernal-C´ardenas, C., Di Penta, M., Oliveto, R., and Poshyvanyk, D. (2013). Api change and fault proneness: A threat to the success of android apps. In Proceedings of the 2013 9th Joint Meeting on Foundations of Software Engineering, ESEC/FSE 2013, pages 477–487, New York, NY, USA. ACM.
Mosqueira-Rey, E., Alonso-R´ıos, D., Moret-Bonillo, V., Fern´andez-Varela, I., and A´ lvarez Este´vez, D. (2018). A systematic approach to api usability: Taxonomy-derived criteria and a case study. Information and Software Technology, 97:46 – 63.
Robbes, R., Lungu, M., and R¨othlisberger, D. (2012). How do developers react to api deprecation?: The case of a smalltalk ecosystem. In Proceedings of the ACM SIGSOFT 20th International Symposium on the Foundations of Software Engineering, FSE ’12, pages 56:1–56:11, New York, NY, USA. ACM.
Robillard, M. P. (2009). What makes apis hard to learn? answers from developers. IEEE Software, 26(6):27–34.
Sawant, A. A., Aniche, M., van Deursen, A., and Bacchelli, A. (2018). Understanding developers’ needs on deprecation as a language feature. In 2018 IEEE/ACM 40th International Conference on Software Engineering (ICSE), pages 561–571.
Stylos, J. and Clarke, S. (2007). Usability implications of requiring parameters in objects’ constructors. In Proceedings of the 29th International Conference on Software Engineering, ICSE ’07, pages 529–539, Washington, DC, USA. IEEE Computer Society.
Stylos, J. and Myers, B. A. (2006). Mica: A web-search tool for finding api components and examples. In Visual Languages and Human-Centric Computing (VL/HCC’06), pages 195–202.
Wang, S., Lo, D., and Jiang, L. (2013). An empirical study on developer interactions in stackoverflow. In Proceedings of the 28th Annual ACM Symposium on Applied Computing, SAC ’13, pages 1019–1024, New York, NY, USA. ACM.
Wijayarathna, C., Arachchilage, N. A. G., and Slay, J. (2017). A generic cognitive dimensions questionnaire to evaluate the usability of security apis. In Tryfonas, T., editor, Human Aspects of Information Security, Privacy and Trust, pages 160–173, Cham. Springer International Publishing.
Bogart, C., K¨astner, C., Herbsleb, J., and Thung, F. (2016). How to break an api: cost negotiation and community values in three software ecosystems. In Proceedings of the 2016 24th ACM SIGSOFT International Symposium on Foundations of Software Engineering, pages 109–120. ACM.
Brajesh, D. (2017). API Management, pages 15–28. Apress, Berkeley, CA.
Brito, G., Hora, A., Valente, M. T., and Robbes, R. (2016). Do developers deprecate apis with replacement messages? a large-scale analysis on java systems. In 2016 IEEE 23rd International Conference on Software Analysis, Evolution, and Reengineering (SANER), volume 1, pages 360–369.
Cataldo, M. and d. Souza, C. R. B. (2014). Exploring the impact of api complexity on failure-proneness. In 2014 IEEE 9th International Conference on Global Software Engineering, pages 36–45.
Ellis, B., Stylos, J., and Myers, B. (2007). The factory pattern in api design: A usability evaluation. In Proceedings of the 29th International Conference on Software Engineering, ICSE ’07, pages 302–312, Washington, DC, USA. IEEE Computer Society.
Komssi, M., Pichlis, D., Raatikainen, M., Kindstr¨om, K., and J¨arvinen, J. (2015). What are hackathons for? IEEE Software, 32(5):60–67.
Linares-V´asquez, M., Bavota, G., Bernal-C´ardenas, C., Di Penta, M., Oliveto, R., and Poshyvanyk, D. (2013). Api change and fault proneness: A threat to the success of android apps. In Proceedings of the 2013 9th Joint Meeting on Foundations of Software Engineering, ESEC/FSE 2013, pages 477–487, New York, NY, USA. ACM.
Mosqueira-Rey, E., Alonso-R´ıos, D., Moret-Bonillo, V., Fern´andez-Varela, I., and A´ lvarez Este´vez, D. (2018). A systematic approach to api usability: Taxonomy-derived criteria and a case study. Information and Software Technology, 97:46 – 63.
Robbes, R., Lungu, M., and R¨othlisberger, D. (2012). How do developers react to api deprecation?: The case of a smalltalk ecosystem. In Proceedings of the ACM SIGSOFT 20th International Symposium on the Foundations of Software Engineering, FSE ’12, pages 56:1–56:11, New York, NY, USA. ACM.
Robillard, M. P. (2009). What makes apis hard to learn? answers from developers. IEEE Software, 26(6):27–34.
Sawant, A. A., Aniche, M., van Deursen, A., and Bacchelli, A. (2018). Understanding developers’ needs on deprecation as a language feature. In 2018 IEEE/ACM 40th International Conference on Software Engineering (ICSE), pages 561–571.
Stylos, J. and Clarke, S. (2007). Usability implications of requiring parameters in objects’ constructors. In Proceedings of the 29th International Conference on Software Engineering, ICSE ’07, pages 529–539, Washington, DC, USA. IEEE Computer Society.
Stylos, J. and Myers, B. A. (2006). Mica: A web-search tool for finding api components and examples. In Visual Languages and Human-Centric Computing (VL/HCC’06), pages 195–202.
Wang, S., Lo, D., and Jiang, L. (2013). An empirical study on developer interactions in stackoverflow. In Proceedings of the 28th Annual ACM Symposium on Applied Computing, SAC ’13, pages 1019–1024, New York, NY, USA. ACM.
Wijayarathna, C., Arachchilage, N. A. G., and Slay, J. (2017). A generic cognitive dimensions questionnaire to evaluate the usability of security apis. In Tryfonas, T., editor, Human Aspects of Information Security, Privacy and Trust, pages 160–173, Cham. Springer International Publishing.
Publicado
03/10/2019
Como Citar
D. COELHO, Filipe; R.B. DE SOUZA, Cleidson; A. RODRIGUES, Emanuel.
Gestão de API Realmente Melhora a Relação com Desenvolvedores?. In: PESQUISAS EM ANDAMENTO - SIMPÓSIO BRASILEIRO DE SISTEMAS COLABORATIVOS (SBSC), 15. , 2019, Rio de Janeiro.
Anais [...].
Porto Alegre: Sociedade Brasileira de Computação,
2019
.
p. 87-92.
