Use Case Driven Object Modeling with UML

471 Pages·2007·11.34 MB·English

CYAN YELLOW
MAGENTA BLACK
PANTONE 123 CV
BOOKS FOR PROFESSIONALS BY PROFESSIONALS® THE EXPERT’S VOICE® IN UML MODELING
Companion
eBook Available
Use Case Driven Object Modeling with UML:
PPaacckkeedd wwiitthh
Theory and Practice eexxaammpplleess aanndd
OU
ssttuuddeenntt eexxeerrcciisseess
Dear Reader, bs
In theoryyou’d like to be using UML and use cases, but in practiceit’s often je
e
difficult. Here are a few reasons why:
Doug Rosenberg, • UML is too big.In theoryit’s all good, but in practiceUML’s size makes it cC Use Case Driven
author of
Use Case Driven Object impractical and causes analysis paralysis. We’ll teach you a UML core subset ta
and a minimalist process that’s been proven on hundreds of projects.
Modeling with UML:A
• Your analysts write vague and ambiguous use cases.In theorythe use cases Ms
Practical Approach
are abstract, technology-free, and implementation independent, but in e
Applying Use Case Driven Object Modeling
Object Modeling with UML: practicethey’re vague and ambiguous, so your programmers ignore them. o
We’ll teach you how to disambiguate them.
An Annotated e-Commerce D
d
Example • Your team has difficulty getting from use cases to code.In theoryit seems
Extreme Programming easy, but in practicesomething doesn’t quite mesh. The team has difficulty er
Refactored:The Case crossing the gap between “what” and “how.” We’ll unveil secrets of the i
Against XP (Apress,2003) “missing link” between analysis and design that have been closely guarded liv UML
Agile Development with by goat-herding Druids in darkest Wales for centuries. ne
• You have dysfunctional requirements.In theoryyou’re capturing everything with
ICONIX Process:People,
gn
Process,and Pragmatism (functional, nonfunctional, and behavior requirements), but in practicethese
(Apress,2005) are all intermangled together. We’ll show you how to disintermangle the
active-voice scenarios from the passive-voice requirements. w
• Your team struggles with issues like requirements traceability,test cover-
age,and keeping models and code in sync.In theorytools should help you i
with these problems, but in practiceyou’re not sure how it all fits together t
h Theory and Practice
and whether all the requirements have been implemented, even though you
unit test. We’ll show you the latest in automated tools and process support
for these issues. U
This book is suitable for classroom use and as a resource for professionals.
M
We take an example project (the Internet Bookstore) from use cases and
requirements all the way through working Java/Spring code and unit tests, in a
Matt Stephens,author of L
step-by-step approach with dozens of exercises and questions at the back of
Extreme Programming each chapter.
Fast-track your project from use cases to working,maintainable code
Refactored:The Case
Against XP (Apress,2003) Doug Rosenberg and Matt Stephens
Agile Development with
ICONIX Process:People,
Process,and Pragmatism THE APRESS ROADMAP
(Apress,2005)
Use Case Driven Object Agile Development with
Fast Track UML 2.0 Modeling with UML: ICONIX Process: People,
Theory and Practice Process, and Pragmatism
R
So
ts Doug Rosenberg and Matt Stephens
SOURCECODEONLINE Companion eBook IISSBBNN--1130:: 917-85-910-5599-075794--7574-3 ephenb
90000 ee
www.apress.com nr
sg
,
Shelve in
Systems Analysis See last page for details
on $10 eBook version
User level:
9 781590 597743
Intermediate–Advanced
this print for content only—size & color not accurate 7" x 9-1/4" / CASEBOUND / MALLOY
(0.9375 INCH BULK -- 472 pages -- 50# Thor)
7745fmfinal.qxd 12/13/06 9:23 PM Page i
Use Case Driven Object
Modeling with UML
Theory and Practice
Doug Rosenberg and
Matt Stephens
7745fmfinal.qxd 12/13/06 9:23 PM Page ii
Use Case Driven Object Modeling with UML: Theory and Practice
Copyright © 2007 by Doug Rosenberg and Matt Stephens
All rights reserved. No part of this work may be reproduced or transmitted in any form or by any means,
electronic or mechanical, including photocopying, recording, or by any information storage or retrieval
system, without the prior written permission of the copyright owner and the publisher.
ISBN-13 (pbk): 978-1-59059-774-3
ISBN-10 (pbk): 1-59059-774-5
Printed and bound in the United States of America 9 8 7 6 5 4 3 2 1
Trademarked names may appear in this book. Rather than use a trademark symbol with every occurrence
of a trademarked name, we use the names only in an editorial fashion and to the benefit of the trademark
owner, with no intention of infringement of the trademark.
Lead Editor: Jonathan Gennick
Technical Reviewer: Dr. Charles Suscheck
Editorial Board: Steve Anglin, Ewan Buckingham, Gary Cornell, Jason Gilmore, Jonathan Gennick,
Jonathan Hassell, James Huddleston, Chris Mills, Matthew Moodie, Dominic Shakeshaft, Jim Sumser,
Matt Wade
Senior Project Manager: Tracy Brown Collins
Copy Edit Manager: Nicole Flores
Assistant Production Director: Kari Brooks-Copony
Senior Production Editor: Laura Cheu
Compositor: Linda Weidemann, Wolf Creek Press
Proofreader: Nancy Riddiough
Indexer: Toma Mulligan
Artist: Kinetic Publishing Services, LLC
Cover Designer: Kurt Krames
Manufacturing Director: Tom Debolski
Distributed to the book trade worldwide by Springer-Verlag New York, Inc., 233 Spring Street, 6th Floor,
New York, NY 10013. Phone 1-800-SPRINGER, fax [phone], e-mail [email protected],
orvisit http://www.springeronline.com.
For information on translations, please contact Apress directly at 2560 Ninth Street, Suite 219, Berkeley,
CA 94710. Phone [phone], fax [phone], e-mail [email protected], or visit http://www.apress.com.
The information in this book is distributed on an “as is” basis, without warranty. Although every pre-
caution has been taken in the preparation of this work, neither the author(s) nor Apress shall have any
liability to any person or entity with respect to any loss or damage caused or alleged to be caused directly
or indirectly by the information contained in this work.
The UML model and source code for the example use cases in this book are available to readers at
http://www.apress.comand http://www.iconixprocess.com/InternetBookstore.
7745fmfinal.qxd 12/13/06 9:23 PM Page iii
For Rob,who has the brightest future of anyone I know.
Keep locating your fastball in unhittable spots,
and good things will continue to happen.
—Doug Rosenberg
To Michelle,for her never-ending patience and support.
—Matt
7745fmfinal.qxd 12/13/06 9:23 PM Page iv
Contents at a Glance
About the Authors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
About the Technical Reviewer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii
Acknowledgments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix
Preface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvii
■CHAPTER 1 Introduction to ICONIX Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
PART 1 ■ ■ ■ Requirements Definition
■CHAPTER 2 Domain Modeling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
■CHAPTER 3 Use Case Modeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
■CHAPTER 4 Requirements Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
PART 2 ■ ■ ■ Analysis, Conceptual Design, and
Technical Architecture
■CHAPTER 5 Robustness Analysis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
■CHAPTER 6 Preliminary Design Review. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
■CHAPTER 7 Technical Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
PART 3 ■ ■ ■ Design and Coding
■CHAPTER 8 Sequence Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
■CHAPTER 9 Critical Design Review. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
■CHAPTER 10 Implementation:Getting from Detailed Design
to Code. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
■CHAPTER 11 Code Review and Model Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
iv
7745fmfinal.qxd 12/13/06 9:23 PM Page v
PART 4 ■ ■ ■ Testing and Requirements
Traceability
■CHAPTER 12 Design-Driven Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
■CHAPTER 13 Addressing Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
PART 5 ■ ■ ■ Appendixes
■APPENDIX A What’s New in UML 2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395
■APPENDIX B Spring Bin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409
■INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425
v
7745fmfinal.qxd 12/13/06 9:23 PM Page vi
7745fmfinal.qxd 12/13/06 9:23 PM Page vii
Contents
About the Authors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
About the Technical Reviewer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii
Acknowledgments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix
Preface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvii
■CHAPTER 1 Introduction to ICONIX Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
ICONIX Process in Theory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Overview:Getting from Use Cases to Source Code. . . . . . . . . . . . . . . 2
Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Analysis/Preliminary Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Detailed Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Extensions to ICONIX Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Persona Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Test-Driven Development (TDD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Driving Test Cases from the Analysis Model. . . . . . . . . . . . . . . . . . . . 20
ICONIX Process in Practice:The Internet Bookstore Example. . . . . . . . . . 20
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
PART 1 ■ ■ ■ Requirements Definition
■CHAPTER 2 Domain Modeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
The 10,000-Foot View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
What’s a Domain Model?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Why Start with the Domain Model Instead of Use Cases? . . . . . . . . 25
Domain Modeling in Theory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Top 10 Domain Modeling Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Internet Bookstore:Extracting the First-Pass Domain Model
from High-Level Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Internet Bookstore:Second Attempt at the Domain Model. . . . . . . . 35
Internet Bookstore:Building Generalization Relationships. . . . . . . . 37
vii
7745fmfinal.qxd 12/13/06 9:23 PM Page viii
viii ■CONTENTS
Domain Modeling in Practice. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Exercises. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
More Practice. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
■CHAPTER 3 Use Case Modeling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
The 10,000-Foot View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Why Do I Need Use Cases in Addition to
Functional Requirements? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Don’t Forget the Rainy-Day Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . 50
Do an Initial Domain Model Before You Write the Use Cases. . . . . . 50
Driving Your Design (and Your Tests) from the Use Cases. . . . . . . . . 51
Use Case Modeling in Theory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Top 10 Use Case Modeling Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . 51
Organizing Use Cases into Packages:Internet Bookstore. . . . . . . . . 61
Use Case Relationship Roundup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Internet Bookstore:Refining Use Cases. . . . . . . . . . . . . . . . . . . . . . . . 70
Internet Bookstore:Basic and Alternate Courses. . . . . . . . . . . . . . . . 72
A Couple of Thoughts on Use Case Templates. . . . . . . . . . . . . . . . . . 74
Use Case or Algorithm? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Use Case Modeling in Practice. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Exercises. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Exercise Solutions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
More Practice. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
■CHAPTER 4 Requirements Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Requirements Review in Theory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Why Review Requirements? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Top 10 Requirements Review Guidelines . . . . . . . . . . . . . . . . . . . . . . 85
Allocating Functional Requirements to Use Cases. . . . . . . . . . . . . . . 89
Requirements Review in Practice:Internet Bookstore . . . . . . . . . . . . . . . . 89
Removing Everything That’s Out of Scope. . . . . . . . . . . . . . . . . . . . . . 90
Naming Participating Domain Objects. . . . . . . . . . . . . . . . . . . . . . . . . 92
Making Sure You Have All the Alternate Courses. . . . . . . . . . . . . . . . 93
Checking That the Use Case Text Isn’t Too Abstract . . . . . . . . . . . . . 93
Changing Passive Voice to Active Voice. . . . . . . . . . . . . . . . . . . . . . . . 95
Tracing Each Requirement to Its Use Cases. . . . . . . . . . . . . . . . . . . . 96
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
7745fmfinal.qxd 12/13/06 9:23 PM Page ix
■CONTENTS ix
PART 2 ■ ■ ■ Analysis, Conceptual Design, and
Technical Architecture
■CHAPTER 5 Robustness Analysis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
The 10,000-Foot View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Where Does Robustness Analysis Fit into the Process?. . . . . . . . . 102
Like Learning to Ride a Bicycle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Anatomy of a Robustness Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Robustness Analysis in Theory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Top 10 Robustness Analysis Guidelines. . . . . . . . . . . . . . . . . . . . . . . 104
More About Robustness Diagram Rules. . . . . . . . . . . . . . . . . . . . . . . 112
How Do You Perform Robustness Analysis? . . . . . . . . . . . . . . . . . . . 114
Updating Your Domain (Static) Model. . . . . . . . . . . . . . . . . . . . . . . . . 125
Robustness Analysis in Practice. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Exercises. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Exercise Solutions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
More Practice. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
■CHAPTER 6 Preliminary Design Review. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Preliminary Design Review in Theory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Why Do a PDR At All? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Top 10 PDR Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Preliminary Design Review in Practice:Internet Bookstore. . . . . . . . . . . 149
PDR for the “Write Customer Review”Robustness Diagram. . . . . 149
The Finished “Write Customer Review”Robustness Diagram. . . . 155
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
■CHAPTER 7 Technical Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
The 10,000-Foot View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
What Is Technical Architecture? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
What Are the Duties of a Technical Architect? . . . . . . . . . . . . . . . . . 160
Technical Architecture in Theory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Top 10 Technical Architecture Guidelines . . . . . . . . . . . . . . . . . . . . . 161
Architectural Layering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Technical Architecture in Practice:Internet Bookstore. . . . . . . . . . . . . . . 164
About Spring Framework. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Anatomy of Spring Framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165