Show simple item record

dc.contributor.authorManikas, Konstantinos
dc.contributor.authorHämäläinen, Mervi
dc.contributor.authorTyrväinen, Pasi
dc.date.accessioned2017-04-04T08:40:50Z
dc.date.available2017-04-04T08:40:50Z
dc.date.issued2016
dc.identifier.citationManikas, K., Hämäläinen, M., & Tyrväinen, P. (2016). Designing, Developing, and Implementing Software Ecosystems: Towards a Step-wise Guide. In S. Jansen, C. Alves, & J. Bosch (Eds.), <em>IWSECO 2016 : Proceedings of the 8th International Workshop on Software Ecosystems</em> (pp. 70-79). CEUR Workshop Proceedings, 1808. Editors; Sun SITE Central Europe. Retrieved from <a href="http://ceur-ws.org/Vol-1808/IWSECO16-paper5-Manikas-p70-79.pdf">http://ceur-ws.org/Vol-1808/IWSECO16-paper5-Manikas-p70-79.pdf</a>
dc.identifier.otherTUTKAID_72245
dc.identifier.urihttps://jyx.jyu.fi/handle/123456789/53474
dc.description.abstractThe 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 propose a process for designing, developing, and establishing software ecosystems based 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 aspects of a single re-iterating phase and thus propose the view of design, development, and establishment as a continous process, running in parallel with and interrelated to the monitoring of the ecosystem evolution.
dc.format.extent94
dc.language.isoeng
dc.publisherEditors; Sun SITE Central Europe
dc.relation.ispartofIWSECO 2016 : Proceedings of the 8th International Workshop on Software Ecosystems
dc.relation.ispartofseriesCEUR Workshop Proceedings;1808
dc.relation.urihttp://ceur-ws.org/Vol-1808/IWSECO16-paper5-Manikas-p70-79.pdf
dc.subject.othersoftware ecosystems
dc.subject.othersoftware ecosystem design
dc.subject.othersoftware ecosystem health
dc.titleDesigning, Developing, and Implementing Software Ecosystems: Towards a Step-wise Guide
dc.typeconferenceObject
dc.identifier.urnURN:NBN:fi:jyu-201704031864
dc.contributor.laitosAgora Centerfi
dc.contributor.laitosTietojenkäsittelytieteiden laitosfi
dc.contributor.laitosAgora Centeren
dc.contributor.laitosDepartment of Computer Science and Information Systemsen
dc.contributor.oppiaineTietojärjestelmät
dc.type.urihttp://purl.org/eprint/type/ConferencePaper
dc.date.updated2017-04-03T09:15:07Z
dc.type.coarconference paper
dc.description.reviewstatuspeerReviewed
dc.format.pagerange70-79
dc.relation.issn1613-0073
dc.type.versionacceptedVersion
dc.rights.copyright© the Authors, 2016.
dc.rights.accesslevelopenAccessfi


Files in this item

Thumbnail

This item appears in the following Collection(s)

Show simple item record