MétaCan
Menu
Back to cohort
Record W2577238692 · doi:10.1109/rew.2016.061

What are Practitioners Asking about Requirements Engineering? An Exploratory Analysis of Social Q&A Sites

2016· article· en· W2577238692 on OpenAlexafffund
Zahra Shakeri Hossein Abad, Shymka Alex, Pant Susant, Currie Ashley, Guenther Ruhe

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicSoftware Engineering Techniques and Practices
Canadian institutionsUniversity of Calgary
FundersNatural Sciences and Engineering Research Council of Canada
KeywordsRequirements engineeringComputer scienceLatent Dirichlet allocationRequirements analysisRequirements elicitationRequirementSoftware requirementsProduct (mathematics)Quality (philosophy)Ask priceIdentification (biology)Process (computing)SoftwareKnowledge managementSoftware engineeringData scienceSoftware developmentTopic modelComponent-based software engineering

Abstract

fetched live from OpenAlex

Requirements Engineering (RE) and all its underlying activities, such as requirements identification, evolution, validation, communication, and management, are still the key factors in successful product development. Therefore, proper implementation of this process is necessary to obtain a quality product. A better understanding of the most challenging RE-related topics for practitioners will greatly help to identify the areas of RE that may require extra attention by researchers and project managers. However, there has been very little experimental work towards identifying a practitioner's needs on the implementation and understanding of RE activities and tasks. Therefore, in this paper, we use data from popular social Q&A sites (i.e. Stack Overflow, Programmers Stack Exchange, Project Management Stack Exchange, and Quora), and analyze 4,553 questions and answers to examine what requirements engineers' needs are and what they ask about. To this end, we applied Latent Dirichlet Allocation-based (LDA) topic models and statistical analysis to explore the main related topics to RE. Our findings show that software practitioners are asking about requirements communication, evolution, validation, and modelling. Furthermore, we determined common RE challenges and issues, identified the main types of questions practitioners ask (i.e. what, how, why, when, where, and RE domain), and categorized these questions based on various aspects of software products (e.g. functionality, quality, and release planning). Our findings help highlight the challenges facing requirements engineers that require more attention from the software engineering - specifically requirements and product engineering - research communities in the future and establish a novel approach for analyzing the content of social Q&A websites.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

How this classification was reachedexpand

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Bench or experimental · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.809
Threshold uncertainty score0.392

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0000.000
Scholarly communication0.0000.005
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.051
GPT teacher head0.316
Teacher spread0.265 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it

Classification

machine, unvalidated

Machine predicted; a candidate call from one teacher head, not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designBench or experimental
Domainnot available
GenreMethods

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations13
Published2016
Admission routes2
Has abstractyes

Explore more

Same topicSoftware Engineering Techniques and PracticesFrench-language works237,207