Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Ilyuza Gizzatullina

dblp:246/5356 · DBLP profile ↗
← Back
1ranked-venue papers
1as first author
0since 2021 · last 2019
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 1 · 1 first-author

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Software engineering, system software, and programming languages
1 paper
Empirical software engineering · 100%

Topics — the 2 heaviest of 3, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Empirical software engineering
developer studies
0.412019
Empirical study of customer communication problem in agile requirements engineering · ESEC/SIGSOFT FSE 2019
Empirical software engineering
systematic literature review
0.112019
Empirical study of customer communication problem in agile requirements engineering · ESEC/SIGSOFT FSE 2019

Methods — techniques the papers use, named apart from their topics

systematic literature review · 0.4semi-structured interviews · 0.4
YearPublicationVenuePosition
2019 Empirical study of customer communication problem in agile requirements engineering
abstract
As Agile principles and values become an integral part of the soft-ware development culture, development processes experience significant changes. Requirements engineering, an individual phase occurring at the beginning of the traditional development, is distributed between various activities according to agile. However, how customer communication related problems are solved within the context of agile requirements engineering (RE)? Empirical study of that problem is done using 2 methods: systematic literature review and semi-structured interviews. Problems related to customer communication in agile RE are revealed and composed into patterns. Patterns are to be supplemented with the solutions in the further research.
Ilyuza Gizzatullina
ESEC/SIGSOFT FSE1