Proceedings of the 31st IEEE/ACM International Conference on Automated Software Engineering 2016
DOI: 10.1145/2970276.2970295
|View full text |Cite
|
Sign up to set email alerts
|

An automated collaborative requirements engineering tool for better validation of requirements

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
6
0

Year Published

2016
2016
2024
2024

Publication Types

Select...
4
3

Relationship

0
7

Authors

Journals

citations
Cited by 18 publications
(8 citation statements)
references
References 6 publications
0
6
0
Order By: Relevance
“…By crowd [48,54,72], by textual data analysis [13,20,25,33,41,42,49,51,52,62,64,80,86,88,89], by prototyping [22], sentiment analysis [21,79], image and unstructured data analysis [21,73] 22…”
Section: Analysis and Validationmentioning
confidence: 99%
See 1 more Smart Citation
“…By crowd [48,54,72], by textual data analysis [13,20,25,33,41,42,49,51,52,62,64,80,86,88,89], by prototyping [22], sentiment analysis [21,79], image and unstructured data analysis [21,73] 22…”
Section: Analysis and Validationmentioning
confidence: 99%
“…Requirements validation is the process of making sure that requirements gathered are aligned with the stakeholder's actual needs and are correct, consist and testable. As shown in Table 1, quite a few papers acknowledge that requirements validation in CrowdRE is challenging [28,54,68,72,73]. Requirements Prioritization.…”
mentioning
confidence: 99%
“…The authors in [4] employed a methodology which prescribes how different stakeholder use the same set of requirements virtually and validate those requirements. The authors solved the problem of communication and collaboration between client and requirement engineer.…”
Section: Related Workmentioning
confidence: 99%
“…In the RE process, initially, all the requirements are written in natural language and subsequently the experts analyze these requirements and develop specifications [3], [4].…”
Section: Introductionmentioning
confidence: 99%
“…Olsson and Grundy [34] implemented an approach that creates models from requirements descriptions, UML-style use case models and black-box test plans, which are later used for change impact analysis. However, their approach lacks automation and does not consider natural language, but formal models only.…”
Section: Related Workmentioning
confidence: 99%