State of practice in requirements engineering: contemporary data

Kassab, Mohamad; Neill, Colin J.; Laplante, Phillip A.

doi:10.1007/s11334-014-0232-4

Cited by 71 publications

(43 citation statements)

References 5 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Natural language is the most adopted notation for requirements [32]. Unfortunately, text does not readily provide a holistic view of the involved entities and relationships.…”

Section: Discussionmentioning

confidence: 99%

“…The premise of our research is the high adoption yet low quality of user stories in industry [32,37,38]. To improve this situation, we focus on fostering deeper understanding of user stories by creating tool-assisted techniques that support practitioners in creating and communicating about high-quality user stories [36,39].…”

Section: Baseline: the Grimm Methodsmentioning

confidence: 99%

“…The Grimm method that we propose is our response to the low quality of user stories in industry [32,37,38], despite their popularity. Grimm features automated tools that improve the situation [37,39].…”

Section: The Grimm Method: Overview and Toolingmentioning

confidence: 99%

“…The software industry commonly uses natural language (NL) notations to express software requirements [47], with NL being employed by over 60% of practitioners [32]. With the increasing adoption of agile development practices such as Scrum, the semi-structured NL notation of user stories is gaining momentum [31,38].…”

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

Extracting conceptual models from user stories with Visual Narrator

et al. 2017

View full text Add to dashboard Cite

Extracting conceptual models from natural language requirements can help identify dependencies, redundancies, and conflicts between requirements via a holistic and easy-to-understand view that is generated from lengthy textual specifications. Unfortunately, existing approaches never gained traction in practice, because they either require substantial human involvement or they deliver too low accuracy. In this paper, we propose an automated approach called Visual Narrator based on natural language processing that extracts conceptual models from user story requirements. We choose this notation because of its popularity among (agile) practitioners and its focus on the essential components of a requirement: Who? What? Why? Coupled with a careful selection and tuning of heuristics, we show how Visual Narrator enables generating conceptual models from user stories with high accuracy. Visual Narrator is part of the holistic Grimm method for user story collaboration that ranges from elicitation to the interactive visualization and analysis of requirements.

show abstract

“…Natural language is the most adopted notation for requirements [32]. Unfortunately, text does not readily provide a holistic view of the involved entities and relationships.…”

Section: Discussionmentioning

confidence: 99%

Section: Baseline: the Grimm Methodsmentioning

confidence: 99%

Section: The Grimm Method: Overview and Toolingmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Extracting conceptual models from user stories with Visual Narrator

et al. 2017

View full text Add to dashboard Cite

show abstract

“…In this analysis we take into consideration also the answers given by people who partially completed the questionnaire for statistical analysis not requiring pairing or correlating information, as suggested in [11]. Given this population, responses to the survey are more likely to reflect the opinions and biases of any given projects development team rather than those of other groups represented in a software development effort.…”

Section: Profiles Of the Respondentsmentioning

confidence: 99%

Quality Attributes in Practice: Contemporary Data

Tumyrkin

Mazzara

Kassab

et al. 2016

Smart Innovation, Systems and Technologies

View full text Add to dashboard Cite

Abstract. It is well known that the software process in place impacts the quality of the resulting product. However, the specific way in which this effect occurs is still mostly unknown and reported through anecdotes. To gather a better understanding of such relationship, a very large survey has been conducted during the last year and has been completed by more than 100 software developers and engineers from 21 countries. We have used the percentage of satisfied customers estimated by the software developers and engineers as the main dependent variable. The results evidence some interesting patterns, like that quality attribute of which customers are more satisfied appears functionality, architectural styles may not have a significant influence on quality, agile methodologies might result in happier customers, larger companies and shorter projects seems to produce better products.

show abstract