Use case modeling

Authors:

Language: English
Cover of the book Use case modeling

Subject for Use case modeling

Approximative price 61.55 €

Subject to availability at the publisher.

Add to cartAdd to cart
Publication date:
346 p. · 19x23 cm · Paperback
A guide to building upon existing requirements-gathering skills and better leveraging the significant power of use cases.
  • A ready reference for the use case practitioner.
  • Reviews the fundamentals of use cases, and then explores the details to becoming writing better use cases.
  • Based on real-world issues, and how project teams overcame them.
Kurt Bittner works for Rational Software as a member of the Rational Unified Process development team. With nearly twenty years in the software industry, his experience covers the complete development life cycle, including analysis, design, development, and project management. He has worked in a number of industries including financial services, manufacturing, and software. Ian Spence also works for Rational Software.

Audience:

The whole gamut of those who are impacted by use cases: customers, project managers, analysts, developers, testers, and anyone else who wants to better understand use cases.

(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 Representatives in the Project.
Creating a Shared Vision.
Analyze the Problem.
Understand the Key Stakeholder and User Needs.
Describe the Features and Other High-Level Product Requirements.
Provide an Overview of the Product.
Bringing It All Together: The Vision Document.
Do You Really Need To Do All Of This?

4. Finding Actors and Use Cases.
Finding Actors.
Start by Identifying the Primary Actors.
Work from the Specific to the General.
Dont Forget the Supporting Actors.
Consider All Existing Requirements Information.
Remember That Actors Are Not Always People.
Focus on the System Boundary.
Identify the information sources.
Dont Preempt the Design.
Dont Confuse the Actors with the Devices They Use.
When you Cant Find the Actors, Start with the Use Cases.
Focus First on the Familiar.
Evolve the Set of Actors Alongside the Set of Use Cases.
Documenting Actors.
How to Name Actors.
Dont Confuse Actors with Organizational Roles or Job Titles.
Dont Overgeneralize.
Give Every Actor a Brief Description.
Characterize the Actors.
Trace the Actors to the User Types, Stakeholders, and Stakeholder Roles.
Finding Use Cases.
Start by Identifying the Actor Goals.
Consider the Information Needs of the System and Its Users.
Dont Worry About Commonality (at least at first).
Dont Confuse Use Cases with Functions .
Focus on Value.
Derive the Use Cases from the Systems Vision.
Dont Forget the Supporting and Operational Use Cases.
Evolve the Set of Use Cases Alongside the Set of Actors and the Supplementary Specification.
Documenting Use Cases.
Associate the Use Cases to their Actors.
Name the Use Cases.
Give every Use Case a Brief Description.
Outline the Use Cases.
Trace the Use Cases to Stakeholders and Stakeholder Roles.
Trace the Use Cases to the Features and Constraints.