Part III: The Basics of Use-Case Modeling

---

Chapter List

Chapter 8: Introducing Use-Case Diagrams

Chapter 9: Defining the Inside of a Use Case

Chapter 10: Relating Use Cases to Each Other

Part Overview

In this part . . .

This part covers some of the most important stuff in software and system development: Who’s your system for? What must it do? Why build it in the first place? Here we cover the basic techniques that help you find answers to those questions: use-case diagrams, which capture and present how the basic users (called actors) call upon the system in their typical situations (called use cases). We explain how to document the contents, flow, and alternate courses as the use cases unfold, making the big picture easier to grasp for narrative or specification purposes.

For advanced use-case modeling, we detail the possible relationships — inclusion, extension, and generalization — among multiple use cases, and help you avoid common problems in this tricky area.

If your use cases start to multiply and get unruly, we show how to corral them in packages so they stay manageable. And we offer advice on how use cases can not only help you create a better understanding of your system’s goals and requirements (so your stakeholders buy in with minimum fuss), but also benefit the process of design and implementation.

---