SECONDA: Software Ecosystem Analysis Dashboard

Pérez, Javier; Deshayes, Romuald; Goeminne, Mathieu; Mens, Tom

doi:10.1109/csmr.2012.69

Cited by 16 publications

(8 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…For example, Neu et al [4] developed Complicity, a web-based application aiming to support software ecosystem analysis through interactive visualisations. Perez et al [5] presented SECONDA, a software ecosystem analysis dashboard. The goal of maintaineR is similar in spirit, namely to provide a webbased dashboard for analysing and understanding the CRAN ecosystem and the packages it contains.…”

Section: Related Work and Existing Toolsmentioning

confidence: 99%

maintaineR: A Web-Based Dashboard for Maintainers of CRAN Packages

Claes

Mens

Grosjean

2014

2014 IEEE International Conference on Software Maintenance and Evolution

Self Cite

View full text Add to dashboard Cite

The R development community maintains thousands of packages through its Comprehensive R Archive Network CRAN. The growth and evolution of this archive makes it more and more difficult to maintain packages and their interdependencies, and the existing tools that aim to help developers in this process no longer suffice. We propose maintaineR, a web-based dashboard that allows CRAN package developers to understand and deal with the implications and problems raised by package updates. The dashboard complements existing analysis tools by providing additional support such as the visualisation of package dependencies and reverse dependencies, package conflicts, crosspackage function clones, and so on.

show abstract

Section: Related Work and Existing Toolsmentioning

confidence: 99%

maintaineR: A Web-Based Dashboard for Maintainers of CRAN Packages

Claes

Mens

Grosjean

2014

2014 IEEE International Conference on Software Maintenance and Evolution

Self Cite

View full text Add to dashboard Cite

show abstract

“…In parallel to the previous monitoring activities, the ESB forwards the service request to the Software management tool, who may have been wrapped if it is not providing a service itself (Req 1) (4). The service invokes the software management tool (5), and receives the response (6). The response is sent through the ESB 7to the initiator of the request, either the Invoker or the OSS community (8).…”

Section: B Monitoring Processmentioning

confidence: 99%

“…OSS ecosystem health operationalization, using the data from collections of open source projects that belong to the ecosystem, is provided by Jansen in [5]. Perez et al studied the correlation between OSS community health and software quality [6]. Abreu and Premraj showed a statistically significant correlation between communication frequency and number of injected bugs in the software [7].…”

Section: Introductionmentioning

confidence: 99%

Assessing open source communities' health using Service Oriented Computing concepts

Oriol

Franco-Bedoya

Franch

et al. 2014

2014 IEEE Eighth International Conference on Research Challenges in Information Science (RCIS)

View full text Add to dashboard Cite

The quality of Open Source Software products is directly related to its community's health. To date, health analysis is made accessing available data repositories or using software management tools that are often too static or ad hoc. To address this issue, we propose to adopt principles and methods from the Service Oriented Computing field. Particularly, we propose to adapt the concepts of quality service and service level agreement, and propose to reuse the existing body of knowledge and techniques from SOC monitoring. To demonstrate the feasibility of the approach, we use a service monitoring framework called SALMonOSS as a proof of concept to realize the implementation of the proposal.Peer ReviewedPostprint (published version

show abstract

“…No [33] Health of a project is related to health of an ecosystem; i.e., the quality of a project affects health of ecosystem and vice versa. [27] The paper focuses on the open-source software ecosystem and it notes that project health is not same than the 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

SECONDA: Software Ecosystem Analysis Dashboard

Cited by 16 publications

References 4 publications

maintaineR: A Web-Based Dashboard for Maintainers of CRAN Packages

maintaineR: A Web-Based Dashboard for Maintainers of CRAN Packages

Assessing open source communities' health using Service Oriented Computing concepts

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

Contact Info

Product

Resources

About