Context: Since the beginnings of software engineering, metrics (such as SLOCs) and practices have been used in an attempt to measure and improve the features of software development projects, their process, or their contributors. Measuring and enhancing software ecosystem features brings a new complexity level because a software ecosystem comprises several interrelated software projects. Over the past two decades, software ecosystems have gained considerable attention, and researchers have proposed various metrics and practices to measure and improve software ecosystems' health. Objective: This thesis presents a systematic literature review that aims to build comprehensive taxonomies for software ecosystem health metrics and practices. These taxonomies synthesize the results of previous categorizations and update them with newer metrics and practices proposed since then. This study also aims to collect and synthesize all the definitions, metrics, and practices proposed to define, measure, and improve software ecosystem health in the literature. Method: I conducted a systematic literature review and identified 40 primary studies related to defining and measuring software ecosystem health. I extracted the definitions, metrics, and practices for software ecosystem health from the primary studies, and then I categorized the metrics and practices to build the taxonomies. Results: I identified a total of 7 different definitions for software ecosystem health, 142 different metrics, and 174 various practices for software ecosystem health. Our taxonomies for software ecosystem health metrics and practices have three categories (niche creation, productivity, and robustness). Each of these categories has several sub-categories of metrics and practices. Conclusion: Software ecosystems have a wide range of stakeholders that have different perspectives regarding software ecosystem health. To satisfy this spectrum, researchers have proposed various metrics and practices to measure and improve software ecosystems' health. To improve unifying contrasting opinions, I conducted this study. The metrics and practices proposed are diverse in both purpose and the data required to compute them. Some metrics are presented along with a method on how to compute them. In contrast, others are defined abstractly without an operational approach to calculate them, and some are mentioned without a clear rationale. Furthermore, the same metric or practice is often proposed in more than one publication using different names. This thesis addresses these alignment problems. / Graduate

Submitted by Fabio Sobreira Campos da Costa (fabio.sobreira@ufpe.br) on 2016-07-12T12:48:10Z No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) Dissertacao_Lucas_Moreno_2015.pdf: 1828699 bytes, checksum: 29da1d7fb693be0db619ca75b8f5a9e6 (MD5) / Made available in DSpace on 2016-07-12T12:48:10Z (GMT). No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) Dissertacao_Lucas_Moreno_2015.pdf: 1828699 bytes, checksum: 29da1d7fb693be0db619ca75b8f5a9e6 (MD5) Previous issue date: 2015-08-24 / Contexto: Atualmente, empresas de software têm adotado uma estratégia mais flexível através da abertura do produto para contribuições externas. Tal abertura proporciona a emergência dos Ecossistemas de Software, que são constituídos por um conjunto de atores que desenvolvem soluções de software sob uma plataforma comum. Objetivo: Entender e comparar os ecossistemas do Google Apps Enterprise e Microsoft Office 365 a partir do estudo de sua composição e redes de parcerias entre membros do ecossistema. Os dois ecossistemas foram escolhidos pela distinção entre os modelos de governança da Google e da Microsoft. Metodologia: Realizou-se uma coleta de dados automática a partir da utilização de um crawler nos marketplaces dos ecossistemas do Google Apps Enterprise e Microsoft Office 365 para a recuperação da lista de niche players e respectivas aplicações. Além disso, foram coletados de forma manual dados de parcerias entre niche players a partir de informações presentes nos websites de cada complementador. Os dados foram analisados através de um estudo comparativo entre as estruturas de rede formadas pelos niche players dos ecossistemas investigados. Resultados e discussões: Foram analisadas a composição e os relacionamentos de parceria dos ecossistemas do Google Apps Enterprise e Microsoft Office 365. Além disso, foi realizada uma comparação com os resultados obtidos em uma pesquisa anterior realizada por van Angeren (2013). Finalmente, foram postuladas três proposições sobre produtividade no ecossistema de software, relacionamentos de parceria e critérios de entrada. Conclusão: Pode-se concluir que o tamanho do ecossistema não determina seu grau de produtividade (número de aplicações por niche player) ou número de relacionamentos de parceria entre os niche players. Observou-se que a flexibilidade dos critérios de entrada do ecossistema atrai um grande número de niche players. / Context: Nowadays, software vendorshave adopted more flexible strategies, opening their products to external contributions. Such opening contributed for the emergence of Software Ecosystems, that can be defined as a set of actors developing software solutions in a single platform. Goals: We aim to understand and compare Google Apps Enterprise and Microsoft Office 365 Software Ecosystems, based on their niche players composition and partnership network. The two ecosystems were chosen by the distinction between governance models of Google and Microsoft. Research method: We built a web crawler to automatically collect the niche players list and their applications from Google Apps Enterprise and Microsoft Office 365 marketplaces. In addition, we manually collected data about partnership between niche players from the niche players websites. This data was analysed in a comparative study of the partnership network structures formed by niche players of both ecosystems. Results and discussion: We analysed the composition and partnership network of Google Apps Enterprise and Microsoft Office 365 ecosystems. In addition, we compared the current results with the results obtained in a previous research done in 2013. Finally, we postulated three propositions about productivity in the software ecosystems, partnership relationship and entry barriers. Conclusion: It was possible to conclude that the size of a software ecosystem or the number of partnership relationship are not the only factors that determine its productivity (number of applications per niche player). It was possible to observe as well that flexibility in entry barriers can attract a large number of niche players.

Submitted by Renata Lopes (renatasil82@gmail.com) on 2018-05-10T11:14:58Z No. of bitstreams: 1 andreluizcamposesqueffabdalla.pdf: 10771982 bytes, checksum: 662108f55e5849c1e43771419d176276 (MD5) / Approved for entry into archive by Adriana Oliveira (adriana.oliveira@ufjf.edu.br) on 2018-09-03T16:02:57Z (GMT) No. of bitstreams: 1 andreluizcamposesqueffabdalla.pdf: 10771982 bytes, checksum: 662108f55e5849c1e43771419d176276 (MD5) / Made available in DSpace on 2018-09-03T16:02:57Z (GMT). No. of bitstreams: 1 andreluizcamposesqueffabdalla.pdf: 10771982 bytes, checksum: 662108f55e5849c1e43771419d176276 (MD5) Previous issue date: 2018-03-22 / Os Sistemas de Recomendação (SR) buscam apresentar informações relevantes para os usuários no momento do consumo. A necessidade de recomendar recursos em diferentes domínios de aplicação e a necessidade do desenvolvimento de soluções focadas no reuso de componentes de SR, criam um cenário interessante para adoção de soluções na perspectiva de um Ecossistema de Software (ECOS). Um ECOS para SR deve permitir, além da interação entre atores e tecnologia, a integração com outros sistemas e plataformas que suportem outros ECOS. Através da proposição de uma plataforma tecnológica que suporte um ECOS, é possível auxiliar pesquisadores na compreensão acerca das diferentes maneiras que as organizações se relacionam. Ao aplicar a perspectiva ECOS em um domínio específico é possível centralizar os requisitos para o desenvolvimento de soluções, facilitando o reuso, criação e evolução de técnicas e abordagens específicas. A granularidade das soluções em SR, sem a possibilidade da definição de padrões de arquiteturas, aliada aos benefícios relacionados ao reuso e compartilhamento de técnicas e abordagens para SR, demonstra a necessidade de desenvolvimento de uma plataforma tecnológica, onde seja possível criar novas soluções, usufruir das soluções existentes e incentivar pesquisas nas duas principais áreas de estudo deste trabalho, Sistemas de Recomendação e Ecossistema de Software. Desta forma, o problema abordado por este estudo é a integração dos variados métodos, técnicas e abordagens de SR existentes de maneira sistemática e centralizada, sendo possível facilitar a implementação de novas soluções em SR, e ainda promover o reuso e compartilhamento destas soluções e também a colaboração entre os atores envolvidos. O objetivo geral deste estudo é propor o R.ECOS, uma plataforma tecnológica para suportar um ecossistema de software para recomendação de recursos a usuários, permitindo a integração entre suas soluções e de outros ECOS e ainda facilitar o desenvolvimento, reuso e compartilhamento destas soluções em SR. A avaliação da proposta foi realizada em duas etapas. Primeiro foram definidos dois Estudos de Viabilidade para validar a tecnologia utilizada e a arquitetura proposta. A seguir foram realizados dois Estudos de Caso em um contexto real de utilização. Os resultados indicam a viabilidade da proposta do estudo. / Recommender Systems (RS) attempt to present relevant information to users at the time of consumption. The need to recommend resources in different application domains and the need to develop solutions focused on the reuse of RS components, creates an interesting scenario for adopting solutions from the Software Ecosystem (SECO) perspective. A SECO for RS should allow, in addition to interaction between actors and technology, integrations with others systems and platforms that support others SECO. By proposing a technology platform that supports a SECO, it is possible to assist researchers in understanding the different ways that organizations relate. By applying the SECO perspective in a specific domain, it is possible to centralize the requirements for developing solutions, facilitating the reuse, creation and evolution of specific techniques and approaches. The granularity of RS solutions, without the possibility of defining architecture patterns, combined with the benefits related to the reuse and sharing of approaches for SR, demonstrates the need to develop a technological platform where it is possible to create new solutions, taking advantage of existing solutions and encouraging research in the two main areas of this work, Recommendation Systems and Software Ecosystem. In this way, the problem addressed by this study is the integration of the methods, techniques and approaches of existing RS in a systematic and centralized way, being possible to facilitate the implementation of new solutions in RS, and also to promote the reuse and sharing of solutions and also the collaboration among the involved actors. The general objective of this study is to propose R.ECOS, a technological platform to support a software ecosystem to recommend resources, allowing the integration between their solutions and other ECOS. The evaluation of the proposal was carried out in two stages. First, two Feasibility Studies were defined to validate the used technology and the proposed architecture. Later, two Case Studies were carried out in a real context of use. The results indicate the feasibility of the study proposal.

Submitted by Renata Lopes (renatasil82@gmail.com) on 2018-11-22T16:50:56Z No. of bitstreams: 1 iuriandradecarvalho.pdf: 2965898 bytes, checksum: c5ff96a680e2cbe98b73b24382ad162b (MD5) / Approved for entry into archive by Adriana Oliveira (adriana.oliveira@ufjf.edu.br) on 2018-11-23T12:53:17Z (GMT) No. of bitstreams: 1 iuriandradecarvalho.pdf: 2965898 bytes, checksum: c5ff96a680e2cbe98b73b24382ad162b (MD5) / Made available in DSpace on 2018-11-23T12:53:17Z (GMT). No. of bitstreams: 1 iuriandradecarvalho.pdf: 2965898 bytes, checksum: c5ff96a680e2cbe98b73b24382ad162b (MD5) Previous issue date: 2018-09-19 / CAPES - Coordenação de Aperfeiçoamento de Pessoal de Nível Superior / A complexidade do ambiente de Ecossistemas de Software (ECOS), onde o gerenciamento de processos e projetos não é trivial, traz grandes desafios para o controle de qualidade. Em acréscimo, os investimentos feitos pelas empresas e desenvolvedores externos podem ser perdidos caso o ECOS deixe de existir. Todos estes fatos são referentes à saúde de um ECOS, que é a capacidade na qual este se mantém e expande ao longo do tempo diante de desafios. Com base neste problema, foi proposta a arquitetura Heal Me, cujo objetivo é analisar a saúde de ECOS. No contexto desta pesquisa, foi efetuado um mapeamento sistemático, pelo qual foram identificadas as soluções atuais, assim como um conjunto de métricas para avaliação de saúde. Estas métricas foram avaliadas através de um estudo observacional, formalizadas e automatizadas como regras semânticas. Com estes recursos, foi desenvolvida uma ontologia de domínio, para analisar o ambiente de ECOS e aplicação das regras semânticas para análise de saúde. Sobre a base ontológica, foi proposta e desenvolvida a arquitetura Heal Me, uma arquitetura de software capaz de efetuar análises de saúde dos ECOS de forma automatizada. Uma vertente importante da automação propiciada é a utilização de APIs de repositórios para captura automática de alguns desses dados. Foi efetuado um estudo de caso com especialistas para avaliar a eficácia das análises deste primeiro esforço de implementação. Os resultados obtidos apontam indícios para a possibilidade da utilidade da arquitetura em seu objetivo, assim como vulnerabilidades a serem tratadas nas próximas versões. / The complexity of the Software Ecosystems (SECO) environment, where process and project management are not trivial, brings major challenges to quality control. In addition, investments made by companies and external developers may be lost if ECOS expires. All these facts refer to the health of a SECO, which is the capacity to be maintained and expanded over time in the face of challenges. Based on this problem, the Heal Me architecture was proposed, whose objective is to automatically analyze the health of a SECO. In the context of this research, a systematic mapping was performed, through which the current solutions were identified, as well as a set of metrics for health evaluation. These metrics were evaluated through an observational study, formalized and automated as semantic rules. With these resources, a domain ontology was developed to analyze the SECO environment and the application of semantic rules for health analysis. Heal Me architecture was proposed and developed over the ontological base, a software architecture capable of capturing SECO data and performing health analyzes in an automated way. An important aspect of the automation is the use of APIs repositories for automatic data capturing. A case study was carried out with specialists to analyses the effectiveness of this first implementation effort. The results obtained point to the feasibility of the proposed architecture, as well as vulnerabilities to be treated in the next versions.

The ability to carry communication services around, combined with the ubiquitous presence of computing technology, affects everything we do from how we pay for things to how we expect to interact with public institutions such as schools. There are now plenty of systems that convey education by utilizing mobile devices. As an extension of technology moving towards ubiquity, there are efforts aiming to bring this to an educational use as well. Efforts in this direction are channelized in the field of mobile learning. The speed of technological development, and the possibilities it brings introduces a large number of challenges when implemented in educational settings. These challenges can be related to for example pedagogical aspects, tools, implementations and organizations. Recent developments including the notions of learning ecosystems, learning landscapes and organizations suggest that the domain of mobile learning can be negatively affected from the lack of a systematic reuse approach. This thesis pursues these challenges by investigating how systematic reuse can be promoted in mobile learning systems. A collection of five peer-reviewed publications that elaborates on the different stages of the research process pursuing the main research question forms the core of this thesis. This research process includes a survey stage, elaborating on different aspects related to reuse and mobile learning, an analysis stage that resulted in a descriptive model and several additional domain models; and finally a stage where the descriptive model is refined into a reference model for mobile learning ecosystems. The outcomes of these activities and the analysis of these results provide some fundamental building blocks regarding how to approach the challenge of reuse in mobile learning systems. The proposed reference model can be considered as the first step towards the creation of a common vocabulary that can be used to compare Software Ecosystems within the domain of mobile learning.

Platform based ecosystems are becoming dominant models in the software engineering industry. ‘Big data’ has recently gained increased attention from both academia and practitioners and it is believed that big data affects every sector and industry. While an abundance of research focuses on big data and platform-based ecosystems, these two are typically approached as secluded spheres. This study aimed toward an investigation of big data’s role in the evolution of platform-based ecosystems in the software engineering industry. In the present thesis the influence of big data on the software engineering industry and more specifically, the impact of big data on the evolution of software ecosystems, is examined. A case study focused on a platform owner and pioneer in the software engineering industry has been conducted. This study identifies challenges and opportunities triggered by the advent of big data in context of platform-based ecosystems. Hence, considerable insight regarding the impact of big data on contemporary platform providers and the evolution of platform-centric ecosystems is gained. The findings illustrate that software ecosystems are affected by big data in a positive manner, but some identified challenges emerge and have to be tackled. Additionally, in this paper, it is suggested that both academia and practitioners should dig deeper into this relationship and identify how the evolution of platform-based ecosystems is impacted by the advent of big data.

Unexpected changes occurring in complex and dynamic domains render supporting systems unsuited to the new conditions. Examples of such domains include business ecosystems, digital service ecosystems, manufacturing, transport, and city modelling. These are regarded as ecosystem domains. Multi-agent systems are seen as an appropriate technology for their support, yet they lack the required ability to adapt to unexpected changes. The research presented in this thesis aims to create a multi-agent system based in-silico model endowed with the capability of adaptation to unexpected changes occurring in ecosystem domains. The approach taken consists of applying adaptation properties of complex adaptive systems, such as natural ecosystems, to multi-agent systems to create one which can cope with unexpected changes. A dynamic agent-based ecosystem model called DAEM is formalised by combining characteristics of natural ecosystem and principles of adaptive multi-agent systems. A set of experiments is presented using a DAEM prototype to demonstrate its resilience to unexpected changes in a hypothetical ecosystem. A comparison is made against a simulated typical solution for showing how DAEM is more resilient to unexpected changes than the typical approach. This supports the claim of this thesis that DAEM represents a significant contribution to knowledge. A software embodiment of DAEM to drive adaptation in ecosystem domains is presented and placed in an execution context evaluated by two practical examples of ecosystem domains. These show how DAEM suggests interactions to the supporting system of the execution context, and incorporates taken decisions into the ecosystem regarding interactions with other individuals. This supports the claim that the DAEM software embodiment is suitable for providing adaptation support in ecosystem domains, thus representing another significant contribution of this thesis. The contributions to knowledge of this thesis are then a) a formal model of a dynamic agent-based ecosystem called DAEM; and b) a software embodiment of DAEM, called DAEM layer, to support adaptation in ecosystem domains. Future work includes further tests to analyse patterns and make estimations in existing ecosystems, among others.

Context: The explosive growth of renowned software ecosystems such as the cloud-based accounting platform Xero, and the communication hub Slack has largely occurred because of an app marketplace they have built. To a large extent, in-app marketplaces are becoming mandatory for SaaS companies. Looking at the 15 largest SaaS companies, all of them have an app marketplace with a median number of 347 applications integrated to the marketplace [1]. It is challenging for any organization to orchestrate a platform independently. The more other participants contribute to that platform, greater resources are applied to create richer offerings for the platform’s end-users. Looking at the initial stages of when an organization transitions from a product to platform development, there is an underlying challenge of how that organization attracts third-party developers to partner and enrich the ecosystem. Objective: This thesis aims to identify what can be used to attract third-party developers or organizations to develop and integrate onto an emerging platform or- ganization. It also examines problem areas faced by emerging software ecosystems when trying to attract third-party developers onto their platform. Method: I performed a case study to investigate the needs of third-party devel- opers looking to develop on a platform organization. I also used mixed data collection to obtain different sources of information, including internal and external interviews, virtual events, an internal developer workshop, and an investigation of competitors and other software ecosystems. Results: The thesis highlights that emerging software ecosystems often do not have the resources or capacity to build an initial robust platform experience as some of the more established software ecosystems like HubSpot and Shopify. With the lack of research completed to date on emerging software ecosystems, I was motivated to investigate the best practices that are crucial to attract third-party developers onto the platform. Conclusion: Through thematic analysis, the study revealed eight emerging con- cepts. When transitioning to a software ecosystem, organizations have struggled with six common issues. Additionally, six recommendations were gathered to help guide emerging software ecosystems towards best practices to attract third-party developers onto their platform. / Graduate

Submitted by Inês Marinho (bele_ballet@hotmail.com) on 2016-06-20T15:13:44Z No. of bitstreams: 1 Dissertação - Awdren de Lima Fontão.pdf: 3467255 bytes, checksum: c628b86f0b320e89d4659daa37a0c5fd (MD5) / Approved for entry into archive by Divisão de Documentação/BC Biblioteca Central (ddbc@ufam.edu.br) on 2016-06-23T18:13:40Z (GMT) No. of bitstreams: 1 Dissertação - Awdren de Lima Fontão.pdf: 3467255 bytes, checksum: c628b86f0b320e89d4659daa37a0c5fd (MD5) / Approved for entry into archive by Divisão de Documentação/BC Biblioteca Central (ddbc@ufam.edu.br) on 2016-06-23T18:16:12Z (GMT) No. of bitstreams: 1 Dissertação - Awdren de Lima Fontão.pdf: 3467255 bytes, checksum: c628b86f0b320e89d4659daa37a0c5fd (MD5) / Made available in DSpace on 2016-06-23T18:16:12Z (GMT). No. of bitstreams: 1 Dissertação - Awdren de Lima Fontão.pdf: 3467255 bytes, checksum: c628b86f0b320e89d4659daa37a0c5fd (MD5) Previous issue date: 2016-03-02 / In a Mobile Software Ecosystem (MSECO), the software organizations have opened up their structures to external developers aiming to reach goals to ensure the MSECO is working properly, such as increasing number of users, mobile applications (apps) and developers. Thus, the management organization (keystone) must restructure its processes to support external developers and create ways to attract the development of apps. The development of apps requires an approach that allows developers to achieve the expected performance into the MSECO. However, there is a quality contribution barrier, the App Store, the App Store’s criteria do not guarantee that apps certified by these criteria have good performance in number of downloads and positive reviews into the MSECO. It is necessary to consider the developer engagement, the quality of support offered by the organization to developers by the evangelists and the existing processes into the MSECO. In this work, we describe a collaborative approach to support app certification in MSEO defined by pair reviews and surveys. This approach is called MSECO-CERT that is composed by three process (Orchestration – MSECO-ORQ, Support – MSECO-SUP and Construction – MSECO-DEV), including recommendations and practices to impact positively the MSECO’s health. The MSECO-CERT was evaluated with feasibility study and observational study. / Em um Ecossistema de Software Móvel (MSECO), as organizações de software passaram a abrir a sua estrutura para desenvolvedores externos visando atingir metas que garantam o funcionamento do MSECO, tais como o aumento do número de usuários, aplicações móveis (apps) e desenvolvedores. Desta forma, a organização central (keystone, em inglês) precisa reestruturar seus processos para lidar com os desenvolvedores externos e criar meios para motivar o desenvolvimento de apps. Neste contexto, o desenvolvimento de aplicações móveis requer uma abordagem que permita aos desenvolvedores alcançar o desempenho esperado dentro de um MSECO. Porém, há uma “barreira” de qualidade, a Loja de Apps. Os critérios de qualidade das lojas não garantem que as apps certificadas a partir deles obtenham o desempenho desejado em relação a número de downloads e avaliações positivas dentro do MSECO. É necessário considerar o engajamento do desenvolvedor, a qualidade de suporte oferecido pela organização aos desenvolvedores por meio dos evangelistas e os processos dentro do MSECO. Assim, acredita-se que trabalhando na qualidade dos processos envolvidos no MSECO pode-se chegar à qualidade do produto, neste caso, a app. Neste trabalho, foi definida uma abordagem para certificação de apps no contexto de MSECO, chamada de MSECO-CERT. Ela é composta por três processos (Orquestração – MSECO-ORQ, Suporte – MSECO-SUP e Construção – MSECO-DEV), recomendações e práticas relacionadas à fase de pré-publicação, ou seja, antes da app ser submetida pelo desenvolvedor à Loja de Apps. A MSECO-CERT foi avaliada por meio de estudo de viabilidade e um estudo de observação.

Submitted by isabela.moljf@hotmail.com (isabela.moljf@hotmail.com) on 2017-02-13T11:42:31Z No. of bitstreams: 1 guilhermegomesmartins.pdf: 2653766 bytes, checksum: c58fd5a1c1871badea4b7305135c8684 (MD5) / Approved for entry into archive by Adriana Oliveira (adriana.oliveira@ufjf.edu.br) on 2017-02-13T16:46:34Z (GMT) No. of bitstreams: 1 guilhermegomesmartins.pdf: 2653766 bytes, checksum: c58fd5a1c1871badea4b7305135c8684 (MD5) / Made available in DSpace on 2017-02-13T16:46:34Z (GMT). No. of bitstreams: 1 guilhermegomesmartins.pdf: 2653766 bytes, checksum: c58fd5a1c1871badea4b7305135c8684 (MD5) Previous issue date: 2016-09-13 / CAPES - Coordenação de Aperfeiçoamento de Pessoal de Nível Superior / [Contexto] Experimentos científicos complexos envolvem a utilização de dados e recursos distribuídos que necessitam da colaboração de diversos pesquisadores. Por envolver pesquisadores geograficamente distribuídos, o desenvolvimento de um experimento pode ser caracterizado através de um ecossistema de experimentação científica, onde grupos de pesquisa distribuídos interagem trocando informações para realizar um experimento. Neste contexto, a plataforma E-SECO implementa uma abordagem de ecossistema de software científico com o objetivo de apoiar a experimentação entre grupos de pesquisadores distribuídos. Entretanto, não basta oferecer apenas recursos de colaboração para diferentes grupos de pesquisa. Para que os grupos possam de fato colaborar entre si, é necessário apoiar as suas atividades considerando o contexto de cada um deles, bem como as suas necessidades. [Objetivo] Diante disso, o objetivo deste trabalho é tratar a falta de um processo para apoiar o desenvolvimento de serviços de colaboração de modo a considerar informações do contexto de cada um dos grupos. Em específico, grupos que utilizam uma plataforma de ecossistema de software científico. [Método] Para isso, este trabalho apresenta duas estratégias: (i) um processo para o desenvolvimento de serviços de colaboração que considera a abordagem de Linha de Produtos de Software e de uma Arquitetura Orientada a Serviço, e (ii) um mecanismo para apoiar o alinhamento entre os serviços de colaboração considerando-se a necessidade de eles interoperarem. [Resultados] A partir deste processo, é possível disponibilizar serviços de colaboração que atendam às necessidades específicas de cada grupo de pesquisa e, com o mecanismo de apoio ao alinhamento de seus conceitos, potencializar a interoperabilidade em ecossistemas de software. Podem-se citar como contribuições deste trabalho a apresentação de um processo para o desenvolvimento de serviços de colaboração, um mecanismo de apoio ao alinhamento entre serviços de colaboração, e a investigação de sua viabilidade. / [Context] Complex scientific experiments involve the use of distributed data and resources that require the collaboration of several researchers. Considering that they comprise geographically distributed researchers, the conduction of an experiment can be characterized by a scientific experimentation ecosystem in which distributed research groups interact by exchanging information to perform an experiment. In this context, the E-SECO platform implements a software scientific ecosystem approach in order to support the development of services that support the distributed experimentation among groups of researchers. However, it is not enough to only offer collaboration features to support the development of services by different groups. It is also necessary to support its activities considering the context of each of group and their needs, as well as the mechanisms that compose a software ecosystem. [Objective] Thus, the objective of this study is to address the lack of a process to support the development of such collaboration services to consider information on the context of each group. In particular, groups which utilize a scientific platform software ecosystem. [Method] Therefore, this work presents two strategies: (i) a process for the development of collaborative services that considers the Software Product Line and a Service Oriented Architecture, and (ii) a mechanism to support the alignment between collaboration services considering the need of them to interoperate. [Results] Experiments were performed in order to verify the feasibility of the solution. From the proposed process, it is possible to provide collaboration services that fulfill the requirements of each research group and, with the support mechanism for the alignment of its concepts, it is possible to enhance the interoperability of software ecosystems. As contributions it can be cited: present a process for the development of collaboration services, and offer a mechanism to support the alignment between collaboration services.