2020
DOI: 10.1007/978-3-030-49418-6_22
|View full text |Cite
|
Sign up to set email alerts
|

Can We Design Software as We Talk?

Abstract: In the context of digital transformation, speeding up the time-to-market of high-quality software products is a big challenge. Main challenges. Software quality correlates with the success of requirements engineering (RE) sessions. RE sessions demand software analysts to collect all relevant material usually specified on written notes, flip charts, pictures, etc. Afterwards comprehensible requirements need to be specified for software implementation and testing. These activities are mostly performed manually, … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1

Citation Types

0
3
0

Year Published

2020
2020
2020
2020

Publication Types

Select...
1

Relationship

1
0

Authors

Journals

citations
Cited by 1 publication
(3 citation statements)
references
References 14 publications
0
3
0
Order By: Relevance
“…To classify transcripts and user reviews these two components leverage deep learning (unsupervised) and machine learning (supervised) strategies, respectively. To train the DL and ML models, these two components extract and pre-process text data from the original datasets of previous work concerning requirements analysis of transcripts [1] and user reviews feedback [2], [3]. Hence, they classify functional and non-functional requirements discussed during requirements elicitation sessions by leveraging machine learning or deep learning strategies.…”
Section: Designing a Requirements Collector Toolmentioning
confidence: 99%
See 2 more Smart Citations
“…To classify transcripts and user reviews these two components leverage deep learning (unsupervised) and machine learning (supervised) strategies, respectively. To train the DL and ML models, these two components extract and pre-process text data from the original datasets of previous work concerning requirements analysis of transcripts [1] and user reviews feedback [2], [3]. Hence, they classify functional and non-functional requirements discussed during requirements elicitation sessions by leveraging machine learning or deep learning strategies.…”
Section: Designing a Requirements Collector Toolmentioning
confidence: 99%
“…Both components are available on our GitHub repositories 3 4 . Important, we experimented the usage of the two components on the dataset available from previous work, concerning the classification of requirements discussed in RE meetings (stored in form of audio recordings) and textual user review feedback [1], [2], [3].…”
Section: Interaction Potentialmentioning
confidence: 99%
See 1 more Smart Citation