This is an unedited manuscript accepted for publication and provided as an Article in Press for early access at the author’s request. The article will undergo copyediting, typesetting, and galley proof review before final publication. Please be aware that errors may be identified during production that could affect the content. All legal disclaimers of the journal apply.
Manas Kumar Yogi,
- Assistant Professor, CSE Department, Pragati Engineering College (A), Surampalem, Andhra Pradesh, India
Abstract
The crowd-based software production model has emerged as a transformative paradigm, leveraging global collaboration, decentralized governance, and artificial intelligence (AI)-driven automation to develop software efficiently. Traditional software development models, characterized by centralized control and in-house teams, are increasingly giving way to distributed, community-driven efforts. Key advancements such as blockchain-based decentralized autonomous organizations (DAOs), AI-assisted coding and debugging, and edge computing applications are reshaping the landscape of software engineering. DAOs provide transparent governance and fair compensation, ensuring equitable participation in open-source development. AI-powered tools enhance code synthesis, bug detection, and testing automation, significantly improving productivity and quality assurance. Additionally, crowd-driven internet of things (IoT) and edge computing software development fosters real-time adaptability and security enhancements. However, these advancements introduce challenges, including intellectual property (IP) concerns, security risks, and coordination complexities in large-scale collaborations. Emerging governance models that integrate reputation-based incentives, smart contracts, and hybrid voting mechanisms aim to streamline contributor engagement and sustain long- term project development. This paper reviews recent trends, technological innovations, and governance models in crowd-based software engineering, highlighting its growing impact on modern software ecosystems. By integrating AI, blockchain, and decentralized governance, the crowd-based software model is evolving into a scalable, secure, and self-sustaining ecosystem, driving the future of software engineering.
Keywords: Crowd source, open source, decentralized governance, Agile, DevOps
[This article belongs to Journal of Software Engineering Tools & Technology Trends ]
Manas Kumar Yogi. Swarm Intelligence in Software Engineering: A Systematic Review of Crowd-Based Development Models. Journal of Software Engineering Tools & Technology Trends. 2025; 12(02):01-11.
Manas Kumar Yogi. Swarm Intelligence in Software Engineering: A Systematic Review of Crowd-Based Development Models. Journal of Software Engineering Tools & Technology Trends. 2025; 12(02):01-11. Available from: https://journals.stmjournals.com/josettt/article=2025/view=207271
References
- Mao K, Capra L, Marman M, Jia Y. A survey of the use of crowdsourcing in software engineering. J Syst Softw. 2017; 126: 57–84.
- Stol K-J, Fitzgerald B. Two’s company, three’s a crowd: a case study of crowdsourcing software development. In: Proceedings of the 36th International Conference on Software Engineering, Hyderabad, India, May 31–June 7, 2014. pp. 187–198.
- Brabham DC. Crowdsourcing. Cambridge, MA, USA: MIT Press; 2013.
- Howe J. The rise of crowdsourcing. Wired Mag. 2006; 14 (6).
- Ågerfalk PJ, Fitzgerald B, Stol KJ. Software Sourcing in the Age of Open. Cham, Switzerland: Springer; 2015.
- Begel A, Bosch J, Storey MI. Social networking meets software development: perspectives from Github, MSDN, Stack Exchange, and Topcoder. IEEE Softw. 2013; 30 (1): 52–66.
- Tamburri P, Vliet H. Organizational social structures for software engineering. ACM Comput. Surv. 2013; 46 (1): 1–35.
- Storey MA, Singer L, Filho FF, Zagalsky A, German DM. How social and communication channels shape and challenge a participatory culture in software development. IEEE Trans Softw Eng. 2015; 41 (7): 185–204.
- Hosseini M, Phalp K, Taylor J, Ali R. Towards crowdsourcing for requirements engineering. In: The 20th International Working Conference on Requirements Engineering: Foundation for Software Quality (REFSQ 2014) – Empirical Track, Essen, Germany, April 7–14, 2014.
- Schenk E, Guittard C. Towards a characterization of crowdsourcing practices. J Innov Econ Manage. 2011; 1: 93–107.
- Vander Schee BA. Crowdsourcing: why the power of the crowd is driving the future of business. J Consum Market. 2009; 26 (4): 305–306.
- Alamer G, Alyahya S, Al-Dossari H. Crowdsourcing requirements engineering: a taxonomy-based review. Int J Adv Computer Sci Appl. 2024; 15 (4): 608–615.
- Wang Y, et al. Spatiotemporal crowdsourcing for domain knowledge inference in requirements elicitation. IEEE Trans Softw Eng. 2022; 48 (11): 4175–4191.
- Lakhani KR, et al. Boosting innovation through crowdsourcing. Harvard Business Rev. 2010; 88 (10): 50–58.
- LaToza TD, et al. Maintaining knowledge in software teams: a theory of information fragmentation. Proceedings of the 35th International Conference on Software Engineering, San Francisco, CA, USA, May 18–26, 2013. pp. 832–841.
- Cooper S, et al. Predicting performance of protein design algorithms with an EteRNA crowdsourcing game. Proceedings of the 17th International Conference on Intelligent Systems for Molecular Biology (ISMB) and 8th European Conference on Computational Biology (ECCB), Stockholm, Sweden, June 29–July 2, 2009. Vol. 26.
- Norman DA, et al. When good design goes bad. Interactions. 2011; 18 (4): 24–28.
- Chatfield AT, Brawidagda FB. Crowdsourcing government: crowdsourcing as a mechanism to enhance government transparency and responsiveness. Information Polity. 2014; 19 (1–2): 123– 140.
- Alonso E, et al. Crowdsourcing for software testing. In: Proceedings of the 2008 International Workshop on Social Development Environments and Infrastructure, 2008. pp. 81–88.

Journal of Software Engineering Tools & Technology Trends
| Volume | 12 |
| Issue | 02 |
| Received | 26/02/2025 |
| Accepted | 06/03/2025 |
| Published | 15/04/2025 |
| Publication Time | 48 Days |
Login
PlumX Metrics