Skip to main content
Log in

Testing agile requirements models

  • Computer & Information Science
  • Published:
Journal of Zhejiang University-SCIENCE A Aims and scope Submit manuscript

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.

This is a preview of subscription content, log in via an institution to check access.

Access this article

Price excludes VAT (USA)
Tax calculation will be finalised during checkout.

Instant access to the full article PDF.

Similar content being viewed by others

References

  • Beck, K., 2001. Aim, Fire (Column on the Test-First Approach). IEEE Software.

  • Binder, R., 1999. Testing Object-Oriented Systems. Models, Patterns, and Tools. Addison-Wesley.

  • Briand, L., Labiche, Y., 2001. A UML-based Approach to System Testing.In: M. Gogolla and C. Kobryn (eds): «UML»—The Unified Modeling Language, 4th Intl. Conference, LNCS 2185. Springer, p. 194–208.

  • Gabb, A., 1998. The Requirements Spectrum. Proceedings of the first regional Symposium of the Systems Engineering Society of Australia.

  • 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.

    Article  Google Scholar 

  • Heymans, P., Dubois, E., 1998. Scenario-based techniques for supporting the elaboration and the validation of formal requirements.Requirements Engineering Journal,3: 202–218.

    Article  Google Scholar 

  • 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, Jyväskylä, Finnland, LNCS 1241.

  • Krüger, I., 2000. Distributed System Design with Message Sequence Charts. Ph.D. Thesis, Technische Universität München.

  • Link, J., Fröhlich, P., 2002. Unit Tests mit Java. Der Test-First-Ansatz. dpunkt. verlag.

  • OMG, 2002. Unified Modeling Language Specification. V1.5.

  • Rumpe, B., 2003. Agiles Modellieren mit der UML. Habilitation Thesis. Technische Universität München. Institut für Informatik.

  • Rumpe, B., 2002. Executable Modeling with UML. A Vision or A Nightmare?In: Issues & Trends of Information Technology Management in Contemporary Associations, Seattle. Idea Group Publishing, Hershey, London, p. 697–701.

    Google Scholar 

  • Warmer, J., Kleppe, A., 1998. The Object Constraint Language. Addison-Wesley.

  • Wiegers, K.E., 2003. Software Requirements. Microsoft Press.

Download references

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Botaschanjan Jewgenij.

Rights and permissions

Reprints and permissions

About this article

Cite this article

Botaschanjan, J., Pister, M. & Rumpe, B. Testing agile requirements models. J. Zheijang Univ.-Sci. 5, 587–593 (2004). https://doi.org/10.1631/jzus.2004.0587

Download citation

  • Published:

  • Issue Date:

  • DOI: https://doi.org/10.1631/jzus.2004.0587

Key words

Document code

CLC number

Navigation