Investigating Change and Incident Management in a Proprietary Software Ecosystem - Survival Mode On

  • Luiz Alexandre Costa UNIRIO
  • Alexandre Sampaio Universidade de Aveiro
  • Awdren Fontão UFMS
  • Rodrigo Pereira dos Santos UNIRIO

Resumo


Ecossistemas de Software Proprietário (ECOSP) são aqueles que concentram o conhecimento em uma plataforma de software fechado. O crescente número de demandas faz com que as organizações trabalhem em ritmo acelerado para entregar resultados. Mudanças e incidentes impactam negativamente na carga de trabalho, comprometendo sua estabilidade. A partir de um estudo de caso em uma grande organização internacional de seguros, este trabalho tem como objetivo verificar o comportamento das equipes de desenvolvimento sob o ponto de vista das mudanças e incidentes no ECOSP. Foram utilizados os seguintes métodos de pesquisa: i) automação robótica de processos; ii) mineração de dados; e iii) análise de redes sociais. Como resultado, este estudo serve como um alerta para a diretoria de TI da organização quanto à governança dos processos tradicionais de desenvolvimento de software para que sobrevivam em um mercado competitivo.

Referências

Addy, R. (2007). Effective IT service management: to ITIL and beyond! Springer-Verlag.

Alves, C., Oliveira, J., and Jansen, S. (2017). Understanding governance mechanisms and health in software ecosystems: A systematic literature review. In International Conference on Enterprise Information Systems, pages 517–542. Springer.

Blondel, V. D., Guillaume, J.-L., Lambiotte, R., and Lefebvre, E. (2008). Fast unfolding of communities in large networks. Journal of Statistical Mechanics: theory and experiment, 2008(10):P10008.

Bosch, J. (2009). From software product lines to software ecosystems. In SPLC, volume 9, pages 111–119.

Brown, C. V. (2003). The it organization of the future. Competing in the Information Age: Align in the Sand (Ed, Luftman, JN). Oxford University Press, New York, NY, pages 191–207.

Costa, L. A., Fontão, A., and Santos, R. (2021). Toward proprietary software ecosystem governance strategies based on health metrics. IEEE Transactions on Engineering Management, 69(6):3589–3603.

Dahesh, M. B., Tabarsa, G., Zandieh, M., and Hamidizadeh, M. (2020). Reviewing the intellectual structure and evolution of the innovation systems approach: A social network analysis. Technology in Society, 63:101399.

Davis, J. and Daniels, R. (2016). Effective DevOps: building a culture of collaboration, affinity, and tooling at scale. “O’Reilly Media, Inc.”.

Dhungana, D., Groher, I., Schludermann, E., and Biffl, S. (2010). Software ecosystems vs. natural ecosystems: learning from the ingenious mind of nature. In Proceedings of the Fourth European Conference on Software Architecture: Companion Volume, pages 96–102.

Grieves, M. and Vickers, J. (2017). Digital twin: Mitigating unpredictable, undesirable emergent behavior in complex systems. Transdisciplinary Perspectives on Complex Systems: New findings and approaches, pages 85–113.

Gross, J. L., Yellen, J., and Anderson, M. (2018). Graph theory and its applications. Chapman and Hall/CRC.

Jafari, P., Mohamed, E., Lee, S., and Abourizk, S. (2020). Social network analysis of change management processes for communication assessment. Automation in Construction, 118:103292.

Jansen, S., Brinkkemper, S., and Finkelstein, A. (2009). Business network management as a survival strategy: A tale of two software ecosystems. IWSECO@ ICSR, 2009.

Kappelman, L. A., McKeeman, R., and Zhang, L. (2006). Early warning signs of it project failure: The dominant dozen. Information Systems Management, 23(4):31–36.

Lahtela, A. and Jäntti, M. (2011). Challenges and problems in release management process: A case study. In 2011 IEEE 2nd International Conference on Software Engineering and Service Science, pages 10–13. IEEE.

Lee, S. J. and Siau, K. (2001). A review of data mining techniques. Industrial Management & Data Systems.

Manikas, K. and Hansen, K. M. (2013). Software ecosystems–a systematic literature review. Journal of Systems and Software, 86(5):1294–1306.

Paszkiewicz, Z. and Picard, W. (2013). Analysis of the Volvo IT incident and problem handling processes using process mining and social network analysis. In BPIC@ BPM.

Runeson, P., Host, M., Rainer, A., and Regnell, B. (2012). Case study research in software engineering: Guidelines and examples. John Wiley & Sons.

Santos, R. P. and Werner, C. M. L. (2011). A proposal for software ecosystems engineering. In IWSECO@ ICSOB, pages 40–51.

Tranfield, D., Denyer, D., and Smart, P. (2003). Towards a methodology for developing evidence-informed management knowledge by means of systematic review. British Journal of Management, 14(3):207–222.

Wohlin, C., Runeson, P., Höst, M., Ohlsson, M. C., Regnell, B., and Wesslén, A. (2012). Experimentation in Software Engineering. Springer Science & Business Media.

Yin, R. K. (2005). Introducing the world of education: A case study reader. Sage.
Publicado
06/08/2023
Como Citar

Selecione um Formato
COSTA, Luiz Alexandre; SAMPAIO, Alexandre; FONTÃO, Awdren; SANTOS, Rodrigo Pereira dos. Investigating Change and Incident Management in a Proprietary Software Ecosystem - Survival Mode On. In: BRAZILIAN WORKSHOP ON SOCIAL NETWORK ANALYSIS AND MINING (BRASNAM), 12. , 2023, João Pessoa/PB. Anais [...]. Porto Alegre: Sociedade Brasileira de Computação, 2023 . p. 55-66. ISSN 2595-6094. DOI: https://doi.org/10.5753/brasnam.2023.229809.

Artigos mais lidos do(s) mesmo(s) autor(es)

1 2 3 4 > >>