Full Text:
<2295>
CLC number: TP31
On-line Access:
Received:
Revision Accepted:
Crosschecked: 0000-00-00
Cited: 1
Clicked: 4901
Testing agile requirements models
| |||||||||||||
BOTASCHANJAN Jewgenij, PISTER Markus, RUMPE Bernhard. Testing agile requirements models[J]. Journal of Zhejiang University Science A, 2004, 5(5): 587-593.
@article{title="Testing agile requirements models",
author="BOTASCHANJAN Jewgenij, PISTER Markus, RUMPE Bernhard",
journal="Journal of Zhejiang University Science A",
volume="5",
number="5",
pages="587-593",
year="2004",
publisher="Zhejiang University Press & Springer",
doi="10.1631/jzus.2004.0587"
}
%0 Journal Article
%T Testing agile requirements models
%A BOTASCHANJAN Jewgenij
%A PISTER Markus
%A RUMPE Bernhard
%J Journal of Zhejiang University SCIENCE A
%V 5
%N 5
%P 587-593
%@ 1869-1951
%D 2004
%I Zhejiang University Press & Springer
%DOI 10.1631/jzus.2004.0587
TY - JOUR
T1 - Testing agile requirements models
A1 - BOTASCHANJAN Jewgenij
A1 - PISTER Markus
A1 - RUMPE Bernhard
J0 - Journal of Zhejiang University Science A
VL - 5
IS - 5
SP - 587
EP - 593
%@ 1869-1951
Y1 - 2004
PB - Zhejiang University Press & Springer
ER -
DOI - 10.1631/jzus.2004.0587
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.
[1] Beck, K., 2001. Aim, Fire (Column on the Test-First Approach). IEEE Software.
[2] Binder, R., 1999. Testing Object-Oriented Systems. Models, Patterns, and Tools. Addison-Wesley.
[3] Briand, L., Labiche, Y., 2001. A UML-based Approach to System Testing.In: M. Gogolla and C. Kobryn (eds): UMLThe Unified Modeling Language, 4th Intl. Conference, LNCS 2185. Springer, p.194-208.
[4] Gabb, A., 1998. The Requirements Spectrum. Proceedings of the first regional Symposium of the Systems Engineering Society of Australia.
[5] Harel, D., Rami, M., 2003. Specifying and executing behavioral requirements: the play-in/play-out approach.Journal on Software and Systems Modeling,SOSYM,2(2):82-107.
[6] Heymans, P., Dubois, E., 1998. Scenario-based techniques for supporting the elaboration and the validation of formal requirements.Requirements Engineering Journal,3:202-218.
[7] Kiczales, G., Lamping, J., Mendhekar, A., Maeda, C., Lopez, C., Loingtier, J.M., Irwin, J., 1997. Aspect-Oriented Programming. ECOOP'97 Object Oriented Programming, 11th European Conference, Jyvskyl, Finnland, LNCS 1241.
[8] Krüger, I., 2000. Distributed System Design with Message Sequence Charts. Ph.D. Thesis, Technische Universitt München.
[9] Link, J., Frhlich, P., 2002. Unit Tests mit Java. Der Test-First-Ansatz. dpunkt.verlag.
[10] OMG, 2002. Unified Modeling Language Specification. V1.5.
[11] Rumpe, B., 2003. Agiles Modellieren mit der UML. Habilitation Thesis. Technische Universitt München, Institut für Informatik.
[12] Rumpe, B., 2002. Executable Modeling with UML. A Vision or A NightmareIn: Issues & Trends of Information Technology Management in Contemporary Associations, Seattle. Idea Group Publishing, Hershey, London, p.697-701.
[13] Warmer, J., Kleppe, A., 1998. The Object Constraint Language. Addison-Wesley.
[14] Wiegers, K.E., 2003. Software Requirements.Microsoft Press.
Open peer comments: Debate/Discuss/Question/Opinion
<1>
utmshah@utmshah<ptar4_2010@uitmedu.my>
2010-08-14 10:39:33
nice