Summary:

Use Cases: Requirements in Context describes how to gather and define software requirements using a process based on use cases. It shows systems analysts and designers how use cases can provide solutions to the most challenging requirements issues, resulting in effective, quality systems that meet the needs of users. Specifically, with use cases, you can: Reduce the incidence of duplicate and inconsistent requirements; Communicate requirements that are understandable to both users and developers; Prototype the right system well before the design phase is underway; Document the entire requirements process clearly and efficiently. Use Cases: Requirements in Context first examines the difficulties of requirements gathering and briefly introduces both use cases and the Unified Modeling Language (UML). Using detailed examples that run through the book, it then elaborates a four-step method for establishing requirements--an iterative process that produces increasingly refined requirements. Drawing on their own extensive experience, the authors offer practical advice on how to manage this process, including guidance on planning, scheduling and estimating. They also reveal common mistakes and pitfalls to avoid. This detailed, hands-on book shows you how to: Describe object relationships and interactions with use case diagrams and scenarios Specify functional and non-functional requirements Create the candidate use case list Break out detailed use cases and add detail to use case diagrams Add triggers, preconditions, basic course of events, and exceptions to use cases Other topics include stakeholder interviews, use case name filters, the context matrix, user interface requirements, team organization, and quality assurance. --This text refers to an out of print or unavailable edition of this title.

Table of Contents:
Preface Second Edition.
Preface First Edition.
1. The Trouble with Requirements.
First and Least of All….
What Is a Requirement?
Requirements Gathering, Definition, and Specification.
The Challenges of Requirements Gathering.
Issues with the Standard Approaches.
Those Troublesome Requirements.

2. Moving to Use Cases.
It's All About Interactions.
The Unified Modeling Language.
Introducing Use Cases, Use Case Diagrams, and Scenarios.
Use Cases Apply Here.
Applying Use Cases to the Requirements Problem.

3. A Use-Case-Driven Approach to Requirements Gathering.
Requirements Specification Tools.
Principles for Requirements Success.
Three Steps for Gathering Requirements.
The Role of the Mission, Vision, Values.
The Role of the Statement of Work
The Role of the Risk Analysis.
The Role of the Prototype.
The Roles of Use Cases.
The Role of the Business Rules Catalog.
Managing Success.

4. The Facade Iteration.
Objectives.
Steps in the Facade Iteration.
Tools.
Deliverables.
Roles.
Context.
Summary.

5. The Filled Iteration.
Objectives.
Steps.
Tools.
Deliverables.
Roles.
Context.
Summary.

6. Focused Iteration.
Objectives'.
What Are Focused Use Cases?
Steps.
Tools.
Deliverables.
Roles.
Context.
Summary.

7. Managing Requirements and People.
Introduction.
Waterfall Lifecycle Management.
Alternatives to Waterfall.
Introducing the Holistic Iterative/Incremental Use Case Driven Project
Lifecycle.
Process.
Principles of the Holistic Iterative/Incremental Software Lifecycle.

8. Requirements Traceability.
Tracing Back to Use Cases.
Tracing Back to Nonfunctionals.
Tracing Back to Business Rules.

9. Classic Mistakes.
Mistakes, Pitfalls, and Bruised Knees.
Classic Mistakes: Make Them and Move On.

10. The Case for Use Cases.
Why Did Use Cases Win?
Use Cases Beyond Software.
Summary.

Appendix A. Real Estate Management System.
Appendix B. Integrated Systems.
Appendix C. Instant Messaging Encryption.
Appendix D. Order a Product from a Catalog.
Bibliography.
Index.
0321154983T04012003