Designing, developing, and implementing software ecosystems: towards a step-wise guide
Research output: Chapter in Book/Report/Conference proceeding › Article in proceedings › Research › peer-review
Standard
Designing, developing, and implementing software ecosystems : towards a step-wise guide. / Manikas, Konstantinos; Hämäläinen, Mervi; Tyrväinen, Pasi.
Proceedings of the 8th Workshop on Software Ecosystems. ed. / Slinger Jansen; Carina Alves; Jan Bosch. CEUR-WS.org, 2017. p. 70-79 (CEUR Workshop Proceedings).Research output: Chapter in Book/Report/Conference proceeding › Article in proceedings › Research › peer-review
Harvard
APA
Vancouver
Author
Bibtex
}
RIS
TY - GEN
T1 - Designing, developing, and implementing software ecosystems
T2 - 8th International Workshop on Software Ecosystems
AU - Manikas, Konstantinos
AU - Hämäläinen, Mervi
AU - Tyrväinen, Pasi
N1 - Conference code: 8
PY - 2017
Y1 - 2017
N2 - 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.
AB - 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.
M3 - Article in proceedings
T3 - CEUR Workshop Proceedings
SP - 70
EP - 79
BT - Proceedings of the 8th Workshop on Software Ecosystems
A2 - Jansen, Slinger
A2 - Alves, Carina
A2 - Bosch, Jan
PB - CEUR-WS.org
Y2 - 10 December 2016 through 10 December 2016
ER -
ID: 172021643