This document describes the folder and script structure of the artifact accompanying the SPLC 2025 paper:
"Feedback analysis in software product line forked developments"
.
├── evaluation_01_data_source.py
├── evaluation_02_data_processing.py
├── evaluation_03_feedback_log.py
├── evaluation_04_analysis.py
├── evaluation_05_visuals.py
├── evaluation_06_heatmap_graph.py
│
├── feature_introduction_timeline.py
├── tag_evolution.py
├── top_n_features.py
│
├── proof_of_concept/
│ ├── proof_of_concept_01_data_source.py
│ ├── proof_of_concept_02_data_processing.py
│ ├── proof_of_concept_03_analysis.py
│ ├── proof_of_concept_04_charts.py
│
├── figures/ # Generated charts (.svg/.png)
├── feedback_log.json # Final aggregated result
├── forks.json # Input file with selected forks
├── requirements.txt
├── Dockerfile
├── docker-compose.yml
├── .env.example
├── README.md
└── structure.md # This fileevaluation_*.py: Full pipeline scripts for data extraction, tagging, analysis, and visualization.feature_*.py,tag_*.py, etc.: Complementary analysis tools.proof_of_concept/: Minimal end-to-end example with synthetic data.figures/: Output charts (automatically generated).feedback_log.json: Unified log with all extracted feedback entries.forks.json: The list of GitHub forks analyzed.
- Run
evaluation_01toevaluation_06for the full process. - Use
proof_of_concept/*.pyif you want to test without GitHub API access. - All outputs are saved to the working directory or inside
/figures.
See also: results_mapping.md for traceability between scripts and paper results.