Crowdsourcing as a tool to elicit software requirements

Sari, Dyah Ayu Permata; Putri, Araeyya Yenofa; Hanggareni, Manis; Anjani, Annisa; Siswondo, M. Luthfan Oktaviano; Raharjana, Indra Kharisma

doi:10.1063/5.0042134

Cited by 6 publications

(4 citation statements)

References 15 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Whereas c(i, j) is the distance value between words vector (x i dan x j ) from each document obtained from (5). Once the cumulative minimum weight value is obtained, the semantic likeness value between documents is obtained using (6).…”

Section: F Extracting Of Semantic Related Termmentioning

confidence: 99%

See 1 more Smart Citation

Extracting software requirements-related information from online news using DomText-WMDS

Dewi,

Raharjana,

Siahaan

et al. 2023

J.INFOTEL

View full text Add to dashboard Cite

Currently, there are not many studies that assess software requirements extraction from non-software artifacts. Most of the research in these related areas are focuses on software artifacts such as project descriptions or user reviews as a source of requirements extraction. This research aims to identify relevant information to the software requirements from online news using the vector space model. This software requirements-related information can assist systems analysts in discovering the problem domain based on the lesson learned presented by stakeholders in online news. This research proposes DomText-WMDS to extract requirements-related information from online news. We used online news and public software requirements specification dataset to develop software-specific vocabulary using domain specificity technique. Then we expanded the specific vocabulary software to obtain more comprehensive results by building vector space model from online news documents. This updated version of software-specific vocabulary can be used for basic filtering of software requirements-related information that previously extracted using the part-of-speech (POS) chunking. This study improved the performance for extracting software requirements-related information, with precision and recall 61.09% and 60.66% compared to domain specificity approach that only manages to obtain 43.34% and 40.78%.

show abstract

Section: F Extracting Of Semantic Related Termmentioning

confidence: 99%

“…Some of the terminal expansion results that are semantically related are shown in Table 2. The similarity scores between software-specific vocabulary and terms extracted from online news were obtained from the WMDS function in (6). This score explained how closely the meanings of the two terms were semantically related.…”

Section: B Semantic Related Termmentioning

confidence: 99%

Extracting software requirements-related information from online news using DomText-WMDS

Dewi,

Raharjana,

Siahaan

et al. 2023

J.INFOTEL

View full text Add to dashboard Cite

show abstract

“…It is widely recognized among researchers and industry practitioners that software projects are very prone to failure when the requirements elicitation process is not carried out properly [7,8]. In the software development life cycle (SDLC), this undertaking is challenging because it involves socio-technical characteristics and changing requirements [9,10], and because there may be problems of ambiguity and tacit knowledge transfer [11,12]. Such problems, if found too late, can lead to high rework costs because they necessitate modifications in other processes [4,13].…”

Section: Introductionmentioning

confidence: 99%

Enhancing Software Feature Extraction Results Using Sentiment Analysis to Aid Requirements Reuse

et al. 2021

Self Cite

View full text Add to dashboard Cite

Recently, feature extraction from user reviews has been used for requirements reuse to improve the software development process. However, research has yet to use sentiment analysis in the extraction for it to be well understood. The aim of this study is to improve software feature extraction results by using sentiment analysis. Our study’s novelty focuses on the correlation between feature extraction from user reviews and results of sentiment analysis for requirement reuse. This study can inform system analysis in the requirements elicitation process. Our proposal uses user reviews for the software feature extraction and incorporates sentiment analysis and similarity measures in the process. Experimental results show that the extracted features used to expand existing requirements may come from positive and negative sentiments. However, extracted features with positive sentiment overall have better values than negative sentiments, namely 90% compared to 63% for the relevance value, 74–47% for prompting new features, and 55–26% for verbatim reuse as new requirements.

show abstract

“…Incomplete requirements can significantly impact the escalation of maintenance costs and development efforts [11]. To achieve effective elicitation results, software projects typically need to engage numerous stakeholders [12], [13], [14], [15]. Experts possessing domain and software knowledge are crucial in generating high-quality requirements [7].…”

mentioning

confidence: 99%

Analyzing Variances in User Story Characteristics: A Comparative Study of Stakeholders with Diverse Domain and Technical Knowledge in Software Requirements Elicitation

Trisnawati,

Raharjana,

Taufik

et al. 2024

J. Inf. Syst. Eng. Bus. Intell.

View full text Add to dashboard Cite

Background: In Agile software development, an essential initial stage is eliciting software requirements. This process engages stakeholders to achieve comprehensive results. However, a common issue is the variance in domain and technical knowledge among stakeholders, potentially impacting the quality of software requirements elicitation. Objective: Understanding the characteristics of user stories produced by stakeholders becomes crucial, particularly considering the differences in domain and technical knowledge. This study aims to compare the characteristics of user stories generated by stakeholders with varying backgrounds in domain and technical expertise. Methods: The initial step involves categorizing respondents into distinct stakeholder groups. Three stakeholders are involved in this study, constituting a combination of those with high and low technical and domain knowledge. Subsequently, data collection of user stories is conducted across various case studies. Finally, the acquired user stories are analyzed for further insights. Results: The analysis reveals variations in user stories generated by the three stakeholder categories across the three case studies. Stakeholders with domain knowledge tend to focus on 'what' aspects with task elements and 'why' aspects with hard-goal elements. Meanwhile, technical knowledge crafts user stories with capability elements in the 'what' aspect. Utilizing the QUS framework, it is evident that technical knowledge consistently produces a higher number of high-quality user stories across all quality categories, Conclusion: The contribution offered by this study lies in determining the distinct characteristics of user stories produced by different types of stakeholders, focusing on disparities in domain and technical knowledge. The study highlights the comparison of various characteristics of user story elements, such as hard-goals, soft-goals, tasks, or capabilities, and assesses the quality of user stories based on the user story framework. Additionally, it endorse the importance of process innovation in shaping the requirements gathering process and subsequently influencing the quality of user stories. Keywords: User story, Agile Software Development, Requirements Elicitation, Stakeholder, Domain Knowledge, Process Innovation Background: In Agile software development, an essential initial stage is eliciting software requirements. This process engages stakeholders to achieve comprehensive results. However, a common issue is the variance in domain and technical knowledge among stakeholders, potentially impacting the quality of software requirements elicitation. Objective: Understanding the characteristics of user stories produced by stakeholders becomes crucial, particularly considering the differences in domain and technical knowledge. This study aims to compare the characteristics of user stories generated by stakeholders with varying backgrounds in domain and technical expertise. Methods: The initial step involves categorizing respondents into distinct stakeholder groups. Three stakeholders are involved in this study, constituting a combination of those with high and low technical and domain knowledge. Subsequently, data collection of user stories is conducted across various case studies. Finally, the acquired user stories are analyzed for further insights. Results: The analysis reveals variations in user stories generated by the three stakeholder categories across the three case studies. Stakeholders with domain knowledge tend to focus on 'what' aspects with task elements and 'why' aspects with hard-goal elements. Meanwhile, technical knowledge crafts user stories with capability elements in the 'what' aspect. Utilizing the QUS framework, it is evident that technical knowledge consistently produces a higher number of high-quality user stories across all quality categories, Conclusion: The contribution offered by this study lies in determining the distinct characteristics of user stories produced by different types of stakeholders, focusing on disparities in domain and technical knowledge. The study highlights the comparison of various characteristics of user story elements, such as hard-goals, soft-goals, tasks, or capabilities, and assesses the quality of user stories based on the user story framework. Additionally, it endorse the importance of process innovation in shaping the requirements gathering process and subsequently influencing the quality of user stories. Keywords: User story, Agile Software Development, Requirements Elicitation, Stakeholder, Domain Knowledge, Process Innovation

show abstract

Crowdsourcing as a tool to elicit software requirements

Cited by 6 publications

References 15 publications

Extracting software requirements-related information from online news using DomText-WMDS

Extracting software requirements-related information from online news using DomText-WMDS

Enhancing Software Feature Extraction Results Using Sentiment Analysis to Aid Requirements Reuse

Analyzing Variances in User Story Characteristics: A Comparative Study of Stakeholders with Diverse Domain and Technical Knowledge in Software Requirements Elicitation

Contact Info

Product

Resources

About