Table of Contents

(NOTE: Each chapter concludes with a Summary.)

Foreword.


Preface: Why Bother with Use Cases?
What Are “Use Cases” All About? Who Should Be Interested in Use Cases? How to Read This Book.

I. GETTING STARTED WITH USE CASE-MODELING.

1. A Brief Introduction to Use-Case Modeling.
Actors and Use Cases. Use-Case Diagrams. The Relationship Between Use Cases and Requirements. Types of Requirements. Functional and Nonfunctional Requirements. The Role of Use Cases. Use Cases Place Software Requirements in Context. To “Use Case” or not to “Use Case”. When Are Use Cases Useful? Use Cases Provide a Conceptual Model of the System. Use Cases Describe How the System Is Used and What It Does for Its Stakeholders. Does Everything the System Does Have to Be Described in a Use Case? General Principles of Use-Case Modeling. Use Cases Do Not Exist In Isolation. Use Cases Are a Synthetic Rather Than an Analytic Technique. Rules of Thumb. 2. Fundamentals of Use Case Modeling.
The Use-Case Model. The Basic Building Blocks of a Use-Case Model. Actors. Use Cases. Connecting Actors and Use cases. Use-Case Diagrams. Brief Descriptions. Use-Case Descriptions. Supporting Artifacts. The Glossary and/or the Domain Model. Supplementary Specifications. Declarative and Special Requirements. 3. Establishing the Vision.
Introducing Stakeholders and Users. What Are Stakeholders? The Role of Stakeholders and Stakeholder Representatives. Users: A Very Important Class of Stakeholder. Stakeholders and Use-Case Modeling. Involving Stakeholders and Users In Your Project. Step 1: Identify Stakeholder and User Types. Step 2: Identify and Recruit the Stakeholder Representatives. Step 3: Involve the Stakeholder Represe

Promotional Information

Use cases are a simple, straightforward -- yet very powerful -- way to express the functional requirements (or behaviors) of a system. Use cases have gained widespread acceptance because they make requirements less ambiguous by specifying exactly when and under what conditions certain behaviors occur. As a result, those who effective employ use cases to model their systems can better deliver projects on time, within budget, and with fewer defects. However, use case modeling is not that easy; it is a practice that comes with characteristics that can impact a project. In this new book, the authors allow you to benefit from their considerable experience making use cases work well in a number of different environments. With the advice, tips, and tricks presented herein, the reader will be further along the path to understanding and exploiting the power of use cases, and ultimately constructing better applications. In writing this book, the authors have worked closely with use case founder Ivar Jacobson, and the book is unique in that it presents a Rational Software Corporation-centric examination of this topic.

About the Author

The director for Requirements Management Solutions at Rational Software, Kurt Bittner served on the original Rational Unified Process development team. He has twenty years of experience in software development, including work in requirements capture, analysis, design, development, and project and product management.

A senior consultant at Rational Software, Ian Spence specializes in the adoption of the Rational Unified Process and the use case driven approach that it recommends. He has over eighteen years of experience in the software industry, covering the complete development lifecycle, including requirements capture, architecture, analysis, design, implementation, and project management.

0201709139AB08062002