Çorba: crowdsourcing to obtain requirements from regulations and breaches

Abstract

The version in the Kent Academic Repository may differ from the final published version. Users are advised to check http://kar.kent.ac.uk for the status of the paper. Users should always cite the published version of record.

Crowdsourced Requirements Engineering Challenges and Solutions: A Software Industry Perspective

“…This type of process is made possible with the continuance of the internet. Stakeholders are the crowd in the CS environment and thus software development relies on them to gather their needs properly [9]. This indicates that it is time to rethink requirements elicitation to handle the difficulty and scale of the crowd and certify that the requirements are gathered efficiently and precisely [9].…”

“…In essence, this reveals that the software development team encounters an extensive user audience, which is referred to as the crowd of people. It is important to involve the crowd to satisfy crowd requirements, which demonstrates the importance of crowdsourcing [9]. Involving an enormous number of users in requirements engineering (RE) has always been challenging with customary RE methods [10,11]; specifically, this is true when RE would include an enormous number of users (a crowd) who are beyond an organisation's reach [10,12].…”

“…CS-based RE is likely to enhance the quality, inclusiveness and even monetary viability of requirements elicitation. It allows software development teams to receive more updated knowledge about users' perceptions of the system's role to fulfil their requirements [9].…”

“…Although CS has noteworthy possibilities for RE, there remains scarce knowledge regarding how to setup a CS-based project to fit the RE task [9]. A study conducted by Ågerfalk et al [22] also specifies the importance of identifying various challenges that can be faced in SW CS.…”

Common Privacy Weaknesses and Vulnerabilities in Software Applications

“…A large number of existing studies have investigated methods to preserve and protect privacy in software development. Several studies have proposed approaches to derive privacy requirements from organisational goals (Kalloniatis et al, 2008), data protection and privacy regulations (Breaux and Antón, 2008;Mihaylov et al, 2016;Ayala-Rivera and Pasquale, 2018;Guo et al, 2020) or privacy policies (Omoronyia et al, 2012;Massey et al, 2013) to ensure that software systems comply with those restrictions and/or constraints. Tschersich et al (2011) and Yang et al (2016) presented frameworks for designing privacypreserving architecture in software development.…”