Abstract
With an initial domain model in place, it’s time to begin writing use cases. Use cases give you a structured way of capturing the behavioral requirements of a system, so that you can reasonably create a design from them. They help you to answer some fundamental questions: What are the users of the system trying to do? What’s the user experience? A surprising amount of what your software does is dictated by the way in which users must interact with it.
This is a preview of subscription content, log in via an institution.
Buying options
Tax calculation will be finalised at checkout
Purchases are for personal use only
Learn about institutional subscriptionsPreview
Unable to display preview. Download preview PDF.
References
For more about these “three magic questions,” see p. 48 of Use Case Driven Object Modeling with UML: A Practical Approach by Doug Rosenberg and Kendall Scott (Addison-Wesley, 1999).
Alistair Cockburn, Writing Effective Use Cases (New York: Addison-Wesley, 2000), p. 119.
Rights and permissions
Copyright information
© 2007 Doug Rosenberg and Matt Stephens
About this chapter
Cite this chapter
(2007). Use Case Modeling. In: Use Case Driven Object Modeling with UML. Apress. https://doi.org/10.1007/978-1-4302-0369-8_3
Download citation
DOI: https://doi.org/10.1007/978-1-4302-0369-8_3
Publisher Name: Apress
Print ISBN: 978-1-59059-774-3
Online ISBN: 978-1-4302-0369-8
eBook Packages: Professional and Applied ComputingProfessional and Applied Computing (R0)Apress Access Books