ABSTRACT
Organizations that produce software cooperatively and competitively to satisfy customer needs give more attention in relationships among several actors (e.g., providers, developers, and IT managers) to build the value creation network called Software Ecosystem (SECO). As a type of SECO, proprietary SECO concerns data concentrated on a platform with contributions protected by intellectual property. The technological platform that supports the business initiatives is developed using different technologies with dozens of integration points, promoting a network of dependencies and architectural complexities. Some studies show that systems downtime (incidents) causes major image and financial upheavals for organizations. To mitigate the risks of incidents, the IT management team should implement strategies based on governance mechanisms to sustain the platform. Our work aims to develop and evaluate a process-based approach (PSECO-IM) for incident management to support the IT management team in the governance of a technology platform architecture in a proprietary SECO. We also addressed some of the identified challenges of quality in proprietary SECO, such as standardized software processes, knowledge management, and governance strategies. As a final result, we got positive feedback on the relevance of the tool in improving governance strategies related to incident management by the organization’s practitioners. We argue that this work is appropriate for the Software Quality area since it covers studies on three pillars: people, process, and technology, such as tacit knowledge, low-quality software, governance, incident management, and proprietary SECO.
- Carina Alves, Joyce Oliveira, and Slinger Jansen. 2017. Understanding governance mechanisms and health in software ecosystems: A systematic literature review. In International Conference on Enterprise Information Systems. Springer, 517–542.Google Scholar
- Luiz Alexandre Costa. 2022. PSECO-IM: An Approach for Incident Management to Support Governance in Proprietary Software Ecosystems. Master’s thesis. PPGI UNIRIO, Rio de Janeiro, Brazil.Google Scholar
- Luiz Alexandre Costa, Awdren Fontão, and Rodrigo Santos. 2020. Investigating asset governance mechanisms in a proprietary software ecosystem. In XVI Brazilian Symposium on Information Systems. 1–8.Google ScholarDigital Library
- Luiz Alexandre Costa, Awdren Fontão, and Rodrigo Santos. 2020. Uma Abordagem para Gestão de Incidentes em Ecossistemas de Software Proprietário. In Anais Estendidos do XVI Simpósio Brasileiro de Sistemas de Informação. SBC, 52–55.Google Scholar
- Luiz Alexandre Costa, Awdren Fontão, and Rodrigo Santos. 2021. Investigating Proprietary Software Ecosystem Governance and Health: An Updated and Refined Perspective. In XVII Brazilian Symposium on Information Systems. 1–8.Google Scholar
- Luiz Alexandre Costa, Awdren Fontão, and Rodrigo Santos. 2021. Toward Proprietary Software Ecosystem Governance Strategies Based on Health Metrics. IEEE Transactions on Engineering Management(2021).Google Scholar
- Mehran Badin Dahesh, Gholamali Tabarsa, Mostafa Zandieh, and Mohammadreza Hamidizadeh. 2020. Reviewing the intellectual structure and evolution of the innovation systems approach: A social network analysis. Technology in Society 63(2020), 101399.Google ScholarCross Ref
- Fred D Davis. 1993. User acceptance of information technology: system characteristics, user perceptions and behavioral impacts. International journal of man-machine studies 38, 3 (1993), 475–487.Google ScholarDigital Library
- Deepak Dhungana, Iris Groher, Elisabeth Schludermann, and Stefan Biffl. 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. 96–102.Google ScholarDigital Library
- Yvonne Dittrich. 2014. Software engineering beyond the project–Sustaining software ecosystems. Information and Software Technology 56, 11 (2014), 1436–1456.Google ScholarCross Ref
- Elsayed A Elsayed. 2020. Reliability engineering. John Wiley & Sons.Google Scholar
- Awdren Fontão, Bruno Ábia, Igor Wiese, Bernardo Estácio, Marcelo Quinta, Rodrigo Pereira dos Santos, and Arilo Claudio Dias-Neto. 2018. Supporting governance of mobile application developers from mining and analyzing technical questions in stack overflow. Journal of Software Engineering Research and Development 6, 1(2018), 8.Google ScholarCross Ref
- Daniel Galin. 2004. Software quality assurance: from theory to implementation. Pearson education.Google Scholar
- Michael Grieves and John Vickers. 2017. Digital twin: Mitigating unpredictable, undesirable emergent behavior in complex systems. In Transdisciplinary perspectives on complex systems. Springer, 85–113.Google Scholar
- Alan R Hevner. 2007. A three cycle view of design science research. Scandinavian journal of information systems 19, 2 (2007), 4.Google Scholar
- Marco Iansiti and Roy Levien. 2004. Strategy as ecology.Harvard business review 82, 3 (2004), 68–78.Google Scholar
- Marcio Imamura, Luiz Alexandre Costa, Bruno Pereira, Francisco Henrique Ferreira, Awdren Fontao, and Rodrigo Pereira dos Santos. 2020. Fatores de Governança em Sistemas-de-Sistemas: Análise de uma Instituição Pública Brasileira. In Anais do V Workshop sobre Aspectos Sociais, Humanos e Econômicos de Software. SBC, 31–40.Google Scholar
- Slinger Jansen, Sjaak Brinkkemper, and Anthony Finkelstein. 2009. Business Network Management as a Survival Strategy: A Tale of Two Software Ecosystems.Iwseco@ Icsr 2009(2009).Google Scholar
- Slinger Jansen, Anthony Finkelstein, and Sjaak Brinkkemper. 2009. A sense of community: A research agenda for software ecosystems. In 2009 31st International Conference on Software Engineering-Companion Volume. IEEE, 187–190.Google ScholarCross Ref
- John O Long. 2012. ITIL® 2011 at a Glance. Springer Science & Business Media.Google Scholar
- Konstantinos Manikas. 2016. Revisiting software ecosystems research: A longitudinal literature study. Journal of Systems and Software 117 (2016), 84–103.Google ScholarDigital Library
- Rodrigo Santos, George Valença, Davi Viana, Bernardo Estácio, Awdren Fontão, Sabrina Marczak, Cláudia Werner, Carina Alves, Tayana Conte, and Rafael Prikladnicki. 2014. Qualidade em ecossistemas de software: Desafios e oportunidades de pesquisa. In Proceedings of VIII Workshop on Distributed Software Development, Software Ecosystems and Systems-of-Systems. 41–44.Google Scholar
- Rodrigo Pereira Santos 2012. ReuseECOS: An approach to support global software development through software ecosystems. In 2012 IEEE Seventh International Conference on Global Software Engineering Workshops. IEEE, 60–65.Google ScholarDigital Library
- Anselm Strauss and Juliet Corbin. 1998. Basics of qualitative research techniques. Citeseer.Google Scholar
- Li Da Xu, Eric L Xu, and Ling Li. 2018. Industry 4.0: state of the art and future trends. International journal of production research 56, 8 (2018), 2941–2962.Google Scholar
Index Terms
- PSECO-IM: An Approach for Incident Management to Support Governance in Proprietary Software Ecosystems
Recommendations
Investigating Asset Governance Mechanisms in a Proprietary Software Ecosystem
SBSI '20: Proceedings of the XVI Brazilian Symposium on Information SystemsThe reuse of artifacts generated throughout the proprietary software development has been improved to support and promote relationships among vendors, consumers and a central organization that maintains the common technological platform. This scenario ...
Investigating Proprietary Software Ecosystem Governance and Health: An Updated and Refined Perspective
SBSI '21: Proceedings of the XVII Brazilian Symposium on Information SystemsAlthough the approaches conceptualizing software ecosystems (SECO) have gained more relevance since 2010, there are not many studies addressing proprietary SECO. In a proprietary SECO, organizations are concerned with keeping their assets protected by ...
Ecosystems effects on software-consuming organizations: an experience report on two observational studies
ECSA '18: Proceedings of the 12th European Conference on Software Architecture: Companion ProceedingsSoftware engineers should have the ability to abstract the complexity of a whole system composed of products, demands and suppliers emerging from an interconnected network termed a software ecosystem (SECO). Since software suppliers resort to virtual ...
Comments