Abstract
The requirements review session ensures that the system as described genuinely matches up with the requirements. It’s a collaborative review session involving the customer representative(s), end users (i.e., the people who will actually be using the system, or who are using the current system being replaced), and marketing people—basically, all the project stakeholders who have a vested interest in ensuring the requirements fit their view of the system.
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.
References
For a lyrical view of why this is a bad thing, see “The Customer’s a Beast of Burden” on page 120 of our book Extreme Programming Refactored: The Case Against XP (Apress, 2003).
General George S. Patton, War as I Knew It (New York: Mariner Books, 1995), p. 335 (referring to battle planning).
Doug Rosenberg and Kendall Scott, Applying Use Case Driven Object Modeling With UML (New York: Addison-Wesley, 2001), p. 53.
Ibid.
Rights and permissions
Copyright information
© 2007 Doug Rosenberg and Matt Stephens
About this chapter
Cite this chapter
(2007). Requirements Review. In: Use Case Driven Object Modeling with UML. Apress. https://doi.org/10.1007/978-1-4302-0369-8_4
Download citation
DOI: https://doi.org/10.1007/978-1-4302-0369-8_4
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