Analyzing and Visualizing Projects and their Relations in Software Ecosystems

1. Analyzing and Visualizing Projects and
their Relations in Software Ecosystems
NIER/TD - Present at IEEE VISSOFT 2021
By Van Tuan Tran, Cheng Cheng, Fabio Petrillo and Yann-Gaël Guéhéneuc

2. Table of Contents
1. Introduction
2. Approach
3. Result

3. 1 - Introduction

4. 1 - Introduction - Problems
There are many software ecosystems:
● GitHub (all sorts of software)
● NPMJS (JavaScript libraries)
● Python Package Index (PyPI)
● Apache Maven Repository (Java libraries)
● Eclipse Foundation open source projects

5. 1 - Introduction - Problems
How to help developers understand, navigate between projects
in related/alternative ecosystems?
How to help developers understand, navigate
the Eclipse IoT ecosystem

6. 1 - Introduction - Goals
Goal 1: Summarize the documentation into word-cloud
KEYPLE
Several ‘Reader Observers’ could be registered to an Observable
Reader. In case of SE insertion / match / removal, the observable
reader notifies sequentially the registered observers with the
corresponding reader event. The observable reader could be a
blocking API, the thread managing the issuance of the plugin event
could wait the acknowledge of the notified observers.
An observable reader has the capability to be set with a ‘Default
Selections Request’: in this case when a SE is inserted in the
reader, the reader will try to operate the configured default
selections. If a selection successfully matches with the SE, instead
to simply notify the insertion of SE, the observable reader will
notify about a successful selection with a SE application.
If the notification mode is defined as ‘always’, then in case of SE
insertion, the observable reader will notify a SE matched reader
event in case of successful selection, or a simple SE inserted
reader event if not.
If the notification mode is defined as ‘matched only’, then in case
of SE insertion, simple SE inserted reader events are not notified.
When the processing of an inserted or matched SE is finished, a
reader observer must release the logical channel with the Secure
Element, in order to prepare the observable reader to detect the
removal of the SE.
Observable reader states
An observable reader is active only when at least one reader
observer is registered, and if the start of the detection has been
requested. When active, an observable read could switch between

7. 1 - Introduction - Goals
Goal 2: Find and map relationships between word-clouds
?

8. 2 - Approach

9. 2 - Approach
1 2 3 4

10. 2 - Approach - Step 1 - Data Collection
1 2 3 4

11. 2 - Approach - Step 2 - Generate wordcloud
1 2 3 4

12. 2 - Approach - Step 3 - Find relationships
1 2 3 4

13. 2 - Approach - Step 4 -
1 2 3 4

14. 3 - Result

15. 3 - Result
https://huntertran.github.io/seco-storms-maker/