2014
DOI: 10.1016/j.scico.2014.06.007
|View full text |Cite
|
Sign up to set email alerts
|

NAT2TESTSCR: Test case generation from natural language requirements based on SCR specifications

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
9
0
1

Year Published

2014
2014
2023
2023

Publication Types

Select...
4
3
2

Relationship

0
9

Authors

Journals

citations
Cited by 35 publications
(10 citation statements)
references
References 27 publications
0
9
0
1
Order By: Relevance
“…There are approaches generating functional system test cases from NL requirements [16], [17], [18], [19]. However, these approaches can be adopted in the context of security functional testing, but not security vulnerability testing since they generate test cases only for the intended behavior of the system.…”
Section: Related Workmentioning
confidence: 99%
“…There are approaches generating functional system test cases from NL requirements [16], [17], [18], [19]. However, these approaches can be adopted in the context of security functional testing, but not security vulnerability testing since they generate test cases only for the intended behavior of the system.…”
Section: Related Workmentioning
confidence: 99%
“…There are approaches that generate functional system test cases from NL requirements (e.g., [19], [20], [21], [22], [23]). For instance, Wang et al [21], [22] automatically generate functional test cases from use case specifications written in RUCM.…”
Section: Related Workmentioning
confidence: 99%
“…Unfortunately, engineers tend to avoid such models because of the costs related to their development and maintenance, especially in contexts where system requirements in Natural Language (NL) are already available. There are approaches that generate functional system test cases from NL requirements [19], [20], [21], [22], [23]. However, these approaches can be adopted in the context of security functional testing, but not security vulnerability testing since they generate test cases only for the intended behavior of the system.…”
Section: Introductionmentioning
confidence: 99%
“…However to support a model based approach to development these NL or CNL specifications would have to be converted into models. In [1], NL requirements specifications are first translated to CNL . Natural language processing techniques are then used to generate Software Cost Reduction (SCR) textual models for model based testing.…”
Section: Problem and Motivationmentioning
confidence: 99%