Many projects struggle to define the specific functions of software, and end users often find that the final product does not perform as expected. Use cases allow analysts to identify the required features of a software system based on how each end user will use the system. This efficient and straightforward analysis process gives end users direct input into the design of the system that will serve them. Applying Use Cases provides a practical and clear introduction to developing use cases, demonstrating their use via a continuing case study. Using the Unified Software Development Process as a framework and the Unified Modeling Language (UML) as a notation, the authors step the reader through applying use cases in the different phases of the process, focusing on where and how use cases are best applied.Other highlights include: *A collection of realistic examples showing how to apply use cases, drawn from the authors' extensive experience in this area *A case study that offers insight into the common mistakes and pitfalls that can plague an object-oriented project *An illustration of the latest version of the UML notation for diagramming use cases *A practical "how-to" discussion on applying use cases to identify system requirements 0201309815B04062001
--このテキストは、絶版本またはこのタイトルには設定されていない版型に関連付けられています。
For applying use cases, it is important to identify system boundaries. System is made from input, output, state and control. If system boundaries are not certain, input, output and state are not uncertain. It is easy to make a sence of boundaries, making primary senarios. Testing the architecture with use cases is another good point.
This book is good starting point to study use cases.