Search

The notion of software ecosystems has been popular both in research and industry for more than a decade, but how software ecosystems are created still remains unclear. This becomes more of a challenge if one examines the "creation'' of ecosystems that have high probability in surviving in the future, i.e. with respect to ecosystem health.In this paper, we focus on the creation of software ecosystems and proposea process for designing, developing, and establishing software ecosystemsbased on three basic steps and a set of activities for each step. We note that software ecosystem research identifies that ecosystems typically emerge from either a company deciding to allow development on their product platform or from a successful open source project. In our study we add to this knowledge by demonstrating, through two case studies, that ecosystems can emerge from more than a technological infrastructure (platform). We identify that ecosystems can emerge out of two more distinct types of environments and thus the design should be based on the characteristics of this categorization. Moreover, we follow the approach that design, development,and establishment are not three distinct phases but rather aspectsof a single re-iterating phase and thus propose the view of design, development,and establishment as a continous process, running in parallelwith and interrelated to the monitoring of the ecosystem evolution.

Making the right decisions is an essential part of software ecosystem governance. Decisions related to the governance of a software ecosystem can influence the health of the ecosystem and can result in fostering the success or greatly contributing to the failure of the ecosystem. However, very few studies touch upon the decision making of software ecosystem governance. In this paper, we propose decomposing software ecosystem governance into three activities: input or data collection, decision making, and applying actions.We focus on the decision making activity of software ecosystem governance and review related literature consisted of software ecosystem governance, organizational decision making, and IT governance. Based on the identified studies, we propose a framework for defining the decision making strategies in the governance of software ecosystems. We identify five decision areas for software ecosystem governance and four archetypes describing the way decisions are taken for each decision area. We explain this matrix-based framework by providing examples from existing software ecosystems.

In this position paper we propose means of measuring pro- gramming expertise on novice and expert programmers. Our approach is to measure the cognitive load of programmers while they assess Java/Python code in accordance with their experience in programming. Our hypothesis is that expert programmers encounter smaller pupillary dilation within pro- gramming problem solving tasks. We aim to evaluate our hypothesis using the EMIP Distributed Data Collection in order to confirm or reject our approach. QC20180129

This Master thesis focuses on the concept of Records Management (RM) and Electronic Records Management (ERM) and how the adoption of an Electronic Document Records Management System (EDRMS) affects a business setting. The research focuses on the factors of perceived efficiency and on the costs that exist in a company. More specifically, this Master thesis is a qualitative exploratory case study which's aim is to examine and present the experiences and the attitudes of 4 individuals who are working in companies that possess an EDRMS. In order to acquire this deeper understanding, the data collection methods that were used were the in person semi structured interviews and the observation. During the research was examined how the perceived efficiency and the costs in a company are affected by a proper RM/ERM program. The analysis of the collected data shown that the specific individuals in the specific firms are benefited by the EDRMS and that their work is improved.