Applying Use Cases: A Practical Guide
With the emergence of the Unified Modeling Language (UML) over the last few years, developers new to the advantages of thorough software-engineering practices now have a better notational system for designing more effective software. To use UML effectively, you will want to createuse cases, which help describe the requirements of a system. In their concise and very readable book, the authors ofApplying Use Casesshow how use cases can benefit all aspects of the software-design process and let you create better software in less time.This guide provides a case study for a mail-order business (with some e-commerce as well) as its central example. Use cases define howactors(i.e., users) are defined for all the various components of a mail-order business, including inventory, accounting, and order fulfillment. The authors suggest that while use cases are particularly useful at the beginning of a project cycle--for assessing risks and setting project timetables, for instance--they are also useful for testing and deployment of systems (specifically, for creating documentation and help manuals). The sample use cases--and supporting design documents--are what's best in this text.--Richard Dragan