Abstract
Introduction:
We call Software Ecosystems (SECOs) the development of software around a common technology platform that results in a set of solutions or services for a consumer market. The Integrated Management System (SIG-UFRN) of the Federal University of Rio Grande do Norte (UFRN) is a technological platform that forms part of the UFRN SECO and is used by a considerable number of Federal Educational Institutions (FEIs) throughout Brazil. The scenarios of use of the technology platform involve a complex mix of technical, social, and business aspects that can lead to the adoption or rejection of the SIG-UFRN. If these aspects are not observed, they can harm the business activities of the FEI, waste resources, and result in penalties for public managers who make poor decisions. This research aimed to construct and validate a theoretical framework that represents the adoption of the SIG-UFRN based on technical, business, and social factors.
Methods:
To achieve this objective, Selective Coding, as defined in the Grounded Theory (GT) method, was used, as well as Focus Groups for validation. Selective coding is the third stage of the GT. This refines and integrates concepts to construct a theoretical framework for a phenomenon. This coding process enabled the refinement and interrelation of the concepts inherent in the adoption scenarios of the SIG-UFRN. These concepts were identified in the previous open and axial coding stages of GT. Using techniques such as Storyline Memo, Core Category, and Paradigm Model, a theoretical framework could be constructed representing the adoption of SIG-UFRN.
Results:
We identified a theoretical framework that explained the adoption process of the SIG-UFRN, which was then validated with stakeholders.
Discussion:
The results of this study could influence the success or failure of the adoption process and guide stakeholders in adopting SIG-UFRN best practices.
1 Introduction
The design and development of Software Ecosystems platforms (SECOs) has advanced in both theoretical and applied research, introducing challenges that extend beyond technical issues (). In this context, an SECO represents a new approach to software product development (). Thus, we can initially conceptualize a software ecosystem as a set of actors that interact with a shared software and services market as a unit, along with the relationships between them. These relationships are often supported by a technological platform or a common market, operating through the exchange of information, resources, and artifacts ().
) also highlight the relationships between actors within a technological platform, conceptualizing SECOs as environments centered on software platforms where actors interact with each other and use artifacts.
The interactions between the actors that make up a SECO involve three dimensions: technical, social, and business (). ) conceptualize these dimensions as follows:
Technical: This dimension covers the technologies employed by SECOs, development standards and resources, application quality, and other technology-related matters. Examples of elements in this dimension include the programming languages supported by SECOs and the development kits and environments used to create applications (apps),
Social: This refers to the people who are part of a SECO's community, their relationships with each other, and their relationship with the software ecosystem itself. This enables third parties to develop applications for a particular platform. This can be observed in the mobile device market through corporations such as Apple and Google. Examples of elements in this dimension include studies that identify the motivations of software developers and studies that investigate user sentiment regarding certain technologies,
Business: This includes finances, software sales, development pipelines, and employment opportunities for software developers. This dimension addresses the future vision, innovation, and strategic planning of SECO-holding companies. Examples of elements within this dimension include comparisons of app store profitability in two different SECOs and studies of the distribution of the same application in several countries.
) analyzed the interaction between stakeholders (e.g., clients, developers, technology platforms, and companies) around a common technology platform. Through a case study of two open-source companies, researchers developed an understanding of the relationship between the health of a SECO (Software Engineering Competence Organization) and the financial performance of software development companies. In this study, companies were evaluated using several metrics, including the “commits to projects” metric, which represents the number of times a project was modified by a developer and belongs to the social dimension of SECOs. This metric is related to the health of a software ecosystem. The “return on equity” metric indicates how much profit a company generates from shareholder investments and belongs to the business dimension of SECOs, being related to financial performance.
) investigated the consequences of the official discontinuation of the main platform of a software ecosystem. Initially, the focus was on the Windows Phone platform and its impact on developers within this ecosystem. The study analyzed metrics such as view count, response count, comment count, favorite count, and score using a repository of questions and answers from platform developers. These metrics are associated with the social dimension of the SECOs.
) conducted an exploratory study to observe the evolution of Application Programming Interfaces (APIs) and their impact on a large-scale software ecosystem. The researchers analyzed 118 API changes to answer research questions concerning the magnitude, duration, extent, and consistency of these changes within the software ecosystem. These metrics fall within the technical dimension of SECOs.
Studies such as these demonstrate the importance of analyzing SECOs using the three-dimensional approach developed by ). For each dimension analyzed, it is possible to investigate, systematize, and develop theories about events occurring within a software ecosystem in the context of a specific event.
The Integrated Management Systems of the Federal University of Rio Grande do Norte (SIG-UFRN) in Brazil is a technological platform developed to computerize the business activities of the university's three core functions (teaching, research, and outreach) and its central operations. SIG-UFRN enables the university to:
Offer fundamental operations for the management of UFRN's finances and heritage through the Integrated Patrimony, Administration, and Contracts Management System (SIPAC),
Computerize human resource procedures through the Integrated Human Resources Management System (SIGRH), and
Computerize academic area procedures with the Integrated Academic Activities Management System (SIGAA). This technology platform is used by a considerable number of Brazilian Federal Educational Institutions (FEIs) distributed throughout the country, where they act as niche players, supporting this platform as part of the SIG-UFRN software ecosystem.
In terms of usage, there are several scenarios for adopting the SIG-UFRN ecosystem that involve technical, social, and business factors (), which determine the current implementation of the technological platform in FEIs. This can lead to success or failure in adopting the SIG-UFRN ecosystem. Success is characterized by the FEI using the technological platform to computerize its business processes, receiving new functionalities from the centralizer (UFRN) and developing modifications to meet its particular needs. This contributes to the sustainability of the software ecosystem.
In order for a public or private body in Brazil to adopt the SIG-UFRN software ecosystem, financial resources must be decentralized for the benefit of the Federal University of Rio Grande do Norte (UFRN), the entity that maintains the ecosystem. The amount to be transferred, which is associated with the business dimension (), is calculated on the basis of the entity's profile and the type of support required by its technical and business teams for the technological platform to be implemented in its IT infrastructure and used by its end users. For example, upon joining the ecosystem, the Federal Rural University of the Amazon (UFRA) disbursed the amount of R$255,011.96 (two hundred and fifty-five thousand and eleven reais and ninety-six cents) to UFRN, according to Resolution UFRN-CONSAD No. 51/2020 ().
In this case, the resources disbursed over a given period must be shown to have generated beneficial returns for the adopting entity. This is particularly important for public organizations, which are subject to inspections by control bodies and may face penalties for misusing public funds. In the federal sphere, a special audit of accounts may be instituted in the event of non-execution of the objective, a lack of connection between the incurred expenses and the agreed objective, or deviation from the objective, among other irregularities (). This justifies the research, as a set of factors associated with the three dimensions () can influence the misuse of public resources directly or indirectly depending on the adoption scenarios of the SIG-UFRN software ecosystem. Therefore, it is of the utmost importance to discover and analyze these factors in their respective dimensions and to highlight them. This will enable us to identify and address any inconsistencies that could impact the success or failure of adopting this software ecosystem. This is important because public resources are scarce and could be allocated to other government initiatives that would benefit Brazilian citizens. It would also eliminate the need for FEIs to invest further to meet their software requirements when SIG-UFRN SECO could fulfill these requirements.
In this scenario, the technical, social, and business factors inherent in the adoption of the SIG-UFRN software ecosystem, which can be used by FEI managers a priori to evaluate the viability of the ecosystem, have been identified in ). These factors were identified using open and axial coding techniques of grounded theory (). However, for these factors to constitute a theory explaining the adoption of the SIG-UFRN software ecosystem, they must be integrated and validated to reach theoretical saturation, whereby no new concepts can be found to explain the adoption of this ecosystem, meaning that no further information can be incorporated into the explanation of this phenomenon.
Unlike previous studies, this research does not focus exclusively on technical SECO processes (as in ), social aspects (as in ), or business and social aspects (as in ). Instead, we have developed a comprehensive theory that interrelates technical, social, and business factors to explain why FEIs chose to adopt the Brazilian SIG-UFRN SECO.
Therefore, our research problem lies in the absence of a theoretical framework for the adoption of the SIG-UFRN software ecosystem based on the identified technical, social, and business factors. Analyzing this theoretical framework can help public managers of FEIs who are interested in adopting this ecosystem determine the success or failure of this process. To this end, we intend to answer the following research question: “Is there a theoretical framework that can explain the adoption of the SIG-UFRN software ecosystem?”
This article presents a theoretical framework that explains why FEI in Brazil adopted the SIG-UFRN software ecosystem. This was achieved by applying the selective coding technique based on the grounded theory of ), which facilitated the development of this theoretical framework to explain the adoption of the SIG-UFRN software ecosystem. This framework is the result of applying grounded theory to the technical, social, and business factors identified by ) as capable of influencing the success or failure of adopting the SIG-UFRN software ecosystem. The framework was validated with FEI software developers who adopted the ecosystem.
In addition to this introductory section, which justifies and identifies the objective of this investigation, the article is structured as follows: Section 2 presents the SIG-UFRN software ecosystem; Section 3 presents some related work; Section 4 presents the methodology used in this research; Section 5 details the results of this research; Section 6 presents a discussion of the results; Section 7 describes threats to the validity of this study; and Section 8 presents the conclusions of the study.
2 SIG-UFRN software ecosystem
According to ), the Integrated Management Systems of the Federal University of Rio Grande do Norte (SIG-UFRN) is a technological platform developed to computerize the university's business and support activities. SIG-UFRN offers, through the Integrated Patrimony, Administration, and Contracts Management System (SIPAC), fundamental operations for the management of units responsible for the finances, assets, and contracts of UFRN, being, therefore, active in the support activities of this institution, fully integrating the administrative area from the requisition (material, service provision, supply of funds, daily allowances, tickets, accommodation, informational material, infrastructure maintenance) to the control of the internal distributed budget ().
The Integrated Human Resources Management System (SIGRH) computerizes HR procedures such as scheduling/changing holidays, calculating retirement benefits, workforce assessment, attendance control and electronic timekeeping, financial operations, competitions, training, in-person service queues, services and requests, functional records, and HR reports ().
The Academic Activities Management System (SIGAA) computerizes academic procedures through the following modules: undergraduate education, postgraduate education, technical education, high school education, preschool education, submission and control of research projects and scholarship holders, submission and control of extension activities, submission and control of teaching projects (monitoring and innovations), recording and reporting of academic production by professors, distance learning activities, and a virtual learning environment ().
Another notable feature is the Integrated Administration and Communication Management System (SIGAdmin), which serves as the administrative and management hub for the aforementioned three integrated systems. Manage common entities among computerized systems, such as users, permissions, units, messages, news, websites, and portal management, as well as other functionalities. Access to SIGAdmin is restricted to system managers and administrators only ().
SIG-UFRN enables the interconnection of information on various topics relating to the computerization of the university's business processes via a single login, facilitating efficient management and effective decision-making. This interconnection of information suggests that the SIG-UFRN was developed based on Enterprise Resource Planning (ERP) applications. An ERP application is a management model based on information systems that integrate business processes and support strategic decision-making. It is based on a single, centralized corporate database that receives and provides data from a set of applications supporting many of a company's functions in an integrated software solution ().
Over the years, the development of new features in SIG-UFRN has intensified. In addition, a considerable number of public bodies in Brazil use the technological platform to computerize their business processes (). In response to this, UFRN has expanded its support structure for the technological platform, establishing governance, collaborative development, and financial incentive mechanisms to benefit the cooperative network being formed. This support structure is characterized as a software ecosystem consisting of a group of actors (software engineers, licensed companies, public bodies, and end users) who interact with the aim of adding value to their businesses by using and contributing to the development of the SIG-UFRN platform. The SIG-UFRN software ecosystem comprises the following elements ():
SIG-UFRN Systems: Set of systems developed within the scope of UFRN that directly or indirectly enable the operationalization and optimization of work processes relating to the academic, administrative, and personnel management of the university, as well as other direct or indirect administrative bodies at federal, state, and municipal levels,
Cooperation Ecosystem: Set of public and private institutions (UFRN, cooperative institutions, and licensed companies) that cooperate and interact with each other to create a functional environment of reciprocity for the evolution and aggregation of value to the SIG-UFRN system,
UFRN: Institution that created and maintains the SIG-UFRN systems,
Cooperating Institutions: Public institutions that receive the transfer of the SIG-UFRN systems and become part of the SIG-UFRN Public Network,
Licensed Companies: Companies in the IT sector whose corporate purpose is compatible with the SIG-UFRN systems. These companies are granted the right to explore these systems through licensing contracts under the terms of Article 6 of Brazilian Law 10,973/04,
SIG Software Architecture: This architecture enables us to abstract the complexity of implementing Java Enterprise Edition (JEE) systems, as well as defining coding, visualization, and navigation standards for web systems. All developed systems were based on this architecture ().
Therefore, the SIG-UFRN technological platform comprises the SIG-UFRN system and the SIG software architecture. Figure 1 shows a representation of the SIG-UFRN software ecosystem.
Figure 1
3 Related works
Several researchers have analyzed software ecosystems from technical, business, and social perspectives, as specified by ), and constructed theories that explain the contexts of these SECOs.
) conducted an exploratory study in which actors and roles operating within a public domain software ecosystem were first identified through technical relationships, interviews, and questionnaires. This enabled analysis of the factors and roles of the actors within this SECO.
Based on these interviews, a framework was developed to suggest which actors exert the greatest influence in maintaining the balance of the public domain software ecosystem against threats from external agents in other SECOs. This framework took into account robustness as an indicator of SECO health.
Although this study presents a conceptual framework for identifying actors that can positively support the health of a SECO, it does not categorize the technical, social, and business elements that determine what motivates and facilitates the adoption of this public domain SECO. Furthermore, the study did not employ GT coding techniques, specifically Strauss's selective coding, to analyze the collected data.
) conducted an exploratory study to identify changes in APIs and observe their evolution and impact on a large-scale software ecosystem. In this case study, the authors examined the Pharo software ecosystem, which comprises approximately 3,600 distinct systems and more than 2,800 contributors, over a period of six years.
These API changes were identified by applying the association rule data mining technique () to a set of method calls that had changed between two revisions of a method. These rules were then applied to the Pharo Core framework, which provides a variety of APIs, including those for collections, files, sockets, unit tests, flows, exceptions, and graphical interfaces. Therefore, 118 API changes were analyzed to answer research questions concerning the magnitude, duration, extent, and consistency of such changes within the software ecosystem. The study resulted in the development of a theory that characterizes the impact of these API changes on the community within this software ecosystem. However, this theory only analyzes the technical aspects that impacted this SECO, as discussed in ).
) conducted a study to further investigate the impact of the official discontinuation of the main platform on a software ecosystem. Initially, the focus was on the Windows Phone platform and the impact of developers within the software ecosystem. To analyze this impact, researchers used data on developer behavior within the SECO from 46,030 questions in the Stack Overflow Q&A repositories. Of the data analyzed from the repository relating to Campbell and Ahmed's social dimension, we highlight view counts, reply counts, comment counts, favorite counts, and scores.
The result of this study was a theory explaining the behavior and relationships among software product developers after the technology platform was discontinued. This theory considers only social aspects ().
The study by ) investigated how public sector organizations establish and orchestrate free and open-source software (FOSS) ecosystems to overcome IT acquisition challenges, such as vendor lock-in. To carry out this research, a multiple case study was carried out with three SECOs. Semi-structured interviews were conducted with 16 informants from various roles (developers, technical managers, and product owners) within the ecosystems investigated. Document analysis of the collaborative platforms used by these ecosystems was also conducted. Although this study identified seven critical activities to maintain the health of the ecosystems under investigation, it did not specifically examine the factors determining success or failure at the time of SECO adoption.
) investigated the evolution of the Finnish public SECO Omaolo during the pandemic, highlighting how an external shock transformed static collaboration into agile and resilient alliances. Omaolo is a Finnish digital health and social services platform that enables citizens to assess their symptoms and receive medical advice. The research team conducted an interpretive case study based on nine semi-structured interviews with medical managers, project leaders, and developers, as well as analyzing public documents. Thematic analysis of the collected data focused on aspects of governance, business, technology, and regulation.
The study identified a set of best practices focused on nine themes that trigger agile dynamics within the ecosystem. These dynamics allow for risk sharing, the creation of synergistic knowledge, and the ability to respond to constant changes. Although ) investigate the evolution of an SECO by identifying best practices for maintaining health, their work does not present a complete theory that describes a phenomenon from the initial phase to the full utilization of a SECO's technological platform.
In ), a systematic literature review (SLR) was presented on the factors that led to the collapse of SECOs. The authors analyzed ten primary studies selected from scientific databases, focusing on SECOs of various sizes ranging from open-source private SECOs to those in the public sector. The analysis identified the reasons for the failure and mitigation activities proposed. Although this study provides a general theoretical overview of why ecosystems collapse, it lacks a detailed empirical basis for the specific challenges of the Brazilian public sector.
Unlike the aforementioned studies, our research does not focus exclusively on technical processes in SECOs, as in the study by ), nor on social aspects, as in the study by ). It focuses on the influence of actors in an SECOs against external threats, as in the study by ); the identification of critical activities to maintain ecosystem health, as in the study by ); investigating the evolution of SECOs by identifying best practices for maintaining health, as in the study by ); or building a general overview of reasons for failure and mitigation activities in different SECOs, as in the study ().
Instead, we have developed a comprehensive theory that interrelates the technical, social, and business factors identified through GT coding techniques. This theory explains the events that occurred when the Brazilian federal educational institutions chose to adopt the SIG-UFRN SECO. We also developed a methodology to apply the selective GT coding technique by ) to build a theoretical framework for the SIG-UFRN SECO adoption process. Additionally, we present this theoretical framework using the TOE&ABC () model, which explains how technological antecedents influence social behaviors that generate business consequences for FEIs.
Finally, our analysis of an SECO in the field of public and academic management is highly relevant in the Brazilian national context.
4 Materials and methods
To achieve the proposed goal, this research was conducted in three stages, as illustrated in Figure 2.
Figure 2
The methodology developed for this study took into account the need to analyze the adoption of the SIG-UFRN SECO. However, we were unaware of the tools that could be used to accomplish this task within the context of software ecosystems. Therefore, we conducted a Systematic Literature Review (SLR) to identify these tools. We found that stakeholder interviews were user primarily to collect data in software ecosystems, as well as GT coding techniques () to analyze the collected data.
To provide the reader with a better understanding of the context, it is important to note that GT coding techniques include open, axial, and selective coding, in that order (). This study presents the methodology developed for selective coding and the results obtained by applying this technique.
Based on this understanding and the proposed objective, the research was conducted in three stages, as shown in Figure 2. This section presents examples of results obtained in previous research that were used as input data for the selective coding process in each preceding methodological stage. Therefore, the main focus of this study is to present the results of the selective coding process, as well as the methodology for applying this coding technique, which utilizes the results obtained in preceding processes.
In the first stage, we conducted a SLR (), which aimed to identify the methods and/or techniques used by researchers to collect and analyze data on the technical, social, and business aspects of different software ecosystems. This SLR revealed that semistructured interviews were predominantly used as a data collection instrument (), and that grounded theory (GT) coding techniques () were predominantly used as an analysis instrument for the collected data. The full results of the SLR are available in ) and allow analysis of the SIG-UFRN software ecosystem.
In the second stage, we conducted semi-structured interviews () with FEI software developers in the northern, north-eastern, southern, and south-eastern regions of Brazil, which are related to the Ministry of Education and are part of the SIG-UFRN software ecosystem. These interviews were conducted individually at agreed times and dates. As a result of this stage, we obtained the perceptions and experiences of these developers regarding the adoption of the SIG-UFRN software ecosystem in their respective FEIs. The aim was to obtain responses related to the technical, business, and social aspects of this adoption process, as conceptualized in ).
According to Table 1, ten software developers with at least two years of experience implementing the SIG-UFRN software ecosystem technology platform in their respective FEIs were interviewed. Interviewees I3 and I6 represented the same institution (FEI3). The nine institutions that participated in this research represent around 17% of the FEI universe within the SIG-UFRN SECO.
Table 1
| Interviewee (I) | FEI | Brazilian region | Experience |
|---|---|---|---|
| I1 | FEI1 | South | He works at FEI for 12 years, acts as Coordinator of the Support Team, and participated in the implementation of SIG-UFRN for 3 years. |
| I2 | FEI2 | South | He works at FEI for 11 years, and acts as General Coordinator of the SIG-UFRN implementation project. |
| I3 | FEI3 | North | He works at the institution for 6 years, and participated in the implementation of the SIGAA, SIPAC, and SIGRH systems. |
| I4 | FEI4 | Northeast | He works at FEI for 4 years, and participated in the implementation of SIG-UFRN, analyzing requirements to implement the modules. |
| I5 | FEI5 | Southeast | He works at FEI for 12 years, and coordinates the technical team for the implementation of SIG-UFRN, in addition to implementing new features in the systems. |
| I6 | FEI3 | North | He works at FEI for 12 years, and participated in the implementation, customization, and bug fixes of SIG-UFRN. |
| I7 | FEI7 | Northeast | He works at FEI for 16 years, and coordinates the technical team for the implementation of SIG-UFRN, acting as a Business Analyst in many systems. |
| I8 | FEI8 | Southeast | He works for 12 years at FEI, and participates in the SIG-UFRN implementation committee and in the implementation of features in the systems. |
| I9 | FEI9 | Southeast | He works for 15 years at FEI, and participates as a Leader of the technical team for the implementation of SIG-UFRN, acting as a Business Analyst for identifying requirements. |
| I10 | FEI10 | Northeast | He works for 15 years at FEI, and acts as Coordinator of the SIG-UFRN implementation team, defining strategies for execution. |
Software developers interview ().
The questions that make up the interview script were taken from ) and adapted to the context of implementing the SIG-UFRN SECO technological platform. The script was designed to align with the implementation of ERP systems on the SIG-UFRN platform. The questions were organized according to the implementation process, corresponding to the stages of decision and selection, implementation, and use of the ERP systems. The interviews were transcribed with the support of the Reshape tool (www.reshape.com.br). The results of this interview stage were previously published in ), and the analysis of the results is available in ), and interview transcripts can be accessed in https://zenodo.org/record/18938691.
The ERP system deployment structure devised by ) is composed of phases and is considered appropriate for classifying the findings of the SIG-UFRN SECO adoption phenomenon. This is because the SIG-UFRN platform is characterized as an ERP system and this phased scheme was structured from a synthesis of various theoretical currents in software engineering and administration, adapted to the specific complexity of integrated systems. ) based his work on classic life cycle concepts, such as the linear (waterfall) model proposed by authors such as ). The scheme incorporates the contributions of ) and ) to the acquisition and maintenance of market packages. This is because the adoption of an ERP system involves the decision to purchase such technology. Finally, the scheme incorporates the rationale that the implementation of an ERP system is not just a technological event, but a process of profound change in work experience and organizational culture. This considers the theory of ).
The third stage involved a qualitative analysis of the data collected during the interviews, which was conducted using GT coding techniques (). Strauss and Corbin's Grounded Theory (GT) was chosen because it offers a systematized process or a structured protocol with three clear phases: open, axial, and selective coding. This allows the researcher to analyze the phenomenon under study and provides an exclusive tool for systematically ordering data (the Paradigm Model technique). Here, the researcher organizes facts and events around conditions (causal, intervening, and contextual), actions/interactions (strategies), and consequences, which facilitates the explanation of complex phenomena.
This stage was conducted in two phases. During the first period, open and axial coding techniques were applied to the interview data. This stage identified the factors influencing the adoption of the SIG-UFRN software ecosystem, i.e. the factors that could determine its success or failure. The Atlas.ti tool (https://atlasti.com/) was used to assist in the application process of open and axial coding techniques. The open coding of the interview data began with identifying the concepts representing the adoption of this ecosystem (codes), as well as the properties and dimensions related to these concepts (categories).
In axial coding, the data are grouped on the basis of the connections between codes and their categories. The codes were obtained by identifying relevant excerpts from the interviewees' responses to each of the questions in the interview script, as shown in Table 2.
Table 2
| Code | Evidence (Transcribed excerpt) |
|---|---|
| Legal Risk | “[E2]... The contract stated that people who were not servers could not access the source codes. They could use the system as long as they were servers, but they could not hire a company to help them use the system, even though the source codes were available.” |
| Maturity Level | “[E3]... For example, is this system already running successfully in other institutions? In other words, using a product that other users have already used and validated is a differentiator.” |
Interview excerpts and generated codes ().
Figure 3 shows an example of the “Selection Criteria” category, representing the criteria (codes) used by the FEI to evaluate technological alternatives to adopt the SIG-UFRN software ecosystem. Here, we demonstrate the evaluation criteria “Maturity Level”, “Technological Risk”, and “Legal Risk”. The grouping of these codes into categories allowed us to create coding networks for each question in the interview guide based on the responses provided by the research participants.
Figure 3
The application of open and axial coding techniques in GT resulted in a total of 268 codes/categories, which were grouped into 31 coding networks representing the adoption of the SIG-UFRN platform. These networks include the technical, social, and business factors that must be observed for the adoption process of this ecosystem to be successful. More details can be found in ). Readers can access the 31 code networks via the following link: https://zenodo.org/records/18818892.
The 268 codes/categories identified contain all the factors necessary to represent the phenomenon of software ecosystem adoption. As presented in Section 1, a set of interacting actors and a common technology platform that share software products and services involve different dimensions, as conceptualized by ). These dimensions can be mapped onto the aspects related to the ERP system implementation cycle, as conceptualized by ). The technical, social, and business aspects identified mapped the experience of the developers who participated in the SECO adoption process. This allowed us to analyze what happened during the process and identify elements that could lead to the successful adoption of SECO if observed.
Table 3 shows a summary of these factors and their respective dimensions ().
Table 3
| Factor | Dimension () |
|---|---|
| Integration | Business |
| Team/development time | Social |
| Institutional mobilization | Technical, social and business |
| Customization | Technical |
| Development of new features | Technical |
| Work teams | Technical and business |
| IT as an enabler/promoter of best practices | Social |
| Impossibility of updates (UFRN reference versions) | Technical |
| Outdated documentation of the SIG platform | Technical and social |
Summary of factors to be observed in the adoption of the SIG-UFRN ecosystem ().
In the context of adopting the SIG-UFRN software ecosystem, the “Integration” factor relating to the business dimension was used to evaluate alternative solutions. This factor assesses the capacity to connect information across the departments involved in FEIs' business administration, i.e., the capacity to integrate information between system modules within the academic, administrative, and human resources sectors. Another evaluation criterion was the “Team/Development Time” factor, which refers to the number of professionals from the companies required to support the evolution/maintenance of SECO's technological platform within the shortest possible timeframe for development. Both factors are present in the decision-making and selection stages of ERP systems.
The factor “Institutional Mobilization” also presents in the decision and selection stages (), allowed the analysis of alternatives to the SIG-UFRN software ecosystem based on the selection criteria to evaluate available technological alternatives, including the “Integration” and “Team/Development Time” criteria mentioned above. This institutional mobilization involved individuals responsible for the FEIs' business areas and other key personnel in these areas. This enabled the decision to favor SIG-UFRN SECO. As this factor involved analyzing various selection criteria to evaluate alternatives to SIG-UFRN SECO, it can be related to the technical, social, and business dimensions proposed by ).
The “Customisation” and “Development of New Features” factors provided by the SIG-UFRN technology platform helped overcome the difficulty of distinguishing the business rules of the central organization (UFRN) from those of the FEIs. This is because the SIG-UFRN technology platform was developed to reflect the business rules of SECO's central organization, the Federal University of Rio Grande do Norte (UFRN). The developers identified these factors as important for the success of the SECO adoption process. These factors are present in the decision, selection, and utilization stages of ERP systems () and are framed within the technical dimension ().
The “Work Teams” factor refers to the formation of FEI work teams to implement the SIG-UFRN technology platform. These teams were involved in the execution of some implementation activities. This factor was conceptualized within the technical and business dimensions () and is present in the implementation stage of ERP systems ().
The “IT as an enabler/promoter of best practices” factor addresses instances in which IT teams in FEIs advised on the benefits of implementing the SIG-UFRN technology platform, thus mitigating their IT service users' resistance to change. This factor is conceptualized within the social dimension () and is present in the implementation stage of ERP systems ().
The “Impossibility of updates (reference versions from UFRN)” factor is conceptualized within the technical dimension () and describes the difficulty of merging source code between the most recent version of the technological platform provided by SECO's central organization (UFRN) and the version customized by the FEI participating in this software ecosystem. This prevents the FEI from accessing corrections for unexpected behaviors, new functionalities, and new technologies made available by the most recent versions of the SIG-UFRN technological platform. This factor is present in the implementation and use stages of ERP systems ().
The “Outdated Documentation of the SIG Platform” factor is related to the deployment documentation and operating manuals for the SIG-UFRN technology platform and its functionalities, as provided by the central organization (UFRN). The interviewees reported that this documentation is outdated as it does not always reflect practical procedures.
The full results of this stage are finally available in ), which was also used as input data for the selective coding process in GT.
In the second and final periods, GT's selective coding technique () was applied to the 31 coding networks resulting from the open and axial coding techniques. This article presents the selective coding, which was carried out in four phases, as shown in Figure 4.
Figure 4
Phase 1, called creating the Storyline Memo, involved the construction of a Storyline Memo. According to ), memos are very specialized types of written record containing analysis products or directions for the analyst. They should be analytical and conceptual rather than descriptive. This Storyline Memo enabled the adoption phenomenon of the SIG-UFRN software ecosystem to be described through an analytical text representing a set of interrelated concepts inherent to this adoption process. The memo is an interpretation of the ecosystem's adoption concepts constructed by the researcher based on the technical, social, and business factors identified through open and axial coding techniques applied to the interview data.
Figure 5 shows a section of the constructed Storyline Memo. The words in bold or italics represent codes and/or categories, i.e., facts, actions, or events related to the adoption process of the SIG-UFRN software ecosystem. The complete Storyline Memo is available at https://zenodo.org/records/15104957.
Figure 5
After completing Phase 1, we proceed to Phase 2, which involves identifying the core category. According to ), the core category represents the main theme of the investigation. Although it emerges from research, it is also an abstraction. In an exaggerated sense, it consists of all the analytical findings, condensed into a few words, that explain “what the research is about”. In other words, it summarizes the phenomenon under study—in our case, the process of adopting the SIG-UFRN software ecosystem—in a few words.
The criteria used to identify the central category are those established in ), which are as follows:
It must be central, meaning that all other important categories can be related to it,
It must also appear frequently in the data. This means that, in almost all cases, there are indicators pointing to this concept,
The explanation resulting from the relationships among the categories must be logical and consistent. The data are not forced,
The name or phrase used to describe the central category must be sufficiently abstract to be applicable to other substantive areas, thus facilitating the development of a more general theory,
As the concept is refined analytically through integration with other concepts, the theory gains more depth and explanatory power,
The concept can explain variations in the data, i.e., when conditions vary, the explanation remains valid, although the way in which a phenomenon is expressed may appear slightly different. We must be able to explain contradictory or alternative cases in terms of this central idea.
Finally, ) state that, in selective coding, the researcher initially identifies the story that emerges from the data, before moving from description to conceptualization. In other words, the story is described analytically until the central phenomenon or category is discovered.
Phase 3 involved integrating the core category into the most important categories of the developed theoretical framework. This integration was carried out using the Paradigm Model technique. The paradigm model is simply a perspective taken in relation to the data—another analytical point of view that helps gather and order the data systematically, integrating the structure and process (). The basic components of the paradigm model are as follows ():
Conditions: A conceptual way of grouping answers to questions of why, where, how, and when. Together, they form a set of circumstances or situations in which the phenomena are incorporated, or the structure. These conditions are subdivided into causal, intervening, and contextual conditions:
- Causal Conditions: Generally represent a set of facts or events that influence the phenomenon,
- Intervening conditions mitigate or alter the impact of causal conditions on the phenomenon. These conditions always arise from contingencies (unexpected facts) and must be responded to with a form of action or interaction,
- Context conditions or context: These are specific sets of conditions that intersect at this time to create circumstances or problems to which people respond through actions or interactions. They originate from the causal and intervening conditions,
Actions/Interactions: Under these conditions, people or groups engage in strategic or routine responses to issues, problems, events, or facts. Actions and interactions are represented by questions such as “Who and how?”,
Consequences: Consequences are the results of actions/interactions. They are represented by questions such as “What happens as a result of these actions/interactions, or the failure of people or groups to respond to situations through actions/interactions?”.
Using the paradigm model allows the central category to be integrated with the most important categories of the theoretical scheme developed in Phase 1 (Storyline Memo Construction), as the concept is refined analytically through integration with other concepts, thereby giving the theory more depth and explanatory power ().
Figure 6 shows an example from the field of nursing research. It is a diagram extracted from ), in which the central category “Signifying the Pressure Ulcer Protocol as a qualification instrument for nurse's managerial care” was integrated with the main categories of the phenomenon under study, “Management of nursing care for patients with pressure ulcers (PUs)”. This integration was performed using the paradigm model technique.
Figure 6
Figure 6 shows that the central category, “Signifying the Pressure Ulcer Protocol as a Qualification Instrument for Nurse's Managerial Care”, is related to all the most important categories of the phenomenon under study: “Management of Nursing Care for Patients with Pressure Ulcers (PUs)”. These categories are logically related to the central category, demonstrating its great explanatory power in consolidating the explanation of the phenomenon “Management of nursing care for patients with pressure ulcers (PUs)”. We can observe that the category “Considering the protocol as a facilitating instrument for care” is a causal condition that allowed the phenomenon “Management of nursing care for patients with pressure ulcers (PUs)” to be analyzed through the consolidation of the analytical products represented by the central category.
The category “Considering the experiences and values of professionals in care management” (intervening condition) significantly affected the causal condition within the context of the category “Managing nursing care for patients with pressure ulcers”, enabling analysis of the phenomenon “Management of nursing care for patients with pressure ulcers”. This led to the consolidation of the analytical outputs represented by the central category.
In a specific context, the causal condition was affected by the intervening condition and produced a reaction in the form of actions or interactions. This reaction is represented by the categories “Individualizing patient care through protocols” and “Building concepts and definitions for protocols”. These actions and interactions resulted in the result represented by the category “Qualifying professionals to provide quality care”. Finally, Figure 6 provides the reader with a summarized, systematized view of the phenomenon “Management of nursing care for patients with pressure ulcers (PUs)”.
Therefore, the central category emerges at the end of the analysis and forms the pivot or main theme around which all other categories revolve. These main categories establish theoretical relationships between the categories and the central category ().
In Phase 4, the theoretical framework for ecosystem adoption was validated and the software developers who participated in the interview stage conducted a validation process of the theoretical framework (Table 1). The details and results of the selective coding stage are presented in Section 5.
5 Results
In this section, we present the results of applying the selective coding technique to the technical, social, and business factors that were identified.
According to ), if the goal of a research project is indeed to build theory, then the results should be presented as a set of interrelated concepts rather than a list of themes. In this case, the relational statements between the concepts are abstracted from the data rather than being descriptive details of each case (raw data). In other words, the analyst reduces the data from many cases into concepts and their relationships, which can be used to generally explain what is happening.
Completing Phase 1 of Selective Coding (Creating the Storyline Memo) enabled us to develop a substantive theory on the adoption of the SIG-UFRN software ecosystem by establishing relational statements between a set of 268 codes/categories, which collectively serve as concepts that analytically explain the phenomenon.
Regarding the results of Phase 1, we present only an excerpt of the Storyline Memo (see Figure 5), since the complete document comprises 1,168 lines. Therefore, as mentioned in Section 4, the complete Storyline Memo can be accessed at: https://zenodo.org/records/15104957.
Based on the criteria established by ) and described in Section 4, the researcher applied these criteria to analyze the Storyline Memo. The identified central category was “The adoption of the SIG-UFRN software ecosystem: an experience of software developers involved in this process”. This category accurately represents the data and provides an interpretation of the adoption of the SIG-UFRN software ecosystem. Consequently, the final product relates to the outcome of Phase 2 of the selective coding process (identifying the core category). Figure 7 shows the result of Phase 3 of selective coding (integrating the core category into the theoretical framework).
Figure 7
Figure 7 shows the consolidation of the theoretical framework for adopting the SIG-UFRN software ecosystem. The central category, “The adoption of the SIG-UFRN software ecosystem: an experience of software developers involved in this process”, is related to the other most important categories of the ecosystem adoption phenomenon. This allows us to understand what is happening.
The ellipse in Figure 7 represents the central category, which, as mentioned in Section 4, encapsulates the essence of the phenomenon under study. In this context, it illustrates the adoption of the SIG-UFRN SECO phenomenon. The rectangles depict the facts, events, actions, or interactions identified by the researcher, and the arrows illustrate the logical relationships between the rectangles and the central category. Colors are used to distinguish between the different components of the Paradigm Model: Causal Conditions, Intervening Conditions, Context, Actions/Interactions, and Consequences. This enables the reader to understand the phenomenon being studied.
The diagram in Figure 7 will be explained in the following subsections to help the reader understand: “Causal and Intervening Conditions”, “Context and Actions/Interactions”, and “Consequences”. These represent the components of the Paradigm Model technique (), which orders the data of the phenomenon under study systematically in a theoretical format. The results of the validation of the theoretical framework represented by Figure 7, which represent the results of Phase 4 (Validate the Theoretical Framework of SECO Adoption), will also be presented in a specific subsection.
5.1 Causal and intervening conditions
Based on the diagram in Figure 7, the central category shows that the software developers interviewed had experience adopting the SIG-UFRN SECO process. This process occurred in stages and comprised typical ERP (enterprise resource planning) implementation activities, as established in ).
The interviewees' experience began with the realization that the information systems used by their FEI had a limited set of features that hindered the full execution of their administrative and academic activities (Characteristics of the SystemsUsed by Institutions). This fact was an intervening condition (the “Intervening Conditions” component of the Paradigm Model) that triggered the events present in the “Causal Conditions” component. In other words, the characteristics of thesystems used by the Institutions were a prerequisite for the occurrence of causal conditions.
This caused institutional mobilization (the Institutional Mobilization action) with the aim of analyzing technological alternatives (the Analysis of Alternatives action) that would meet their need to automate business processes involving teaching, research, extension, and administration.
This institutional mobilization, carried out in each of the FEIs, was led by a group of key individuals from the business areas, including members of these institutions' IT units. During this process, technological alternatives that could meet their business management needs were analyzed using the Selection criteria category, which provided a technical basis for the decision to favor the SIG-UFRN platform.
The FEI's goal in adopting the SIG-UFRN SECO was to enable them to engage with their target audience by offering digital services that met their needs. The interviewees mentioned some of the benefits they anticipated from adopting the SIG-UFRN SECO (category: BenefitsSought by Institutions). The set of facts that result in the choice of the SIG-UFRN platform is conceptualized as the decision and selection stage (). In other words, the decision and selection stage encompasses a series of causal conditions (the “Causal Conditions” component of the Paradigm Model) that led to the choice of technological platform and, consequently, the adoption of the SIG-UFRN software ecosystem.
5.2 Context and actions/interactions
According to Figure 7, in response to events that occurred during the decision and selection stages, a set of actions and/or interactions (the “Action/Interaction” component of the Paradigm Model) were carried out with the aim of bringing the SIG-UFRN platform into full operation within the FEIs of the interviewees. In this interaction context (the “Context” component of the Paradigm Model), work teams (Workteams fact) were formed in each FEI to implement the SIG-UFRN technological platform. These actions relate to the implementation and use stages of the SIG-UFRN platform ().
These teams carried out various actions, including performing tests on system modules to verify whether they would meet the FEI's business needs (Module overview/study action), taking technical actions to configure these modules (Module deployment in production action), analyzing informational prerequisites (Prerequisite for module deployment action) for the module to be implemented, and providing user training (User training action) in operating the technological platform.
In some cases, the IT teams of the interviewees played a role in raising awareness and implementing good practices (the action IT as an enabler/promoter of best practices), holding presentations, and/or meetings on the benefits of the SECO and the good practices that would be implemented using the SIG-UFRN technological platform. This is one of the actions associated with mitigating the context of resistance to change by users of the FEIs (the “Context” component of the Paradigm Model). Resistance to change (Resistance to Change fact) was caused by some of the SIG-UFRN technological platform's business rules not meeting the needs of the FEIs' business areas. In this context, the FEIs acted through actions that allowed full use of the SIG-UFRN technological platform, in a process known as the differentiation of business rules (Differentiation of Business Rule event). These actions involved developing new features (Development of new features action) and customizing existing features (the Customization action). Both of these actions aimed to meet specific needs and help mitigate resistance to change by technological platform users (the Resistance to change fact), in addition to the aforementioned IT as an Enabler/Promoter of Best Practices action.
In this context of business rules differentiation (Differentiation of Business Rule event), the adaptation of FEIs to the business rules of the central organization (UFRN) (Adaptation to the business rules of UFRN action) was also used as an option; that is, FEIs adopted the business standards implemented in the SIG-UFRN technological platform.
The diversity of academic backgrounds (Education fact) and experience of other system implementation projects (Implementation projects fact) among the majority of interviewees are two contexts (“Context” component of the Paradigm Model) that enabled them to take on different roles within the SIG-UFRN technological platform implementation process, facilitating the adoption of the SIG-UFRN SECO. The inability of the data center infrastructures of the cooperating FEIs to host the SIG-UFRN technological platform was due to issues with their storage and processing capacities (Datacenter infrastructure fact) and the reduced number of IT employees in their FEIs (Reduced IT team size fact). These two contexts (“Context” component) also hindered the implementation and use stage of the SIG-UFRN technological platform.
5.3 Consequences
Figure 7 also shows that the central phenomenon or category is related to some consequences (the component “Consequences” of the Paradigm Model) and the result of actions and/or interactions (the component “Actions/Interactions” of the Paradigm Model) carried out in the process of adopting the SIG-UFRN SECO.
The following benefits of using the technological platform (the Benefits of the MISecosystem event, MIS - Management Information Systems): the fact that the SIG-UFRN ecosystem centralizes a team with the appropriate number of people and skills to support and evolve the technological platform in a shorter development time (the Team/development time event); the optimization of the FEIs' business processes (the Processoptimization event); and the cost-benefit of using the platform (the Cost–benefit event).
Additionally, the central category highlights the issues associated with using the SIG-UFRN technological platform as a consequence (Problems of the MIS ecosystem event). We only mentioned the fact that the cooperating FEIs are not consulted by the central organization (UFRN) when changing the functional and non-functional requirements of the technological platform (the Cooperating FEIs not participating in the elaboration ofrequirements event), without taking into account the impact that these changes may have on these institutions. Furthermore, the SIG-UFRN technological platform is not integrated with other internal information systems that meet the specific needs of the FEIs (Lack ofintegration with other systems used by cooperative members event), and even after the implementation of the platform, these systems continue to be used by the FEIs.
The central category indicates the costs of the usage of the SIG-UFRN technological platform. These costs include hiring interns to provide level 1 support to system users via the Internship contract event, which essentially involves answering operational queries. Other costs include training IT departments of FEI cooperatives in the technologies used to support the SIG-UFRN platform (the Training for IT departments event), and hiring cloud computing services or maintaining data center infrastructures (the Cloud computing services and Datacenter infrastructure events), respectively. These actions were taken in order to host the SIG-UFRN platform within the FEI cooperatives.
The central category also indicates significant changes to the IT units of the FEIs resulting from the implementation of the SIG-UFRN technological platform. We only mention the event in which the number of IT teams increased to provide adequate support for the implementation and maintenance of the platform (Changes to the IT unit event). The offer of greater robustness to these teams improved the quality of the IT services provided.
Finally, the central category also indicates partial support for management information in response to specific reporting requirements, which could be made available in modules of the SIG-UFRN technological platform (Partial support (management information) event). To meet these needs, the FEI used several technological alternatives, including the development of a report building tool (Report building tool event), the use of business intelligence (BI) tools (BI tools event), the creation of routines in certain programming languages (Routines created in certain languages event) and the implementation of reports in the SIG-UFRN technological platform itself (Implementing reporting requirements event).
As mentioned in Section 4, Phase 4 of selective coding involved validating the theoretical framework of the investigation using a diagram and the paradigm model technique (). The details and results of this phase are presented in Subsection 5.4.
5.4 Validation with participants
In this section, we present the details and results of Phase 4 (Validate the Theoretical Scheme of SECO Adoption) of Selective Coding, as shown in Figure 4. As mentioned in Section 4, in Phase 1 (Creating the Storyline Memo) of Selective Coding, the theoretical framework of the research was constructed through a document called the Storyline Memo (see Figure 5), which provides an analytical description of the phenomenon of adoption of the SIG-UFRN software ecosystem and helps conceptualize what is happening.
This theoretical framework is described in considerable detail because it explains the research phenomenon in detail. This theoretical framework was validated on the basis of the diagram in Figure 7, which represents the main concepts identified in the adoption of the SIG-UFRN software ecosystem. The central concept (“Central” category) is present alongside the main categories of the 31 code networks constructed when the open and axial coding techniques were applied to the interview data. These interviews were held in Phase 2 of the research methodology (see Figure 3) and were conducted with the participants described in Table 1.
Therefore, based on the presentation of the central concept and the main secondary concepts, participants were asked if they could identify with the story depicted in the diagram (Figure 7) and if they could therefore perceive it as a reasonable explanation of what is happening. In other words, they were asked if the explanation of the SECO adoption process at the SIG-UFRN reflects their experiences acquired in their FEIs. Participants in Phase 4 (Validate the Theoretical Framework of SECO Adoption) are the same as those who participated in Phase 2 interviews, as listed in Table 1.
To collect validation data, the focus group technique () was used, which involved gathering participants on a scheduled day and time to discuss the analysis elements presented, with the objective of eliciting opinions, responses and identifying conflicts in the diagram. This differs from the interview technique used in Phase 2 of the methodological flow (Figure 2) in that the interviews were conducted individually to gather the experiences of these professionals in implementing the SIG-UFRN technological platform in their respective FEIs. As the name suggests, the focus group technique was applied to a group of participants gathered on a pre-agreed day and time. The objective was to analyze the theoretical framework described in Figure 7.
To guide participants through the validation process, a discussion group was created using a messaging tool to disseminate guidelines for this phase.
The validation meeting took place online via the Google Meet tool. The audio of the meeting was recorded with the consent of the participants and can be accessed at: the theoretical framework. The https://zenodo.org/records/15122050. On the day of the meeting, only two interviewees were absent: I5 and I9 (see Table 1). Therefore, 80% of the participants participated in this validation process.
In the month leading up to the validation meeting, some relevant information about the research was disclosed to the participants. They were introduced to the concept of software ecosystems and became familiar with the characterization of the SIG-UFRN technological platform as part of the wider SIG-UFRN SECO organization. Consequently, the participants recognized the importance of their contributions at this stage of the study and the relevance of the investigation.
The validation meeting, conducted by a researcher, lasted approximately 1 hour and 38 minutes. To facilitate the meeting, the researcher required audio recording equipment, a video conferencing platform, a computer, and a text editing application to compile the data obtained from the participants after the theoretical framework was presented to them.
Following the presentation of the diagram (Figure 7), the participants suggested a minor amendment to the central category relating to the term “software developers”, proposing replacement with “team from the IT sector/unit”.
This change was requested because the participants' experiences of adopting SIG-UFRN SECO involved a range of activities beyond just building code, encompassing all the methodological steps of the software development cycle: communication (listing stakeholders and requirements), planning (defining scope and costs), analysis and design (functional modeling and interfaces), construction (code generation and testing), and deployment (support and manuals).
The software developers' experiences involved working in teams comprising several information technology professionals, including project managers, systems analysts, requirements engineers, support technicians, and programmers. These professionals were members of the FEI IT units and were involved in the adoption process of SIG-UFRN SECO.
It is important to note that the logical relationships presented in the Paradigm Model (Figure 7) and the analytical description of the Storyline Memo have not been altered and remain valid. In summary, changing the central category to “team from the IT sector/unit” provides a more precise identification of the group that experienced the phenomenon without altering the established facts, events, or connections between causal conditions, actions, and consequences, while maintaining all the analytical elements expressed in the updated Paradigm Model (Figure 8) and Storyline Memo.
Figure 8
Therefore, the new version of the central category represents “The adoption of the SIG-UFRN software ecosystem: an experience of the team from the IT sector/unit involved in this process” (see Figure 8).
The researcher then asked the participants two questions:
“Do you feel included in the general context that this diagram represents?”
“If yes or no, would you like to discuss any of the events presented in detail?”
Below are some excerpts from the participants' responses to these questions:
“Congratulations on your work, you have highlighted the main problems and contexts very well, I completely agree with what you pointed out, we have been through this.”- Interviewee I10.
“Congratulations on your work, they (SIG Systems) only see the rules of UFRN.” (Differentiation of business rule event) - Interviewee I2.
“SIGAA is not multicampus (centralized academic calendar); there is already a team working on this, including me, and we are adjusting the SIG so that it becomes a multicampus system.” (Customization action) - Interviewee I1.
“Your description of the problems was very good, especially the ones that we see a lot there, I remember some things that I mentioned that were present there, as well as others that my colleagues mentioned that I could also relate to.”- Interviewee I8.
“I suggest dividing the document into two parts: the first part should cover the selection methodology and the second part should cover the implementation and maintenance methodology, as well as a checklist for a proof of concept (POC) to evaluate tools.”- Interviewee I2.
In the above quote, Interviewee I2 suggested expanding this research by developing two manuals. The first would be related to the decision and selection stages in ERP systems () and would contain the necessary guidelines to determine the feasibility of adopting the SIG-UFRN platform. This would consider other technological alternatives to the ecosystem and would include preparing a proof of concept (POC) to evaluate these alternatives. The second manual will contain a set of recommendations to sustain the SIG-UFRN platform after its implementation in an organization. This documentation relates to the implementation and use stage in ERP systems ().
“My silence is precisely because the situations we have experienced here at FEI have already been covered by the model (diagram presented) and by what my colleagues have said; the experiences are very similar; everything you have said already encompasses what we have experienced here, which is why I have not said anything.”- Interviewee I6.
Finally, in light of the systematization and results obtained in Phase 4 (“Validate the Theoretical Scheme of SECO Adoption”), we can confirm that the theoretical saturation of the SIG-UFRN SECO adoption phenomenon was formally evaluated and confirmed during this phase. This evaluation was carried out through a focus group with participants, who, after reviewing the theoretical framework expressed in Figure 7, approved the logical structure of the phenomenon. They suggested only one refinement for the central category: “team from the IT sector/unit”. This modification aimed to more accurately reflect the multidisciplinary adoption experience, encompassing infrastructure and support professionals, as well as developers.
The extent of saturation is proven by the participants' responses to the researcher's questions. Although I10 and I8 agreed that the model highlighted the problems and contexts experienced, I6 explained that he had remained silent because “everything you said already encompasses what we experience here”, indicating that the model was sufficiently accurate and that no new concept was necessary.
The consensus reached, along with the absence of new suggestions for categories, confirms that the theoretical framework satisfactorily responds to real facts and events, thus allowing for the formal validation of the discovered theory.
Following the approval of the theoretical framework, we recognized the need to represent the SIG-UFRN SECO phenomenon using existing technology adoption models, such as the Technology-Organization-Environment (TOE) and Antecedents-Behavior-Consequences (ABC) models. The TOE model explains the adoption of technological innovations by organizations (), while the ABC model provides a framework for understanding how specific inputs drive behaviors that produce measurable results ().
We will therefore integrate these two models to synergistically combine these structures and comprehensively explain how the adoption of SIG-UFRN SECO occurred, taking into account the contextual aspects of technology, organization, and environment, as well as the temporal components that link antecedents to behaviors and consequences ().
With the integrated TOE&ABC model (see Figure 9), we will be able to explain how Technology, Organization, and Environment factors (Antecedents) drove the adoption actions of SIG-UFRN SECO (Behavior), generating results for FEIs that chose to cooperate in this SECO (Consequences).
Figure 9
Finally, according to Figure 9, the representation of the adoption phenomenon of the SIG-UFRN SECO is described as follows:
The realization that the information systems used by the FEIs had a limited set of functionalities that did not meet their business needs (Technology) led to institutional mobilization (Organization) with the aim of analyzing technological alternatives that would meet these organizations' business needs,
The FEIs, embedded in a demanding regulatory, governmental, social, and academic environment, sought benefits from adopting a technology that would meet their needs (Environment). Desired benefits in this context include process optimization, transparency, and collaborative development,
The academic background and project experience of software developers in the implementation of software technologies (Technology) was an important factor in the adoption process of the SIG-UFRN SECO,
We therefore conclude that events related to Characteristics of the Systemsused by Institutions, Institutional Mobilization, Benefits sought by Institutions, and Education were the main antecedents or prerequisites that stimulated the adoption behaviors of the SIG-UFRN SECO,
The aforementioned antecedents boosted behaviors such as forming work teams within each FEI to implement the SIG-UFRN SECO technological platform. These work teams carried out various actions, including performing tests on system modules to verify whether they would meet business needs, carrying out technical configuration actions on these modules, analyzing informational prerequisites for the implementation of the modules, and training users to operate the technological platform,
The IT teams of the interviewees played a key role in raising awareness and implementing best practices. In some cases, they carried out presentations and/or meetings on the benefits of SECO and the best practices that would be incorporated when using the SIG-UFRN technological platform. This behavior also helped to mitigate user resistance to changes to the operating modules of the technological platform,
Therefore, the main behaviors involved in the adoption of SIG-UFRN SECO were IT as an Enabler/Promoter of Best Practices, Work Teams, andResistance to Change,
The adoption behaviors mentioned generated results or consequences for the FEIs. The benefits of using the technological platform (Benefits of the MISEcosystem). The centralizer of SIG-UFRN SECO has a team with the adequate number and competence to support and evolve the technological platform in a shorter development time. This optimizes the business processes of the FEIs and improves the cost-benefit of using the technological platform,
We also highlight the issues associated with using the SIG-UFRN technological platform (Problems of the MIS Ecosystem). The central organization (UFRN) does not consult the cooperating FEIs when the functional and nonfunctional requirements of the technological platform change, without considering the potential impact on these institutions. Another problem is the lack of integration of the SIG-UFRN technological platform with other internal information systems that meet the specific needs of the cooperating FEIs. Even after the implementation of the SIG-UFRN technological platform, these systems continued to be used,
Finally, we would like to mention the following consequences: the costs of using the SIG-UFRN technological platform (Usage costs); significant changes that occurred in the IT units of the FEIs (Changes in the IT Unit); and the partial provision of management information in response to specific reporting needs, which could be made available in modules of the SIG-UFRN technological platform (Partial Support (Management Information)).
6 Discussion
Based on the results obtained in Section 5, it was possible to identify the factors that must be considered for the successful adoption of the SIG-UFRN software ecosystem by all interested parties. This was achieved through the creation of the Storyline Memo, which revealed the outcomes when the FEIs of the interviewees suggested collaborating within this ecosystem.
The theory expressed in the Storyline Memo, as well as the identification and integration of the central category into this theory using the Paradigm Model technique (), summarizes the experiences of adopting the SIG-UFRN software ecosystem. This can be validated by testing the theoretical framework with members of the IT teams that participated in the adoption process.
Table 4 shows a summary of the interrelated adoption factors of the SIG-UFRN SECO that form the research's theory or the theoretical framework. The experiences of FEIs IT teams, as evidenced by the factors in Table 4 and their strong relationships with the central category—which is presented in full in the Storyline Memo (this can be accessed via the link: https://zenodo.org/records/15104957)—allow us to obtain a set of theoretical elements that, if observed, can lead to the successful adoption of the SIG-UFRN software ecosystem. These theoretical elements were successfully categorized into the dimensions established by ).
Table 4
| Factor | Dimension () |
|---|---|
| Characteristics of the systems used by institutions | Technical and business |
| Analysis of alternatives | Technical and business |
| Selection criteria | Technical and business |
| Benefits sought by institutions | Business |
| Module overview/study | Business |
| Module deployment in production | Technical |
| Prerequisite for module deployment | Business |
| Team/development time | Social |
| Institutional mobilization | Technical, social and business |
| Development of new features | Technical and business |
| Customization | Technical |
| Development of new features | Technical |
| Work teams | Technical and business |
| IT as an enabler/promoter of best practices | Social |
| Resistance to change | Business |
| Differentiation of business rule | Business |
| Education | Technical and social |
| Implementation projects | Technical and social |
| Datacenter infrastructure | Technical |
| Reduced IT team size | Social |
| Benefits of the MIS ecosystem | Technical and business |
| Process optimization | Business |
| Cost–benefit | Business |
| Problems of the MIS ecosystem | Technical, social and business |
| Cooperating FEI not participating in the elaboration of requirements | Social |
| Lack of integration with other systems used by cooperative members Usage costs | Business |
| Internship contracts | Business |
| Training for the IT department | Technical and social |
| Cloud computing services | Business |
| Changes in the IT unit | Social and business |
| Partial support (management information | Business |
| Report building tool | Technical and business |
| Routines created in certain languages | Technical and business |
| Implementing reporting requirements | Technical and business |
Interrelated factors for the formation of the theoretical scheme.
For example, the Differentiation of Business Rule factor should be given particular attention by the IT teams of the FEIs, given that the business rules implemented in the SIG-UFRN technological platform are designed to meet the needs of the central organization (UFRN). In order for this technological platform to be successfully adopted by other FEIs, development teams that have the necessary numbers and technical qualifications (Team/development time) to support customizations (Customization) and the development of new functionalities are required (Development of New Features), thereby ensuring that the platform meets their specific needs.
This finding is highly relevant as it aligns with the study by ). They state that recruiting software developers demonstrates a SECO's ability to engage the community in collaborating on its projects. Without active management of this recruitment, however, the community tends to abandon the SECO, consequently causing its collapse.
In addition, the interested manager must conduct a technical feasibility study prior to implementation to verify how far their business rules differ from those of the technological platform. If the differentiation is high and the institution lacks the capacity to respond, the project may be interrupted or generate high levels of resistance from users (Resistance tochange).
The Selection criteria factor, which was used to evaluate alternatives to the SIG-UFRN platform, being decisive for its adoption, is associated with the health of the ecosystems (), which refers to the SECO's performance in the pillars of productivity, robustness, and niche creation. In this context, we are following the trend of analyzing SECOs based on their health pillars, as carried out in the research by ).
One example is the Adoption rate factor, which is associated with the robustness pillar and deals with the number of organizations that come together in a SECO. ) exemplify a similar evaluation factor called Interest over time, which measures public interest in a SECO. This factor was measured using Google Trends.
Therefore, the evaluation criteria used for the alternatives to the SIG-UFRN SECO are highly relevant, as they provide an objective method of SECO evaluation. This allows the decision to adopt to be based not only on isolated technical functionalities, but also on long-term sustainability and ecosystem health.
The IT as an enabler/promoter of best practices factor bears a strong resemblance to the developer relations (DevRel) metrics evaluated in a question-and-answer repository inherent to a SECO in the study by ). Some metrics are: View Count, AnswerCount, Comment Count, and Favorite Count. These metrics are similar in that efficient management of these factors depends on actions that promote the adoption of SECOs by mentioning the benefits and/or advantages of cooperating in these environments.
It is important to consider the metrics of magnitude and extent used in the study by ) to analyze the impact of API evolution in a SECO. Some of these metrics are: Frequency of reactions (counting the number of distinct systems, methods, and developers—the authors of commits that effectively applied the change prescribed by the evolution of an API); and Systems affected (identifying systems that contained calls to an old API that underwent an evolution process).
These metrics strongly resemble the Maturity level and Adoption rate factors in our research as both studies evaluate the number of organizations/software developers using and validating the functionalities of a SECO's technological platform. This finding is of great importance, as it reveals the ability to objectively measure technical risk and community vitality before committing resources to a technological platform.
Notably, the textual expression of the central category also explains exceptional cases in the research phenomenon when the SIG-UFRN software ecosystem was adopted compulsorily without analyzing the platform's technological alternatives (Analysis ofAlternatives fact). This exceptionality is represented by the compulsory adoption fact, which can be seen in the Storyline Memo.
A complete analysis of all the factors involved in adopting the SIG-UFRN SECO can be found in the Storyline Memo at: https://zenodo.org/records/15104957.
Constructing the Storyline Memo, which represents the discovered theory and the central category expressing “what is happening” in a few words, and integrating it with the main factors present in the Paradigm Model technique (Figure 8) allows us to detail a theoretical framework that answers the research question proposed by this study: “Is there a theoretical framework that can explain the adoption of the SIG-UFRN software ecosystem?”
We can also mention the benefits of the developed theoretical framework and how it can be applied by the FEIs when conducting the SIG-UFRN SECO adoption process:
In the decision and selection stage (), the FEIs can carry out an analysis to assess whether the SIG-UFRN platform is superior to other technological alternatives in terms of integration and the support capacity of the development team, as well as other selection criteria described in the theoretical framework. Additionally, the theory describes that the adoption of a SECO should not be an IT-only decision, but should involve key personnel from business areas such as teaching, research, and extension, to validate whether the functionalities meet academic and administrative requirements,
In the implementation stage (), the theoretical framework describes the importance of structuring dedicated teams to study the modules and configure the environments (development, testing, and production). The FEIs should also identify areas where their business rules differ from those of the central organization (UFRN). If differentiation is high, customizations or development of new functionalities should be planned, ensuring the local technical team has the necessary size and qualifications to maintain this code in future. Before the technological platform is fully operational, the FEIs must invest in improving the data center infrastructure to ensure sufficient processing and storage capacity for the systems,
In the use stage (), the discovered theory states that it is essential to institutionalize user training and IT team capacity building in base technologies (Java, DBMS, etc.) to avoid unexpected behavior and ensure system stability. IT teams must take action to prevent the technological platform from becoming unupdateable. This can be achieved by minimizing unnecessary customizations and promoting good practices among IT members, enabling the FEIs to receive legal corrections and updates to the UFRN reference version. The theoretical framework then guides the FEIs in identifying shortcomings in the integration of other systems (including government systems) and in seeking alternative solutions, such as creating reporting tools or using orbital systems, to address technological and performance gaps.
This research had a positive impact on its participants because: they identified that had experienced the same problems when adopting the SIG-UFRN software ecosystem in their respective FEIs, where some FEIs developed solutions to these problems that can be shared among them; and our explanation of the adoption of the SIG-UFRN SECO is not limited to listing factors that define success or failure, but builds a substantive theory that provides an analytical explanation of this phenomenon.
This study addresses a gap in the literature by establishing a methodological standard for applying the selective coding technique of Grounded Theory (GT), while also explaining the phenomenon through the integration of the Technology-Organization-Environment (TOE) and Antecedents-Behavior-Consequences (ABC) models. This enables technical readers to visualize how context (TOE) drives adoption actions (Behavior), generating measurable results (Consequences).
Finally, the developed theoretical framework functions as a knowledge management product, enabling the sharing of experiences from different FEIs. In other words, we identified a set of structured best practices to assist teams in managing risks and maximizing successes.
7 Threats to validity
Based on the results described in Sections 5.4 and 6, we can identify some threats to the validity of this study:
7.1 Quality of data consolidation
In Phase 2 of the methodological process (Figure 3), the researcher obtained data on the developers' experience in adopting the SIG-UFRN SECO through interviews. The data were then used to construct coding networks, forming the basis for a theory on the adoption of this SECO. However, the researcher's subjective interpretation of the data is a potential threat, as experiences may have been described in light of ideological convictions, with important facts being highlighted at the expense of relevant events and potentially omitting what really matters. Nevertheless, this threat is mitigated by the researcher's extensive experience in managing SIG-UFRN SECO adoption projects at FEI, which ensures the quality of the consolidated data.
7.2 The theory of the phenomenon is based on the subjective nature of the experiences described by the interviewees
The subjective nature of the experiences described by the interviewees is based on each person's judgment and may involve their beliefs and convictions. This can lead to facts necessary for building the theory being mischaracterized or omitted when grounded theory coding techniques are used. In this scenario, Selective Coding is advantageous as it incorporates concepts identified in previous stages. Although this subjectivity can reduce the quality of data consolidation, obtaining perceptions from people who experienced the process of adopting the SIG-UFRN ecosystem in their respective FEI – working directly on the technical, social, and business issues of the ecosystem as conceptualized in ) – enables us to ratify the knowledge produced in a consistent manner. Furthermore, these interviewees positively validated the theory discovered.
7.3 Validation of the theory through a diagram
The Storyline Memo contains the complete theoretical framework explaining the adoption process of the SIG-UFRN software ecosystem. As it is a lengthy document, we opted to validate the theory using a diagram that represents the central category and its relationship to the main categories of the SECO adoption phenomenon (see Figure 7). The diagram is constructed using the Paradigm Model technique, which systematizes a summary of the analytical viewpoint of a phenomenon by bringing together elements that allow us to identify the causes of this phenomenon in a specific context. This enables us to understand the actions taken in response to these conditional events and their consequences, providing a reasonable and concise explanation of what is happening, even without mentioning all the events, which were mentioned less frequently by the interviewees. This scenario enables us to validate this theory through the diagram.
7.4 Impossibility of generalizing the results
This research involved a small number of federal educational institutions from different geographic regions of Brazil. Although this does not allow us to generalize that the discovered theory fully meets the experiences of other FEIs that have adopted the SIG-UFRN software ecosystem, it is important to note that we had the opportunity to identify and understand the events evidenced by FEIs from different regions of Brazil. This enables us to conclude that the theoretical framework identified in the Storyline Memo and Figure 7 may be a reasonable explanation of what is happening in other FEIs in terms of the adoption of the SIG-UFRN SECO.
7.5 Technical bias of the theoretical framework
It is acknowledged that the technical bias of the discovered theory restricts the explanation of the theoretical framework since the perspectives of stakeholders in the business area, such as the academic, administrative, and human resources teams, were not directly incorporated. Although the IT technical team at FEI observed facts and events relating to technical, social, and business factors from the perspective of business managers during the adoption process of SIG-UFRN SECO—providing a “reasonable explanation” of the phenomenon from the perspective of those who experienced the process—this omission significantly restricted the analytical depth of the social and business dimensions (). The expression “reasonable explanation” refers to the fact that the developed theoretical framework limited its explanation of the social dimension () to the IT sector's perception of user resistance to using the SIG-UFRN platform, and to the IT sector's role as a promoter of good practices. This was considered in terms of the implementation and use stages of the SIG-UFRN platform. However, the subjective motivations, feelings, and cultural barriers of end users in the teaching, research, and extension activities of FEI were not addressed in depth. Regarding the business dimension, the explanation was restricted to the operational aspects of the implementation and use stages of the platform, mentioning the formation of work teams, the benefits of use, good practices, and the costs of using the platform. This may have underestimated factors of strategic value and the return on benefits to citizens and institutional efficiency from the perspective of managers in the core areas. Consequently, the resulting theoretical framework should be viewed as an adoption theory centered on the IT sector. While this theory is consistent with technical reality and incorporates elements of the social and business dimensions, it is one-sided and focuses on the feasibility and execution of a software project.
7.6 Absence of participants in the validation phase
Two participants were absent from the validation phase. These were interviewees I5 and I9, who represented the south-eastern region of Brazil. This may have restricted the theory that was discovered. However, the representativeness of this region was maintained by participant I8, who is also from the south-east and actively participated in the validation process, praising the description of the presented problems. This suggests that the regional particularities were probably not overlooked due to the absence of the other two participants. Additionally, during the focus group, the participants' accounts demonstrated a strong convergence of experiences, regardless of geographical location. Participant I6's testimony is crucial here, as they state that the experiences are very similar and that the model already encompasses everything they have experienced in their institution. This consensus suggests that theoretical saturation had already been reached and that including the two absent participants would probably only reinforce the established concepts without adding any new significant categories and/or codes.
7.7 Circularity of the validation phase
This research tested the theoretical framework of the SECO adoption phenomenon using the same groups of participants who were interviewed in the interview phase. However, this introduces a significant methodological circularity bias, as we are only verifying whether participants corroborate a theory originating from their own contributions. True theoretical saturation, which would be achieved through validation, requires testing the theoretical framework with a new set of stakeholders or using quantitative research to generalize the findings to a broader population of FEIs. Nevertheless, testing the theoretical framework with participants from FEIs in different regions of Brazil provides a reasonable explanation of the adoption of the SIG-UFRN SECO in other FEIs.
7.8 Theoretical saturation in breadth
This research aimed to explain the adoption of SIG-UFRN SECO in a broad way, taking into account a significant number of influencing factors. However, not delving into the description of these factors may limit the understanding of those interested in knowing more about the phenomenon. However, we provide an extensive and complete description of SECO adoption, enabling readers to gain a comprehensive understanding of the process, rather than detailing some factors to the detriment of others, which could lead to a partial view of the phenomenon.
8 Conclusion
This research aimed to contribute to the development of a theoretical framework that managers of public bodies could use to analyze the viability of joining the SIG-UFRN software ecosystem and benefit from the features of the technological platform, which are limited to teaching, research, extension, and administration.
Through selective coding, we were able to integrate the technical, social, and business factors involved in the process of adopting the SIG-UFRN SECO, as described in ).
This theoretical framework explains the process of adopting the SIG-UFRN software ecosystem, highlighting the typical stages of the implementation of the ERP system (): decision and selection, implementation, and use. It can therefore be used to help public managers identify the institutional demands that must be met for an FEI interested in adopting the SIG-UFRN software ecosystem to be successful in this process and reap the benefits of using this software technology.
FEIs that have adopted the SIG-UFRN SECO and are working on the implementation phase of the SIG-UFRN technological platform can use the theoretical framework as a best practice document. They can consult the framework for guidance on how to proceed and overcome any issues in this phase, using solutions based on the experience of the FEIs interviewed in this research.
For FEIs intending to analyze the possibility of joining the SECO of SIG-UFRN, the theoretical framework can provide guidance in the decision and selection process (), helping them to choose the most suitable technological platform available on the market with SIG-UFRN as a reference point. The good practices presented in the theoretical framework can also help other FEIs in the utilization stage () by providing insights from the experiences of the IT teams and users of SIG-UFRN. This can help avoid errors and maximize successes, ensuring that the cooperating institution completes this stage successfully.
Finally, the main contribution of this research is the availability of a theoretical framework to adopt SIG-UFRN SECO. This framework can be used as a knowledge management work product, enabling FEI experiences to be shared in the decision, selection, implementation, and utilization stages (). Creates a knowledge repository that enables FEIs wishing to adopt SIG-UFRN SECO to learn from previous mistakes and successes. This acts as a turning point between success and failure in the adoption process.
As a contribution to this research, we also present the development of a systematized and rigorous methodology that serves as a procedural guide for researchers seeking to apply the selective coding protocol in complex qualitative studies, not restricted to software ecosystems. This constructed methodology has many advantages, including an approach that allows for an efficient transition from raw data description to high-level conceptualization. This makes it possible to integrate and refine large volumes of fragmented data (268 codes were identified in this research) into a cohesive narrative using the Storyline Memo tool. This ensures that the resulting theory is more than just a list of themes; it is a comprehensive and well-founded explanation of the phenomenon.
The methodology uses the Paradigm Model technique, which offers the benefit of systematically organizing the structure and process of a phenomenon. This enables readers at different levels to clearly visualize the interrelationships between conditions, actions, and consequences, transforming isolated factors into an explanatory tool for understanding what drives the occurrence of the phenomenon under study.
The developed methodology also establishes clear criteria for identifying the central category and defines a validation phase of the phenomenon, ensuring theoretical saturation is achieved in a verifiable way.
This research also benefits the industry by providing a theoretical framework that managers of companies that commercially exploit the SIG-UFRN technological platform (Licensed Companies—see Figure 1) can use. These companies are contracted by public or private organizations, and managers can use this document on best practices to coordinate efforts with these organizations and assist them in adopting the SIG-UFRN SECO. This helps to maintain the health of SECO by bringing new organizations on board to support SIG-UFRN SECO. Furthermore, this theoretical framework can be used by all stakeholders in the SIG-UFRN SECO who require guidance on how to fulfill a given role.
Specifically in the context of academia, this research contributes to the development of a methodology to apply Grounded Theory (GT) coding techniques, particularly selective coding, as outlined in ). It also provides a theoretical framework on which subsequent research can build on to offer a managerial perspective on the adoption process of the SIG-UFRN SECO. This theoretical framework is based on the experiences of the IT teams involved in the process and provides a technical perspective on the resulting theory.
Regarding the limitations of this research, we would like to highlight the following:
Participation of a small number of FEIs. Only a small number of FEIs from different Brazilian regions participated in the interview and validation phases. As mentioned in Section 7, this was also considered to pose a threat to validity of the study, as it may make it impossible to generalize the results,
Absence of participants in the validation phase. We also highlight the limitation of the absence of two interviewees in the validation phase (Validate the Theoretical Scheme of SECO Adoption), who would have accounted for 80% of contributions,
Absence of validation with external participants. The theoretical framework discovered was not tested with an external group of participants, which means we cannot generalize the theoretical saturation obtained in the research. As mentioned in Section 7, this was also considered a threat to the validity of the research,
Absence of methodological standard. We could not find a methodological standard for the application of the selective coding technique of GT in the literature, so it was necessary to develop this standard based on ), as well as the particularities inherent to SECOs and ERP systems.
Finally, we suggest the following areas for future work:
The theoretical framework will be quantitatively validated through a survey study with collaborators from IT units of other FEIs that were not part of the initial discovery sample. This will function as an independent validation resource. The central objective of this quantitative analysis is to generalize the results beyond the nine participating institutions, thereby consolidating the discovered theory as a robust, predictive, decision-support tool capable of guiding Brazilian public IT units and their managers in mitigating risks and optimizing the use of scarce resources when adopting the SIG-UFRN SECO,
Collecting data from the FEI business area that adopted the SIG-UFRN software ecosystem to obtain the perceptions and experiences of these actors, which, when combined with GT coding techniques, will expand the discovered theoretical scheme to include a vision focused on process optimization, operational efficiency, service provision, and decision-making, and
Creating a manual/guide document based on the theoretical framework developed to guide public body managers through the necessary steps to carry out a technical feasibility study on adopting the SIG-UFRN software ecosystem for the decision and selection stage in ERP systems.
Statements
Data availability statement
The original contributions presented in the study are included in the article/supplementary material, further inquiries can be directed to the corresponding author.
Ethics statement
The requirement of ethical approval was waived by National Committee for Research Ethics (CONEP) in Brazil for the studies involving humans because this study is based on public opinion research with unidentified participants and therefore did not require ethical approval. The studies were conducted in accordance with the local legislation and institutional requirements. The participants provided their written informed consent to participate in this study.
Author contributions
AV: Validation, Conceptualization, Writing – original draft, Methodology, Formal analysis, Investigation. SO: Supervision, Writing – review & editing, Conceptualization, Validation.
Funding
The author(s) declared that financial support was received for this work and/or its publication. The authors received funding from the Vice-Rectorate for Research and Graduate Studies of the Federal University of Pará, Brazil (PROPESP/UFPA).
Acknowledgments
The authors would like to thank the interview participants and those who validated the theoretical framework for sharing their perceptions and experiences of adopting the SIG-UFRN software ecosystem. The authors would also like to thank the Vice-Rectorate for Research and Graduate Studies at the Federal University of Pará (PROPESP/UFPA) in Brazil for providing financial support for the publication of this work.
Conflict of interest
The author(s) declared that this work was conducted in the absence of any commercial or financial relationships that could be construed as a potential conflict of interest.
Generative AI statement
The author(s) declared that Generative AI was not used in the creation of this manuscript.
Any alternative text (alt text) provided alongside figures in this article has been generated by Frontiers with the support of artificial intelligence and reasonable efforts have been made to ensure accuracy, including review by the authors wherever possible. If you identify any issues, please contact us.
Publisher’s note
All claims expressed in this article are solely those of the authors and do not necessarily represent those of their affiliated organizations, or those of the publisher, the editors and the reviewers. Any product that may be evaluated in this article, or claim that may be made by its manufacturer, is not guaranteed or endorsed by the publisher.
References
1
ArantesP.SoupinskiF.FontoA. (2023). “Social networks during software ecosystems' death,” in 2023 IEEE/ACM 11th International Workshop on Software Engineering for Systems-of-Systems and Software Ecosystems (SESoS) (Melbourne, VIC: IEEE), 09–12.
2
BarbosaS.SilvaB. (2010). Interao humano-computador. Amsterdam: Elsevier.
3
CampbellP. R. J.AhmedF. (2010). “A three-dimensional view of software ecosystems,” in Proceedings of the Fourth European Conference on Software Architecture: Companion Volume (Copenhagen: ACM), 81–84.
4
CassianiS. H. d. B.AlmeidaA. M. d. (1999). Teoria fundamentada nos dados: a coleta e anlise de dados qualitativos. Cogitare Enfermagem4, 13–21.
5
Da SilvaR. T.GustavoF. L.AudacioE. D.GengivirE. C. (2017). “Identifying actors to support software ecosystem health,” in 2017 IEEE/ACM Joint 5th International Workshop on Software Engineering for Systems-of-Systems and 11th Workshop on Distributed Software Development, Software Ecosystems and Systems-of-Systems (JSOS) (Buenos Aires: IEEE), 76–77.
6
DijkersJ.SincicR.WasankhasitN.JansenS. (2018). “Exploring the effect of software ecosystem health on the financial performance of the open source companies,” in Proceedings of the 1st International Workshop on Software Health (Gothenburg: ACM), 48–55.
7
HenttonenK. M.PulkkinenM.TyrvainenP. (2024). Health and orchestration of public-sector open-source software ecosystems roles, rules and tools. Scand. J. Inform. Syst. 36, 69–120. Available online at: https://aisel.aisnet.org/sjis/vol36/iss2/3 (Accessed June 22, 2026).
8
HoraA.RobbesR.ValenteM. T.AnquetilN. (2018). How do developers react to API evolution? A large-scale empirical study. Softw. Qual. J. 26, 161–191. doi: 10.1007/s11219-016-9344-4
9
JansenS.CusumanoM. A. (2013). Defining Software Ecosystems: A Survey of Software Platforms and Business Network Governance. Software Ecosystems. Cheltenham: Edward Elgar Publishing, 13–28.
10
KitchenhamB.ChartersS. (2007). “Guidelines for performing systematic literature reviews in software engineering,” in Technical Report EBSE 2007-001 (Keele: Keele University and Durham University Joint Report).
11
KolehmainenT.GhezziR.HyrynsalmiS.MikkonenT.PekkolaS.SetM. (2024). How pandemics changed a public software ecosystem: Omaolo case. IEEE Software42, 57–67. doi: 10.1109/MS.2024.3521992
12
LaudonK.LaudonJ. (2020). Management Information Systems: Managing the Digital Firm. London: Pearson.
13
LewinK. (1947). “Group decision and social change,” in Readings in Social Psychology by Theodore M. Neweomb and Eugene L. Hartley, Co-Chairmen of Editorial Committee. New York: Henry Holt and Co.
14
LucasH. C. (1985). The Analysis, Design, and Implementation of Information Systems. Columbus, OH: McGraw-Hill, Inc.
15
MartinJ.McclureC. (1983). Buying software off the rack. packages can be the solution to the software shortage. Harv. Busin. Rev. 61, 32–6, 40–6, 52–4.
16
MassanoriD.CafeoB.WieseI. S.FontA. (2020). “Death of a software ecosystem: a developer relations (devrel) perspective,” in Proceedings of the XXXIV Brazilian Symposium on Software Engineering (Natal: ACM), 399–404.
17
OliveiraM. A.RamosA. S. M. (2002). Fatores de sucesso na implementao de sistemas integrados de gesto empresarial (ERP): estudo de caso em uma mdia empresa,” in XXII Encontro Nacional de Engenharia de Produo. Anais. Curitiba (Porto Alegre: ABEPRO).
18
SaarniK.RaatikainenM.HyrynsalmiS. (2025). “Failures in software ecosystems: a systematic literature review,” in 2025 IEEE International Conference on Engineering, Technology, and Innovation (ICE/ITMC) (Valencia: IEEE).
19
SantosR. P. d. (2016). Managing and monitoring software ecosystem to support demand and solution analysis (Doctoral Thesis). Universidade Federal do Rio de Janeiro, Rio de Janeiro, Brazil.
20
SoaresR. S. d,. A LimaS. B. S.KesslerM.EberhardtT. D.Saul-RoratoA. M. R.et al. (2015). “Codificando e analisando dados na perspectiva da teoria fundamentada nos dados: relato de expericia,” in Revista de Enfermagem UFPE Online (Recife: Biblioteca Central da UFPE), 8916–8922.
21
SouzaC. A. (2000). “Sistemas integrados de gest empresarial: estudos de casos de implementao de sistemas ERP,” in Tese de Doutorado (Rio de Janeiro: Universidade de S Paulo).
22
SteglichC.MarczakS.GuerraL. P.MosmannL. H.PerinM.FilhoF. F. (2019). “Revisiting the mobile software ecosystems literature,” in 2019 IEEE/ACM 7th International Workshop on Software Engineering for Systems-of-Systems (SESoS) and 13th Workshop on Distributed Software Development, Software Ecosystems and Systems-of-Systems (WDES) (Montreal, QC: IEEE), 50–57.
23
SteglichC.MarczakS.SantosR.MosmannL. H.GuerraL. P.De SouzaC.et al. (2020). “How do business factors affect developers in mobile software ecosystems?,” in XVI Simpsio Brasileiro De Sistemas De Informao (SBSI) (Porto Alegre: SBC).
24
StraussA. L.CorbinJ. (2008). Pesquisa qualitativa: tcnicas e procedimentos para o desenvolvimento de teoria fundamentada. Porto Alegre: SBC.
25
TCU (2013). Secretaria-geral de controle externo. convnios e outros repasses: A tomada de contas especial - tce. 4a. [s. l]. Brasília: Tribunal de Contas da União.
26
TornatzkyL. G.FleischerM. (1990). Processes of Technological Innovation. Lanham, MD: Lexington Books.
27
UFRN (2019). Superintendncia de tecnologia da informao. Sistemas institucionais integrados de gest- sig. [s. l.]. rio grande do norte. Natal: Universidade Federal do Rio Grande do Norte.
28
UFRN (2020). Resoluo consad no 51, de 17 de dezembro de 2020. disciplina o relacionamento entre a UFRNe os interessados no licenciamento e transferncia dos sistemas integrados de gest - sig-ufrn bem como sua manuteno, evoluo e sustentabilidade financeira. rio grande do norte, Brazil. Natal: Universidade Federal do Rio Grande do Norte.
29
van den BerkI.JansenS.LuinenburgL. (2010). “Software ecosystems: a software ecosystem strategy assessment model,” in Proceedings of the Fourth European Conference on Software Architecture: Companion Volume (ECSA'10) (Copenhagen: ACM), 127–134.
30
VasconcelosA. M. (2024). “Ecossistema de Software SIG-UFRN: Um Estudo Exploratio Sobre os Fatores Determinantes sua Adoo,” in Dissertao (Mestrado de Cicia da Computao) - Programa de P-Graduao em Cincia da Computao, Instituto de Cicias Exatas e Naturais (Belem: Universidade Federal Do Par).
31
VasconcelosA. M.OliveiraS. R. B. (2024a). “Analysis of software ecosystem use scenarios: a systematic review of the literature,” in 20th CONTECSI - International Conference on Information Systems and Technology Management.
32
VasconcelosA. M.OliveiraS. R. B. (2024b). “Identification of factors that define success or failure in the adoption of the sig-ufrn software ecosystem,” in Proceedings of the 20th Brazilian Symposium on Information Systems (Juiz de Fora: ACM), 1–10.
33
VasconcelosA. M.OliveiraS. R. B. (2024c). “Perceptions of the sig-ufrn implementation process: application of interviews,” in 20th CONTECSI - International Conference on Information Systems and Technology Management.
34
VasconcelosA. M.OliveiraS. R. B. (2025). Um estudo exploratio sobre os fatores determinantes adoo do ecossistema de software sig-ufrn. iSys-Brazil. J. Inform. Syst. 18, 5:1–5:22. doi: 10.5753/isys.2025.5650
35
WangS.ZhangH. (2025). Generative ai in international hotel marketing: impacts on employee creativity and performance. Int. J. Contemp. Hospital. Managem. 37, 2601–2626. doi: 10.1108/IJCHM-10-2024-1595
36
ZakiM. J.Meira JrW. (2014). Data Mining and Analysis: Fundamental Concepts and Algorithms. Cambridge: Cambridge University Press.
Summary
Keywords
focus group, grounded theory, selective coding, software ecosystems, theoretical framework, usage scenarios
Citation
Vasconcelos AM and Oliveira SRB (2026) An application of selective coding to create a theoretical framework on the factors that influence success or failure in adopting the SIG-UFRN software ecosystem. Front. Comput. Sci. 8:1816972. doi: 10.3389/fcomp.2026.1816972
Received
25 February 2026
Revised
05 June 2026
Accepted
05 June 2026
Published
02 July 2026
Volume
8 - 2026
Edited by
Martin Shepperd, Brunel University London, United Kingdom
Reviewed by
William Rodrigo Joanico, Federal University of Paraná, Brazil
Maicon Bernardino, Universidade Federal do Pampa - Campus Alegrete, Brazil
Updates
Copyright
© 2026 Vasconcelos and Oliveira.
This is an open-access article distributed under the terms of the Creative Commons Attribution License (CC BY). The use, distribution or reproduction in other forums is permitted, provided the original author(s) and the copyright owner(s) are credited and that the original publication in this journal is cited, in accordance with accepted academic practice. No use, distribution or reproduction is permitted which does not comply with these terms.
*Correspondence: Sandro Ronaldo Bezerra Oliveira, srbo@ufpa.br
Disclaimer
All claims expressed in this article are solely those of the authors and do not necessarily represent those of their affiliated organizations, or those of the publisher, the editors and the reviewers. Any product that may be evaluated in this article or claim that may be made by its manufacturer is not guaranteed or endorsed by the publisher.