Abstract
Nowadays, the complexity of the software systems that needs to be produced is staggering. Developing such systems requires that the development team first understands the problem, i.e., they have a global picture of what is required to be built, before they can make a sensible judgment on an architecture for the solution. Use cases offer a simple, storytelling-like way to capture the requirements. They provide a means for facilitating the capture and validation of requirements from stakeholders, technical and non-technical alike, which makes them an important tool to have in one’s development kit. The simplicity of the use case concept is nevertheless deceptive, because writing effective use cases requires much practice and experience. In fact, there are many issues that must be addressed on the road to mastering requirements elicitation with use cases. In this tutorial, a number of these issues will be raised and addressed, giving the participants a better understanding of what an effective use case is, how to produce them, and where use cases in general can be appropriately applied.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2003 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Sendall, S. (2003). Requirements Elicitation with Use Cases. In: Guelfi, N., Astesiano, E., Reggio, G. (eds) Scientific Engineering for Distributed Java Applications. FIDJI 2002. Lecture Notes in Computer Science, vol 2604. Springer, Berlin, Heidelberg. https://doi.org/10.1007/3-540-36520-6_19
Download citation
DOI: https://doi.org/10.1007/3-540-36520-6_19
Published:
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-540-00679-4
Online ISBN: 978-3-540-36520-4
eBook Packages: Springer Book Archive