Abstract
We’ve held off on discussing requirements until the end of the book for a couple of reasons. First off, there seems to be a lot of confusion about the differences between requirements, use cases, and behavior (operations). Since we talked about use cases in Chapter 3, allocating behavior in Chapter 8, and a whole series of techniques driven by use cases and operations in the subsequent chapters, it’s easier to talk about requirements in terms of how they contrast with those items.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
Similar content being viewed by others
References
Doug Rosenberg and Kendall Scott, Use Case Driven Object Modeling with UML: A Practical Approach (New York: Addison-Wesley, 1999).
Rights and permissions
Copyright information
© 2007 Doug Rosenberg and Matt Stephens
About this chapter
Cite this chapter
(2007). Addressing Requirements. In: Use Case Driven Object Modeling with UML. Apress. https://doi.org/10.1007/978-1-4302-0369-8_13
Download citation
DOI: https://doi.org/10.1007/978-1-4302-0369-8_13
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