The paper “Software Engineering Applications Enabled by Blockchain Technology: A Systematic Mapping Study” provides a comprehensive overview of how blockchain technology can be integrated into software engineering (SE) practices. While the authors present a thorough examination of the potential benefits, several flaws and limitations undermine the study’s impact and practical application. Here, we critique the key areas where the paper falls short and suggest improvements for future research.
Overemphasis on Theoretical Potential
The paper primarily discusses the theoretical benefits of blockchain in SE without providing substantial empirical evidence. For example, it mentions blockchain’s potential to replace centralized systems like GitHub and Travis CI, yet no real-world implementations or case studies support these claims. The authors’ reliance on hypothetical scenarios and proposed models without practical validation weakens the study’s overall credibility.
Lack of Detailed Technical Analysis
The paper offers a broad overview of blockchain applications in SE but lacks a detailed technical analysis of the challenges and limitations. For instance, while the study acknowledges the security concerns related to GitHub/Travis CI, it fails to delve into the technical challenges of implementing a decentralized alternative. The absence of a rigorous technical examination of blockchain integration leaves many questions about feasibility and scalability unanswered.
Insufficient Exploration of Consensus Mechanisms
One significant flaw is the limited discussion on consensus mechanisms, which are crucial for the functioning of blockchain systems. The study briefly mentions two proposed consensus mechanisms (Yilmaz et al.’s approach and Proof of Skill by Wang et al.). Still, it does not provide in-depth analysis or comparison with existing mechanisms. Understanding the implications of different consensus algorithms on SE practices is vital for assessing blockchain’s practicality in this domain.
Neglect of Performance and Efficiency Issues
The paper overlooks the performance and efficiency issues associated with blockchain technology. Blockchain’s inherent characteristics, such as high computational costs and latency, are critical factors that can hinder its adoption in SE. The study does not adequately address these challenges nor propose solutions to mitigate them. This omission raises concerns about the real-world applicability of blockchain in large-scale SE projects.
Limited Scope of Empirical Evidence
The empirical evidence presented in the study is scant and primarily based on a small number of interviews and theoretical proposals. For example, the evaluation study by Akbar et al. involved only five interviews with industry practitioners, which is insufficient to draw broad conclusions. To substantiate its claims, the study would benefit from a more extensive empirical investigation, including pilot projects and real-world case studies.
Conclusion
While the paper provides a valuable starting point for exploring blockchain applications in software engineering, it falls short in several critical areas. The over-reliance on theoretical potential, lack of detailed technical analysis, insufficient exploration of consensus mechanisms, neglect of performance issues, and limited empirical evidence undermine the study’s practical relevance. Future research should address these gaps through rigorous technical analysis, comprehensive empirical studies, and real-world implementations to provide a more balanced and actionable understanding of blockchain’s role in software engineering.