Due to Industry 4.0 (I4.0) the software ecosystem is constantly changing, and new possibilities and challenges are arising. The purpose of this Master Thesis is to map the software ecosystem in the automotive industry in order to understand the position of Atlas Copco and what gaps an industrial tool supplier can close. In addition, find out what opportunities and challenges that exist in the ecosystem today. Since Industry 4.0 and the software ecosystem are relatively new topics and alters continuously, the study was carried out in an abductive approach and a research design model was created according to that. By combining literature study with empirical study such as interviews, a better understanding was gained which laid the foundation of accumulating a deeper knowledge about the research field and made it feasible to answer the research questions. The current structure in different markets of the software ecosystem are shaped according to an old industry standard for modelling system structures. Differences and similarities between the markets can be found, which explains difficulties in providing software globally. By analysing and combining the current structures for each market, including the answers gained from the conducted interviews, a model was created. A new model for the definition of a software ecosystem in the automotive industry was the result. Additionally, a new way of structuring and visualizing the generic structure of the software ecosystem for Atlas Copco in the Automotive industry was presented as well. The latter model could be used as a tool, that enables a better understanding of the software ecosystem as well as a way to present new solutions to customers. In the ecosystem Atlas Copco takes the role as a premium industrial tool supplier and a provider of software used to configure and monitor quality and errors in the assembly processes. Hence, they broaden their market to become a software supplier. However, thanks to I4.0 technologies, there are potential areas in the production where it is possible for Atlas Copco to extend their establishment further to get more market shares of the software market as well as to provide more value to their customers. Although, the recommendation for Atlas Copco is to shape a reference architecture and focus on software close to the operations of industrial equipment. / Mjukvaruekosystemet är något som ständigt är i förändring där nya möjligheter och utmaningar uppstår i ekosystemet i anknytning till Industri 4.0 (I4.0). Syftet med denna masteruppsats är att kartlägga mjukvaruekosystemet i fordonstillverkningsindustrin för ta reda på vilken position AtlasCopco har och vilka luckor en industriverktygsleverantör kan sluta samt undersöka utmaningar och möjligheter som existerar idag. En forskningsdesignmodell skapades och eftersom projektet omfattar ämnet Industri 4.0 samt mjukvaruekosystemet som är ett relativt nytt ämne som är under kontinuerlig förändring, så utfördes studien baserat på abduktiv strategi. Genom att kombinera litteraturstudier med empiriska studier som intervjuer erhölls en bättre förståelse som lade grunden för att vidare samla på djupare kunskap om forskningsområdet vilket gjorde det möjligt att svara på forskningsfrågorna. Den nuvarande strukturen på olika marknader i mjukvaruekosystemet formas enligt en gammal branschstandard för ett modelleringssystemstrukturer. Skillnader och likheter mellan marknaderna har presenterats som förklarar svårigheterna med att tillhandahålla programvara globalt. I samband med att analysera och kombinera de nuvarande strukturerna för varje marknad, inklusive svaren från de genomförda intervjuerna, har modeller tagits fram. I resultatet presenteras en ny modell för att definiera ett mjukvaruekosystem inom bilindustrin. Dessutom presenterades också ett nytt sätt att strukturera och visualisera den generiska strukturen i mjukvaruekosystemet för Atlas Copco inom fordonsindustrin. Modellen kan användas som ett verktyg för att lättare förstå mjukvaruekosystemet, och till att presentera nya lösningar för kunderna. I ekosystemet tar AtlasCopco rollen som en premiumleverantör av industriella verktyg, inklusive att tillhandahålla programvara som används för att konfigurera, övervaka kvalitet och fel i monteringsprocesserna. Detta breddar Atlas Copcos marknad till att även bli en mjukvaruleverantör. Tack vare I4.0 teknik finns det potentiella produktionsområden där det är möjligt för Atlas Copco att etablera sig ännu mer, för att få fler marknadsandelar på mjukvarumarknaden samt ge mer värde till sina kunder. Rekommendationen är att Atlas Copco skapar en referensarkitektur samt fokusera på mjukvara nära kopplat till operationsnivån och industriverktyg.

Målet med denna studie är att utveckla en adapterprototyp mot en öppen energiplattformoch dokumentera utvecklingsprocessen. Fokus ligger på att integreraPhilips Hue, ett system för styra trådlösa lampor mot plattformen Elis (Mobile servicesfor energy e ciency in existing buildings). Inom en begränsad tidsram så skavi sätta oss in i två främmande system till en sådan grad att vi kan skapa kommunikationenmellan dem. Inledningsvis krävs det att vi läser dokumentation och att vijobbar fram en arbetsplan. Vidare kommer vi lösa den adaption som krävs för attvärden mellan det två systemen överensstämmer och fungerar. Vi kommer användaoss av intervjuer för att få klarhet i hur plattformen är uppbyggd och grunden tillderas designval. Metoden design research används för att på ett iterativt sätt skapadelmål och successivt utveckla och utvärdera arbete. Målet med design research äratt skapa en artefakt, en adapterprototyp i vårt fall. Vi gjorde totalt fyra iterationerdär vi delade upp arbetet. Steg ett var att lära oss om plattformen, steg två lära ossPhilips Hue. Först i steg tre började vi utveckla vår adapterprototyp med kunskapenfrån det första iterationerna Slutligen intervjuade vi utvecklare i Elis och prata meddom om vad vi har kommit fram till och diskuterade fördelarna och nackdelarna vistött på vid utveckling mot deras plattform. Vi kommer med synpunkter och sakervi anser kan förbättras och hur adaptern bidrar till ett Elis ur ett software ecosystemperspektiv.. . . / The purpose of this essay is to develop an adapter prototype for an open energyplatform and document the development process. We focus on integrating PhilipsHue personal wireless lighting unto the platform Elis (Mobile services for energye ciency in existing buildings). Within the short timeframe of this study we intendto reach a level of understanding enough to make the systems communicate usingour adapter prototype. Initially we study documentation and prepares a work plan.Further more we try to solve the adaptation needed for the two system to communicate,this involves converting and matching up values. We will do some interviewswith the developers of Elis to get the big picture of how and why they designed theplatform they way it is. The research paradigm design research is a iterative methodologythat creates milestones, develop prototypes and evaluate the work. Thegoal of design research is to create an artifact, in our case an adapterprototype. Wemade a total of four iterations where the work was divided. Step one was to learnhow the platform works and step two was to study Philips Hue. At step three theimplementation of our prototype with the preparatory work from the rst iterationscould begin. The nal step was to interview members of Elis development team to nd out the impact of our work and to discuss the pros and cons of working withtheir platform. We present opinions and ndings of things we have found that canbe improved. We also de ne how our adapter bene ts Elis in a software ecosystemperspective.. . .

Submitted by Fabio Sobreira Campos da Costa (fabio.sobreira@ufpe.br) on 2017-02-23T12:19:21Z No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) A Theory of Power in Software Ecosystems formed by Small to Medium Enterprises _ GeorgeValença.pdf: 3429187 bytes, checksum: 8f170a2be6f42b4cf8f070f5f7ebd7b5 (MD5) / Made available in DSpace on 2017-02-23T12:19:21Z (GMT). No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) A Theory of Power in Software Ecosystems formed by Small to Medium Enterprises _ GeorgeValença.pdf: 3429187 bytes, checksum: 8f170a2be6f42b4cf8f070f5f7ebd7b5 (MD5) Previous issue date: 2016-08-26 / Context: the emergence of software ecosystems has changed the dynamics of software industry in the last decade. An ecosystem consists of a set of businesses functioning as a unit and interacting with a shared market for software and services, together with the relationships involving them. Software ecosystems originate in partnerships among software companies as a strategy to acquire complementary skills and features, obtain new customers, as well as divide R&D costs. In this setting, partner companies rely on each other for survival and effectiveness, which generates a network of dependent actors and a flow of power among them. Aims: the goal of this research is to develop a substantive theory to explain how power and dependence manifest in partnerships among small-to-medium enterprises (SMEs) building a software ecosystem. This result enables us to describe the dynamics of partnerships in this environment, since power is a base atomic particle of relationships. Method: we performed two exploratory case studies of software ecosystems formed by SMEs. We collected rich qualitative data from eight software companies by means of twenty-seven semi-structured interviews. In addition, we considered companies’ internal documents, field notes and web-based data. Thematic analysis was adopted to organise and describe the data set. The results were interpreted in light of a theoretical framework underpinned by French and Raven’s power taxonomy and later refined in six confirmatory interviews with the companies. Finally, we performed a cross-case analysis to synthesise our findings and build the theory. Results: the resultant theory, called PRM-SECO, highlights the interactions among different power forms in addition to their correspondent source(s) in the software ecosystem. It reveals that (1) power is fluid in a software ecosystem formed by SMEs; (2) pool of customers and skill/knowledge are the most frequent power sources; (3) expert power is the fundamental power form that triggers most power capabilities held by SMEs; (4) reward power attaches the partner and is often exercised by SMEs; (5) coercive power disturbs the partnerships and is rarely exercised by SMEs; (6) referent power tends to supersede other power forms and is rarely held by SMEs; and (7) legitimate power is the most frequent power form exercised by SMEs. Conclusion: this theory provides a better understanding on how power and dependence influence the behaviour and coordination of companies within a software ecosystem. The particular focus on SMEs complements the state-of-art, since most research in the field concerns mature ecosystems governed by big players such as SAP and Apple. It is a useful lens for researchers to explore ecosystem partnerships. In addition, it is a valuable tool for companies to analyse power distribution, have insights on how to evolve their participation in the network and define sustainable strategies for ecosystem governance. / Contexto: o surgimento de ecossistemas de software tem mudado a dinâmica da indústria de software na última década. Um ecossistema consiste em um conjunto de empresas que funcionam como uma unidade e interagem com um mercado compartilhado de software e serviços, junto com os relacionamentos que as envolvem. Ecossistemas de software têm origem nas parcerias entre empresas de software como uma estratégia para adquirir competências e funcionalidades complementares, obter novos clientes, bem como dividir custos de P&D. Neste cenário, as empresas parceiras dependem umas das outras para sobrevivência e efetividade, o que gera uma rede de atores dependentes e um fluxo de poder entre eles. Objetivos: o objetivo desta pesquisa é desenvolver uma teoria substantiva para explicar como poder e dependência se manifestam em parcerias entre pequenas e médias empresas (PMEs) construindo um ecossistema de software. Este resultado nos permite descrever a dinâmica das parcerias neste ambiente, uma vez que poder é uma partícula atômica de base dos relacionamentos. Método: nós realizamos dois estudos de caso exploratórios de ecossistemas de software formados por PMEs. Nós coletamos dados qualitativos ricos de oito empresas de software por meio de vinte e sete entrevistas semiestruturadas. Além disso, nós consideramos documentos internos das empresas, notas de campo e dados da web. Análise temática foi adotada para organizar e descrever o conjunto de dados. Os resultados foram interpretados à luz de um quadro teórico apoiado pela taxonomia de poder de French e Raven, e posteriormente refinados em seis entrevistas de confirmação com as empresas. Por fim, nós realizamos um processo de cruzamento de casos para sintetizar nossos resultados e construir a teoria. Resultados: a teoria resultante, denominada PRM-SECO, destaca as interações entre diferentes formas de poder, além da correspondente(s) fonte(s) no ecossistema de software. Ela revela que (1) o poder é fluido em um ecossistema de software formado por PMEs; (2) base de clientes e competências/conhecimento são as fontes de poder mais frequentemente usadas pelas PMEs; (3) poder do conhecimento é a forma de poder fundamental, que gera a maioria das capacidades de poder que as PMEs possuem; (4) poder de recompensa aproxima o parceiro e muitas vezes é exercido pelas PMEs; (5) poder coercitivo perturba as parcerias e raramente é exercido pelas PMEs; (6) poder de referência tende a suplantar outras formas de poder e raramente é detido pelas PMEs; e (7) poder legítimo é a forma de poder mais frequentemente exercida pelas PMEs. Conclusão: esta teoria oferece uma melhor compreensão sobre como poder e dependência influenciam o comportamento e coordenação de empresas em um ecossistema de software. O foco particular em PMEs complementa o estado-da-arte, uma vez que a maioria das pesquisas na área diz respeito a ecossistemas governados por grandes atores, tais como SAP e Apple. É uma lente útil para que pesquisadores explorem parcerias em ecossistemas. Além disso, é uma ferramenta valiosa para as empresas analisarem a distribuição de poder, terem ideias sobre como evoluir a sua participação na rede e definirem estratégias sustentáveis para a governança do ecossistema.

Submitted by Fabio Sobreira Campos da Costa (fabio.sobreira@ufpe.br) on 2017-02-23T13:43:15Z No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) A Theory of Power in Software Ecosystems formed by Small to Medium Enterprises _ GeorgeValença.pdf: 3429187 bytes, checksum: 8f170a2be6f42b4cf8f070f5f7ebd7b5 (MD5) / Made available in DSpace on 2017-02-23T13:43:15Z (GMT). No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) A Theory of Power in Software Ecosystems formed by Small to Medium Enterprises _ GeorgeValença.pdf: 3429187 bytes, checksum: 8f170a2be6f42b4cf8f070f5f7ebd7b5 (MD5) Previous issue date: 2016-08-26 / Contexto: o surgimento de ecossistemas de software tem mudado a dinâmica da indústria de software na última década. Um ecossistema consiste em um conjunto de empresas que funcionam como uma unidade e interagem com um mercado compartilhado de software e serviços, junto com os relacionamentos que as envolvem. Ecossistemas de software têm origem nas parcerias entre empresas de software como uma estratégia para adquirir competências e funcionalidades complementares, obter novos clientes, bem como dividir custos de P&D. Neste cenário, as empresas parceiras dependem umas das outras para sobrevivência e efetividade, o que gera uma rede de atores dependentes e um fluxo de poder entre eles. Objetivos: o objetivo desta pesquisa é desenvolver uma teoria substantiva para explicar como poder e dependência se manifestam em parcerias entre pequenas e médias empresas (PMEs) construindo um ecossistema de software. Este resultado nos permite descrever a dinâmica das parcerias neste ambiente, uma vez que poder é uma partícula atômica de base dos relacionamentos. Método: nós realizamos dois estudos de caso exploratórios de ecossistemas de software formados por PMEs. Nós coletamos dados qualitativos ricos de oito empresas de software por meio de vinte e sete entrevistas semiestruturadas. Além disso, nós consideramos documentos internos das empresas, notas de campo e dados da web. Análise temática foi adotada para organizar e descrever o conjunto de dados. Os resultados foram interpretados à luz de um quadro teórico apoiado pela taxonomia de poder de French e Raven, e posteriormente refinados em seis entrevistas de confirmação com as empresas. Por fim, nós realizamos um processo de cruzamento de casos para sintetizar nossos resultados e construir a teoria. Resultados: a teoria resultante, denominada PRM-SECO, destaca as interações entre diferentes formas de poder, além da correspondente(s) fonte(s) no ecossistema de software. Ela revela que (1) o poder é fluido em um ecossistema de software formado por PMEs; (2) base de clientes e competências/conhecimento são as fontes de poder mais frequentemente usadas pelas PMEs; (3) poder do conhecimento é a forma de poder fundamental, que gera a maioria das capacidades de poder que as PMEs possuem; (4) poder de recompensa aproxima o parceiro e muitas vezes é exercido pelas PMEs; (5) poder coercitivo perturba as parcerias e raramente é exercido pelas PMEs; (6) poder de referência tende a suplantar outras formas de poder e raramente é detido pelas PMEs; e (7) poder legítimo é a forma de poder mais frequentemente exercida pelas PMEs. Conclusão: esta teoria oferece uma melhor compreensão sobre como poder e dependência influenciam o comportamento e coordenação de empresas em um ecossistema de software. O foco particular em PMEs complementa o estado-da-arte, uma vez que a maioria das pesquisas na área diz respeito a ecossistemas governados por grandes atores, tais como SAP e Apple. É uma lente útil para que pesquisadores explorem parcerias em ecossistemas. Além disso, é uma ferramenta valiosa para as empresas analisarem a distribuição de poder, terem ideias sobre como evoluir a sua participação na rede e definirem estratégias sustentáveis para a governança do ecossistema. / Context: the emergence of software ecosystems has changed the dynamics of software industry in the last decade. An ecosystem consists of a set of businesses functioning as a unit and interacting with a shared market for software and services, together with the relationships involving them. Software ecosystems originate in partnerships among software companies as a strategy to acquire complementary skills and features, obtain new customers, as well as divide R&D costs. In this setting, partner companies rely on each other for survival and effectiveness, which generates a network of dependent actors and a flow of power among them. Aims: the goal of this research is to develop a substantive theory to explain how power and dependence manifest in partnerships among small-to-medium enterprises (SMEs) building a software ecosystem. This result enables us to describe the dynamics of partnerships in this environment, since power is a base atomic particle of relationships. Method: we performed two exploratory case studies of software ecosystems formed by SMEs. We collected rich qualitative data from eight software companies by means of twenty-seven semi-structured interviews. In addition, we considered companies’ internal documents, field notes and web-based data. Thematic analysis was adopted to organise and describe the data set. The results were interpreted in light of a theoretical framework underpinned by French and Raven’s power taxonomy and later refined in six confirmatory interviews with the companies. Finally, we performed a cross-case analysis to synthesise our findings and build the theory. Results: the resultant theory, called PRM-SECO, highlights the interactions among different power forms in addition to their correspondent source(s) in the software ecosystem. It reveals that (1) power is fluid in a software ecosystem formed by SMEs; (2) pool of customers and skill/knowledge are the most frequent power sources; (3) expert power is the fundamental power form that triggers most power capabilities held by SMEs; (4) reward power attaches the partner and is often exercised by SMEs; (5) coercive power disturbs the partnerships and is rarely exercised by SMEs; (6) referent power tends to supersede other power forms and is rarely held by SMEs; and (7) legitimate power is the most frequent power form exercised by SMEs. Conclusion: this theory provides a better understanding on how power and dependence influence the behaviour and coordination of companies within a software ecosystem. The particular focus on SMEs complements the state-of-art, since most research in the field concerns mature ecosystems governed by big players such as SAP and Apple. It is a useful lens for researchers to explore ecosystem partnerships. In addition, it is a valuable tool for companies to analyse power distribution, have insights on how to evolve their participation in the network and define sustainable strategies for ecosystem governance.

Submitted by Renata Lopes (renatasil82@gmail.com) on 2018-05-04T11:52:00Z No. of bitstreams: 1 leonardodeaguiarpereira.pdf: 2326653 bytes, checksum: 8c6f963d57bb5da46d8fcfcac54d29b8 (MD5) / Approved for entry into archive by Adriana Oliveira (adriana.oliveira@ufjf.edu.br) on 2018-09-03T16:02:00Z (GMT) No. of bitstreams: 1 leonardodeaguiarpereira.pdf: 2326653 bytes, checksum: 8c6f963d57bb5da46d8fcfcac54d29b8 (MD5) / Made available in DSpace on 2018-09-03T16:02:00Z (GMT). No. of bitstreams: 1 leonardodeaguiarpereira.pdf: 2326653 bytes, checksum: 8c6f963d57bb5da46d8fcfcac54d29b8 (MD5) Previous issue date: 2018-03-22 / Plataformas de apoio à experimentação científica apoiam cientistas e permitem que eles possam desfrutar de recursos para prosseguir com suas pesquisas. Dentre esses recursos estão os serviços científicos, usados para processar dados em determinadas tarefas de um processo de experimentação científica. Desenvolvedores especializados criam e mantêm esses serviços científicos. O sucesso de uma experimentação científica depende da correta execução de seu processo. Como os serviços científicos são utilizados em tarefas dos processos, suas falhas comprometem toda a experimentação. Por isso, é importante que os serviços estejam funcionando corretamente. Neste contexto, é necessário apoiar o desenvolvedor de serviços científicos para que ele possa desenvolver serviços com o máximo de eficiência possível. Diante disso, o objetivo deste trabalho é apresentar recursos que buscam apoiar o desenvolvimento de serviços científicos em uma plataforma de ecossistema de software científico. Esses recursos são associados a um processo de desenvolvimento de serviços que mapeia as atividades dos desenvolvedores e cientistas durante o desenvolvimento de serviços. Apresenta uma interface para análise contextual dos serviços, oferecendo elementos de visualização associados a informações contextuais. Além disso, utiliza a análise de redes sociais científicas para auxiliar na seleção de cientistas mais adequados à avaliação dos serviços. Visando avaliar estes recursos, foram realizados estudos de caso envolvendo o desenvolvimento de serviços científicos. Os resultados sugerem que os recursos empregados podem apoiar o desenvolvimento de serviços científicos em uma plataforma de ecossistema de software científico. / Platforms supporting scientific experimentation support scientists and allow them the use of resources to pursue their research. Among these resources are the scientific services, used to process data in certain tasks of a process of scientific experimentation. Specialized developers create and maintain these scientific services. The success of a scientific experiment depends on the correct execution of its process. As scientific services are used in process tasks, their failures undermine all experimentation. Therefore, it is important that the services are working properly. In this context, it is necessary to support the scientific services developer so that he can develop services as efficiently as possible. Therefore, the objective of this work is to present resources that seek to support the development of scientific services in a scientific software ecosystem platform. These resources are associated with a service development process that maps the activities of developers and scientists during service development. It presents an interface for contextual analysis of the services, offering elements of visualization associated with contextual information. In addition, it uses the analysis of scientific social networks to assist in the selection of better suited scientists to the evaluation of services. In order to evaluate these resources, case studies involving the development of scientific services were carried out. The results suggest that the resources employed can support the development of scientific services in a scientific software ecosystem platform.

Submitted by Renata Lopes (renatasil82@gmail.com) on 2017-10-23T17:43:12Z No. of bitstreams: 1 phillipeisraelmarques.pdf: 8922079 bytes, checksum: 6a86d6e40e9d80c77e61a71e2c42f8e5 (MD5) / Approved for entry into archive by Adriana Oliveira (adriana.oliveira@ufjf.edu.br) on 2017-11-09T13:52:35Z (GMT) No. of bitstreams: 1 phillipeisraelmarques.pdf: 8922079 bytes, checksum: 6a86d6e40e9d80c77e61a71e2c42f8e5 (MD5) / Made available in DSpace on 2017-11-09T13:52:35Z (GMT). No. of bitstreams: 1 phillipeisraelmarques.pdf: 8922079 bytes, checksum: 6a86d6e40e9d80c77e61a71e2c42f8e5 (MD5) Previous issue date: 2017-08-23 / CAPES - Coordenação de Aperfeiçoamento de Pessoal de Nível Superior / A área de e-Science envolve a realização de experimentos científicos complexos, normalmente apoiados por workflows. Esses experimentos geralmente utilizam dados e recursos distribuídos, e podem ser apoiados por uma plataforma de ecossistema de software científico. Neste contexto, é necessário permitir que diferentes serviços web possam ser compostos, reutilizados, além de interoperarem na plataforma para tratar das complexidades dos experimentos. Entretanto, compor serviços em plataformas de ecossistemas é uma atividade complexa, considerando, sobretudo, os requisitos funcionais e não funcionais desses serviços. Diante disso, o objetivo deste trabalho é apresentar um mecanismo que busca apoiar a composição de serviços no contexto de um ecossistema de software científico. Para tanto, esse mecanismo é associado ao processo de criação de serviços da plataforma de ecossistema de software científico. Oferece elementos de visualização para representar os relacionamentos de dependência funcional e interoperabilidade entre os serviços. Além disso, utiliza a análise de redes sociais científicas para identificar potenciais colaboradores. Os pesquisadores identificados poderão interagir com o auxílio das visualizações existentes, no espaço de trabalho compartilhado, para avaliar as composições. Essa plataforma, denominada E-SECO, apoia as diferentes fases do ciclo de vida de um experimento científico. A partir desse mecanismo, cientistas interagem e analisam as relações entre serviços nas composições realizadas considerando, sobretudo, as métricas de dependência funcional e a interoperabilidade entre os serviços existentes em diferentes instâncias da plataforma. Visando avaliar o mecanismo para apoiar a composição de serviços, foram realizados estudos de caso na plataforma E-SECO. / The area of e-Science encompasses performing complex scientific experiments, usually supported by workflows. These experiments generally use distributed data and resources, and can be supported by a scientific software ecosystem platform. In this context, it is necessary to allow different web services to be composed, reused, and interoperate in the platform to deal with the complexities of the experiments. However, performing services composition on ecosystem platform is a complex activity which requires computational support, considering, above all, the functional and non-functional requirements of these services. Therefore, the goal of this work is to present a mechanism that aims to support services composition in scientific software ecosystem context. To this end, this mechanism is associated to the service construction process of the scientific software ecosystem platform. It also provides visualization elements to represent functional dependency and interoperability relationships between the services. In addition, it uses scientific social networks analysis to identify potential collaborators. The identified researchers may interact through the visualizations, in the shared workspace, to evaluate the compositions. This platform, named E-SECO, supports different phases of the scientific experiment life cycles. From this mechanism, scientists interact and analyze the relationships between services in compositions which were performed considering, above all, the functional dependency metrics and interoperability issues between existing services in different instances of the platform. In order to evaluate the mechanism to support services composition, case studies were carried out on the E-SECO platform.

Software Product Lines (SPLs) and Software Ecosystems (SECOs) are approaches to capturing families of closely related software systems in terms of common and variable functionality (variability in space). SPLs and especially SECOs are subject to software evolution to adapt to new or changed requirements resulting in different versions of the software family and its variable assets (variability in time). Both dimensions may be interconnected (e.g., through version incompatibilities) and, thus, have to be handled simultaneously as not all customers upgrade their respective products immediately or completely. However, there currently is no integrated approach allowing variant derivation of features in different version combinations. In this thesis, remedy is provided in the form of an integrated approach making contributions in three areas: (1) As variability model, Hyper-Feature Models (HFMs) and a version-aware constraint language are introduced to conceptually capture variability in time as features and feature versions. (2) As variability realization mechanism, delta modeling is extended for variability in time, and a language creation infrastructure is provided to devise suitable delta languages. (3) For the variant derivation procedure, an automatic version selection mechanism is presented as well as a procedure to derive large parts of the application order for delta modules from the structure of the HFM. The presented integrated approach enables derivation of concrete software systems from an SPL or a SECO where both features and feature versions may be configured.

Software Product Lines (SPLs) and Software Ecosystems (SECOs) are approaches to capturing families of closely related software systems in terms of common and variable functionality (variability in space). SPLs and especially SECOs are subject to software evolution to adapt to new or changed requirements resulting in different versions of the software family and its variable assets (variability in time). Both dimensions may be interconnected (e.g., through version incompatibilities) and, thus, have to be handled simultaneously as not all customers upgrade their respective products immediately or completely. However, there currently is no integrated approach allowing variant derivation of features in different version combinations. In this thesis, remedy is provided in the form of an integrated approach making contributions in three areas: (1) As variability model, Hyper-Feature Models (HFMs) and a version-aware constraint language are introduced to conceptually capture variability in time as features and feature versions. (2) As variability realization mechanism, delta modeling is extended for variability in time, and a language creation infrastructure is provided to devise suitable delta languages. (3) For the variant derivation procedure, an automatic version selection mechanism is presented as well as a procedure to derive large parts of the application order for delta modules from the structure of the HFM. The presented integrated approach enables derivation of concrete software systems from an SPL or a SECO where both features and feature versions may be configured.:I. Context and Preliminaries 1. The Configurable TurtleBot Driver as Running Example 1.1. TurtleBot: A Domestic Service Robot 1.2. Configurable Driver Functionality 1.3. Software Realization Artifacts 1.4. Development History of the Driver Software 2. Families of Variable Software Systems 2.1. Variability 2.1.1. Variability in Space and Time 2.1.2. Internal and External Variability 2.2. Manifestations of Configuration Knowledge 2.2.1. Variability Models 2.2.2. Variability Realization Mechanisms 2.2.3. Variability in Realization Assets 2.3. Types of Software Families 2.3.1. Software Product Lines 2.3.2. Software Ecosystems 2.3.3. Comparison of Software Product Lines and Software Ecosystems 3. Fundamental Approaches and Technologies of the Thesis 3.1. Model-Driven Software Development 3.1.1. Metamodeling Levels 3.1.2. Utilizing Models in Generative Approaches 3.1.3. Representation of Languages using Metamodels 3.1.4. Changing the Model-Representation of Artifacts 3.1.5. Suitability of Model-Driven Software Development 3.2. Fundamental Variability Management Techniques of the Thesis 3.2.1. Feature Models as Variability Models 3.2.2. Delta Modeling as Variability Realization Mechanism 3.2.3. Variant Derivation Process of Delta Modeling with Feature Models 3.3. Constraint Satisfaction Problems 3.4. Scope 3.4.1. Problem Statement 3.4.2. Requirements 3.4.3. Assumptions and Boundaries II. Integrated Management of Variability in Space and Time 4. Capturing Variability in Space and Time with Hyper-Feature Models 4.1. Feature Models Cannot Capture Variability in Time 4.2. Formal Definition of Feature Models 4.3. Definition of Hyper-Feature Models 4.4. Creation of Hyper-Feature Model Versions 4.5. Version-Aware Constraints to Represent Version Dependencies and Incompatibilities 4.6. Hyper-Feature Models are a True Extension to Feature Models 4.7. Case Study 4.8. Demarcation from Related Work 4.9. Chapter Summary 5. Creating Delta Languages Suitable for Variability in Space and Time 5.1. Current Delta Languages are not Suitable for Variability in Time 5.2. Software Fault Trees as Example of a Source Language 5.3. Evolution Delta Modules as Manifestation of Variability in Time 5.4. Automating Delta Language Generation 5.4.1. Standard Delta Operations Realize Usual Functionality 5.4.2. Custom Delta Operations Realize Specialized Functionality 5.5. Delta Language Creation Infrastructure 5.5.1. The Common Base Delta Language Provides Shared Functionality for all Delta Languages 5.5.2. Delta Dialects Define Delta Operations for Custom Delta Languages 5.5.3. Custom Delta Languages Enable Variability in Source Languages 5.6. Case Study 5.7. Demarcation from Related Work 5.8. Chapter Summary 6. Deriving Variants with Variability in Space and Time 6.1. Variant Derivation Cannot Handle Variability in Time 6.2. Associating Features and Feature Versions with Delta Modules 6.3. Automatically Select Versions to Ease Configuration 6.4. Application Order and Implicitly Required Delta Modules 6.4.1. Determining Relevant Delta Modules 6.4.2. Forming a Dependency Graph of Delta Modules 6.4.3. Performing a Topological Sorting of Delta Modules 6.5. Generating Variants with Versions of Variable Assets 6.6. Case Study 6.7. Demarcation from Related Work 6.8. Chapter Summary III. Realization and Application 7. Realization as Tool Suite DeltaEcore 7.1. Creating Delta Languages 7.1.1. Shared Base Metamodel 7.1.2. Common Base Delta Language 7.1.3. Delta Dialects 7.2. Specifying a Software Family with Variability in Space and Time 7.2.1. Hyper-Feature Models 7.2.2. Version-Aware Constraints 7.2.3. Delta Modules 7.2.4. Application-Order Constraints 7.2.5. Mapping Models 7.3. Deriving Variants 7.3.1. Creating a Configuration 7.3.2. Collecting Delta Modules 7.3.3. Ordering Delta Modules 7.3.4. Applying Delta Modules 8. Evaluation 8.1. Configurable TurtleBot Driver Software 8.1.1. Variability in Space 8.1.2. Variability in Time 8.1.3. Integrated Management of Variability in Space and Time 8.2. Metamodel Family for Role-Based Modeling and Programming Languages 8.2.1. Variability in Space 8.2.2. Variability in Time 8.2.3. Integrated Management of Variability in Space and Time 8.3. A Software Product Line of Feature Modeling Notations and Constraint Languages 8.3.1. Variability in Space 8.3.2. Variability in Time 8.3.3. Integrated Management of Variability in Space and Time 8.4. Results and Discussion 8.4.1. Results and Discussion of RQ1: Variability Model 8.4.2. Results and Discussion of RQ2: Variability Realization Mechanism 8.4.3. Results and Discussion of RQ3: Variant Derivation Procedure 9. Conclusion 9.1. Discussion 9.1.1. Supported Evolutionary Changes 9.1.2. Conceptual Representation of Variability in Time 9.1.3. Perception of Versions as Incremental 9.1.4. Version Numbering Schemes 9.1.5. Created Delta Languages 9.1.6. Scalability of Approach 9.2. Possible Future Application Areas 9.2.1. Extend to Full Software Ecosystem Feature Model 9.2.2. Model Software Ecosystems 9.2.3. Extract Hyper-Feature Model Versions and Record Delta Modules 9.2.4. Introduce Metaevolution Delta Modules 9.2.5. Support Incremental Reconfiguration 9.2.6. Apply for Evolution Analysis and Planning 9.2.7. Enable Evolution of Variable Safety-Critical Systems 9.3. Contribution 9.3.1. Individual Contributions 9.3.2. Handling Updater Stereotypes IV. Appendix A. Delta Operation Generation Algorithm B. Delta Dialects B.1. Delta Dialect for Java B.2. Delta Dialect for Eclipse Projects B.3. Delta Dialect for DocBook Markup B.4. Delta Dialect for Software Fault Trees B.5. Delta Dialect for Component Fault Diagrams B.6. Delta Dialect for Checklists B.7. Delta Dialect for the Goal Structuring Notation B.8. Delta Dialect for EMF Ecore B.9. Delta Dialect for EMFText Concrete Syntax Files