Foreword |
|
xiii | (2) |
Preface |
|
xv | (2) |
Acknowledgments |
|
xvii | |
|
|
1 | (12) |
|
|
1 | (1) |
|
|
2 | (3) |
|
Notations and Meta-Models |
|
|
5 | (2) |
|
Why Do Analysis and Design? |
|
|
7 | (3) |
|
|
7 | (2) |
|
Communicating with Domain Experts |
|
|
9 | (1) |
|
Understanding the Big Picture |
|
|
10 | (1) |
|
Looking for More Information |
|
|
10 | (3) |
|
Chapter 2: An Outline Development Process |
|
|
13 | (30) |
|
|
14 | (2) |
|
|
16 | (1) |
|
|
16 | (13) |
|
Dealing with Requirements Risks |
|
|
17 | (5) |
|
Dealing with Technological Risks |
|
|
22 | (1) |
|
Dealing with Skills Risks |
|
|
23 | (2) |
|
Dealing with Political Risks |
|
|
25 | (1) |
|
|
25 | (1) |
|
When Is Elaboration Finished? |
|
|
26 | (1) |
|
|
26 | (3) |
|
|
29 | (1) |
|
|
30 | (6) |
|
|
32 | (1) |
|
|
32 | (1) |
|
Iterative Development and Planning |
|
|
33 | (1) |
|
Using the UML in Construction |
|
|
33 | (3) |
|
|
36 | (4) |
|
|
39 | (1) |
|
|
39 | (1) |
|
|
40 | (1) |
|
When to Use Iterative Development |
|
|
41 | (1) |
|
|
41 | (2) |
|
|
43 | (10) |
|
User Goals and System Interactions |
|
|
44 | (1) |
|
|
45 | (6) |
|
|
46 | (2) |
|
|
48 | (3) |
|
|
51 | (1) |
|
|
51 | (2) |
|
Chapter 4: Class Diagrams: The Essentials |
|
|
53 | (22) |
|
|
55 | (1) |
|
|
56 | (7) |
|
|
63 | (1) |
|
|
63 | (1) |
|
|
64 | (4) |
|
|
66 | (1) |
|
|
66 | (2) |
|
|
68 | (1) |
|
|
69 | (1) |
|
|
70 | (3) |
|
When to Use Design by Contract |
|
|
72 | (1) |
|
|
73 | (1) |
|
When to Use Class Diagrams |
|
|
73 | (1) |
|
|
74 | (1) |
|
Chapter 5: Class Diagrams: Advanced Concepts |
|
|
75 | (28) |
|
|
75 | (2) |
|
Multiple and Dynamic Classification |
|
|
77 | (3) |
|
Aggregation and Composition |
|
|
80 | (2) |
|
Derived Associations and Attributes |
|
|
82 | (3) |
|
Interfaces and Abstract Classes |
|
|
85 | (3) |
|
Reference Objects and Value Objects |
|
|
88 | (1) |
|
Collections for Multi-Valued Roles |
|
|
89 | (1) |
|
|
90 | (1) |
|
Classification and Generalization |
|
|
91 | (1) |
|
|
91 | (2) |
|
|
93 | (3) |
|
|
96 | (3) |
|
|
99 | (4) |
|
Chapter 6: Interaction Diagrams |
|
|
103 | (10) |
|
|
104 | (4) |
|
Concurrent Processes and Activations |
|
|
106 | (2) |
|
|
108 | (3) |
|
Comparing Sequence and Collaboration Diagrams |
|
|
111 | (1) |
|
|
112 | (1) |
|
When to Use Interaction Diagrams |
|
|
112 | (1) |
|
|
112 | (1) |
|
Chapter 7: Package Diagrams |
|
|
113 | (8) |
|
When to Use Package Diagrams |
|
|
119 | (1) |
|
|
120 | (1) |
|
Chapter 8: State Diagrams |
|
|
121 | (8) |
|
Concurrent State Diagrams |
|
|
126 | (2) |
|
When to Use State Diagrams |
|
|
128 | (1) |
|
|
128 | (1) |
|
Chapter 9: Activity Diagrams |
|
|
129 | (14) |
|
Activity Diagrams for Use Cases |
|
|
132 | (6) |
|
|
138 | (2) |
|
|
140 | (1) |
|
When to Use Activity Diagrams |
|
|
141 | (1) |
|
|
142 | (1) |
|
Chapter 10: Deployment Diagrams |
|
|
143 | (4) |
|
When to Use Deployment Diagrams |
|
|
145 | (2) |
|
Chapter 11: UML and Programming |
|
|
147 | (20) |
|
Patient Observation: Domain Model |
|
|
148 | (4) |
|
Patient Observation: Specification Model |
|
|
152 | (3) |
|
|
155 | (12) |
Appendix: Techniques and Their Uses |
|
167 | (2) |
Bibliography |
|
169 | (4) |
Index |
|
173 | |