This paper discusses a model-based approach to validate software requirements in agile development processes
by simulation and in particular automated testing. The use of models as central development artifact needs to be added to the
portfolio of software engineering techniques, to further increase efficiency and flexibility of the development beginning
already early in the requirements definition phase. Testing requirements are some of the most important techniques to give
feedback and to increase the quality of the result. Therefore testing of artifacts should be introduced as early as possible,
even in the requirements definition phase.
%0 Journal Article
%1 botas04b
%A Botaschanjan, J.
%A Pister, M.
%A Rumpe, B.
%D 2004
%E Wu, Xiufang
%J Journal of Zhejiang University SCIENCE
%K agile requirements
%N 5
%P 587--593
%T Testing Agile Requirements Models
%U http://www4.in.tum.de/~botascha/doc/Hangzhou.ReqTestingFinal.pdf
%V 5
%X This paper discusses a model-based approach to validate software requirements in agile development processes
by simulation and in particular automated testing. The use of models as central development artifact needs to be added to the
portfolio of software engineering techniques, to further increase efficiency and flexibility of the development beginning
already early in the requirements definition phase. Testing requirements are some of the most important techniques to give
feedback and to increase the quality of the result. Therefore testing of artifacts should be introduced as early as possible,
even in the requirements definition phase.
@article{botas04b,
abstract = {This paper discusses a model-based approach to validate software requirements in agile development processes
by simulation and in particular automated testing. The use of models as central development artifact needs to be added to the
portfolio of software engineering techniques, to further increase efficiency and flexibility of the development beginning
already early in the requirements definition phase. Testing requirements are some of the most important techniques to give
feedback and to increase the quality of the result. Therefore testing of artifacts should be introduced as early as possible,
even in the requirements definition phase.},
added-at = {2006-09-17T06:41:48.000+0200},
author = {Botaschanjan, J. and Pister, M. and Rumpe, B.},
biburl = {https://www.bibsonomy.org/bibtex/2b5662607505444ca04bb287deea36f9a/fink08},
citeulike-article-id = {776817},
description = {From CUL on Sept 16},
editor = {Wu, Xiufang},
interhash = {e887ccedb6bf5692e214650c1c6e358e},
intrahash = {b5662607505444ca04bb287deea36f9a},
journal = {Journal of Zhejiang University SCIENCE},
keywords = {agile requirements},
number = 5,
pages = {587--593},
priority = {0},
timestamp = {2006-09-17T06:41:48.000+0200},
title = {Testing Agile Requirements Models},
url = {http://www4.in.tum.de/~botascha/doc/Hangzhou.ReqTestingFinal.pdf},
volume = 5,
year = 2004
}