Use Cases: Requirements in Context
Search in google:
Outlining a process based on use cases, this introductory-level tutorial provides instruction for gathering and defining software requirements. Written for systems analysts and designers, the book describes a three-step method for establishing increasingly refined requirements. Numerous examples demonstrate the practical application of this approach. Kulak has worked as a software development manager. Guiney is a consultant. Annotation ©2003 Book News, Inc., Portland, OR Booknews Describes how to gather and define software requirements using a process based on use cases. First examines difficulties of requirements gathering and introduces both use cases and UML. Presents detailed ongoing examples and a four-step method for establishing requirements, with practical advice provided on planning, scheduling, estimating, and common mistakes. Other tools examined include the stakeholder interview, team organization, and quality assurance. Kulak is president and CEO of an Internet business and technology consulting firm; Guiney works with a company that provides management consulting and system integration services. Annotation c. Book News, Inc., Portland, OR (booknews.com)
PrefacePreface to the First Edition1The Trouble with Requirements12Moving to Use Cases213A Use-Case-Driven Approach to Requirements Gathering534The Facade Iteration635The Filled Iteration936Focused Iteration1097Managing Requirements and People1198Requirements Traceability1499Classic Mistakes15910The Case for Use Cases173AReal Estate Management System183BIntegrated Systems219CInstant Messaging Encryption225DOrder a Product from a Catalog229Bibliography235Index237
