KPIs for Software Ecosystems: A Systematic Mapping Study

Fotrousi, Farnaz; Fricker, Samuel; Fiedler, Markus; Gall, Franck Le

doi:10.1007/978-3-319-08738-2_14

Cited by 23 publications

(14 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…It analyses the types of solutions to improve software ecosystems. [30] It analyses the Key Performance Indicators (KPI). It identifies the goals of software ecosystems in which the KPI are applied.…”

Section: Discussionmentioning

confidence: 99%

“…Finally, there are 5 studies that go in depth in a particular characteristic or technique related to software ecosystems: 1 paper about requirements engineering [28]; 1 paper that analyses the governance mechanisms in SECO [24]; 1 paper focused on key performance indicators (KPIs) [30]; 1 paper about "ecosystem health" which refers to a set of key indicators of well-being, longevity and performance of a SECO [32]; and 1 paper about how to document or describe SECOs [25].…”

Section: P O S Tmentioning

confidence: 99%

See 1 more Smart Citation

Mapping the systematic literature studies about software ecosystems

García‐Holgado

García-Peñalvo

2018

Proceedings of the Sixth International Conference on Technological Ecosystems for Enhancing Multiculturality

View full text Add to dashboard Cite

There is a need to improve the definition and development of technological ecosystems in order to solve the main problems detected in previous studies. To achieve this goal, it is required to identify and analyse the solutions available in the literature in the field of software engineering applied to ecosystems. The research in software ecosystems is a relatively young research area, but there are already several works that analyse the literature associated. To conduct a new systematic literature review is necessary to ensure that there are no studies that do the same, namely, that do not answer the same research questions. The identification of the need for a review was done through a study focused on systematic literature reviews and mapping studies about software ecosystems. This work aims to describe the mapping conducted as part of that study. It provides a global state of the art of this kind of studies in the area of software ecosystems. CCS CONCEPTS • Information systems • Software and its engineering → Software creation and management • Software and its engineering → Ultra-large-scale systems

show abstract

Section: Discussionmentioning

confidence: 99%

Section: P O S Tmentioning

confidence: 99%

Mapping the systematic literature studies about software ecosystems

García‐Holgado

García-Peñalvo

2018

Proceedings of the Sixth International Conference on Technological Ecosystems for Enhancing Multiculturality

View full text Add to dashboard Cite

show abstract

“…Thus, what are such mechanisms that a firm should use to evaluate the access and availability of above "resources and information". Thirdly, it has been considered that an ecosystem should be responsible for its participants: "SECO platform ownership also brings responsibilities" [50]. This question is not clear even network literature and practice -when a network's focal company faces financial problems, its loyalty towards its suppliers has been deteriorating in many cases.…”

Section: Discussionmentioning

confidence: 99%

“…Yes [50] To be able to create value, a keystone's responsibility is to ensure a healthy and sustainable ecosystem. Follows [7] in an view of ecosystem health.…”

Section: Nomentioning

confidence: 99%

Wealthy, Healthy and/or Happy — What does ‘Ecosystem Health’ Stand for?

Hyrynsalmi

Seppänen

Nokkala

et al. 2015

Lecture Notes in Business Information Processing

View full text Add to dashboard Cite

Abstract. The health of a software ecosystem is argued to be a key indicator of well-being, longevity and performance of a network of companies. In this paper, we address what scientific literature actually means with the concept of 'ecosystem health' by selecting relevant articles with systematic literature review. Based on the final set of 38 papers, we found that despite a common base, the term has been used to depict a wide range of hoped characteristics of a software ecosystem. However, the number of studies addressing the topic is shown to grow while empirical studies are still rare. Thus, further studies should aim to standardize the terminology and concepts in order to create a common base for future work. Further work is needed also to develop early indicators that warn and guides companies on problems with their ecosystems.

show abstract

“…Many scholars have intended to address the health of an ecosystem either as a whole or from a specific perspective. In this context, Fotrousi et al [4] review the literature to identify key performance indicators used to assess the health of an ecosystem. Jansen [9] examines open source software ecosystems and proposes an "operationalization" of open source ecosystem health.…”

Section: Background and Related Workmentioning

confidence: 99%

Characterizing Software Activity

Manikas

Kontogiorgos

2015

Proceedings of the 2015 European Conference on Software Architecture Workshops

View full text Add to dashboard Cite

The health of a software ecosystem reflects the ability of the ecosystem to endure and remain variable and productive over time. Measurements of health in a software ecosystem are applied to inform on how the ecosystem is evolving, evaluate changes, and predict future states. In this study we investigate the influence of software to the overall health of the ecosystem. We propose an approach of measuring the activity of the ecosystem over time and identifying the influence to health. We do this in two ways: (i) we study the evolution of the software network over time to identify changes in the structure of the software network and investigate whether they relate to general changes in the ecosystem. (ii) We propose the identification of the influence of the independent software components to ecosystem health at an activity level. We do so by defining keystone and dominator activities and propose tentative means of measuring them. We apply our proposed approach to the platform of the Apache Cordova ecosystem, an ecosystem with a community-based platform and independent contributions. Our analysis identifies two points in time where the ecosystem is under major change. These points are confirmed independently by both the measures of software network and keystone and dominator activities.

show abstract

KPIs for Software Ecosystems: A Systematic Mapping Study

Cited by 23 publications

References 9 publications

Mapping the systematic literature studies about software ecosystems

Mapping the systematic literature studies about software ecosystems

Wealthy, Healthy and/or Happy — What does ‘Ecosystem Health’ Stand for?

Characterizing Software Activity

Contact Info

Product

Resources

About