2011 Model-Driven Requirements Engineering Workshop 2011
DOI: 10.1109/modre.2011.6045361
|View full text |Cite
|
Sign up to set email alerts
|

Interactive requirements validation for reactive systems through virtual requirements prototype

Abstract: -Adequate requirements validation can prevent errors from propagating into later development phases, and eventually improve the quality of software systems. However, validating natural language requirements is often difficult and error-prone. An effective means of requirements validation for embedded software systems has been to build a working model of the requirements in the form of a physical prototype that stakeholders can interact with. However, physical prototyping can be costly, and time consuming, exte… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
2
0

Year Published

2016
2016
2023
2023

Publication Types

Select...
3
3

Relationship

1
5

Authors

Journals

citations
Cited by 10 publications
(2 citation statements)
references
References 21 publications
0
2
0
Order By: Relevance
“…The objective is to minimize the amount of visual analysis that the user would need to perform by reducing his/her need to examine every path string when trying to assess results. To explicitly address states and transitions during the framing of questions, we have proposed a method of translating the requirements into a STD [27]. The method results in traceability between NL requirements and its STD model, which in turn enables any SQ derived from requirements, to use the same states and transitions which appear in the STD.…”
Section: Discussion Conclusion and Future Workmentioning
confidence: 99%
“…The objective is to minimize the amount of visual analysis that the user would need to perform by reducing his/her need to examine every path string when trying to assess results. To explicitly address states and transitions during the framing of questions, we have proposed a method of translating the requirements into a STD [27]. The method results in traceability between NL requirements and its STD model, which in turn enables any SQ derived from requirements, to use the same states and transitions which appear in the STD.…”
Section: Discussion Conclusion and Future Workmentioning
confidence: 99%
“…3) Requirements validation: Validating whether natural language requirements meet the needs of the stakeholders is often difficult and error-prone. Prototyping is an effective way for requirements validation [21]. However, the construction of prototypes is time consuming and costly.…”
Section: Integrating Into Requirements Engineeringmentioning
confidence: 99%