图书介绍
编写有效用例 英文版PDF|Epub|txt|kindle电子书版本网盘下载
- (美)Alistair Cockburn著 著
- 出版社: 北京:机械工业出版社
- ISBN:7111105370
- 出版时间:2002
- 标注页数:270页
- 文件大小:13MB
- 文件页数:300页
- 主题词:
PDF下载
下载说明
编写有效用例 英文版PDF格式电子书版下载
下载的文件为RAR压缩包。需要使用解压软件进行解压得到PDF格式图书。建议使用BT下载工具Free Download Manager进行下载,简称FDM(免费,没有广告,支持多平台)。本站资源全部打包为BT种子。所以需要使用专业的BT下载软件进行下载。如BitComet qBittorrent uTorrent等BT下载工具。迅雷目前由于本站不是热门资源。不推荐使用!后期资源热门了。安装了迅雷也可以迅雷进行下载!
(文件页数 要大于 标注页数,上中下等多册电子书除外)
注意:本站所有压缩包均有解压码: 点击下载压缩包解压工具
图书目录
Chapter 1 Introduction1
1.1 What Is a Use Case (More or Less)?1
Use Case 1 ?Buy Stocks over the Web?4
Use Case 2 ?Get Paid for Car Accident?5
Use Case 3 ?Register Arrival of a Box?6
1.2 Your Use Case Is Not My Use Case7
Use Case4 ?Buy Something(Casual Version)?9
Use Case 5 ?Buy Something(Fully Dressed Version)?9
◆Steve Adolph: Dlscovering Requirements in New Territory12
1.3 Requirements and Use Cases13
Use Cases as Project-Linking Structure14
Figure 1.1 The Hub-and-Spoke model of requirements15
1.4 When Use Cases Add Value15
1.5 Manage Your Energy16
1.6 Warm Up with a Usage Narrative17
◆Usage Narative:Getting Fast Cash18
1.7 Exercises19
Part 1 The Use Case Body Parts21
Actors Have Goals23
2.1 Interactions between Actors with Goals23
Chapter 2 The Use Case as a Contract for Behavior23
Figure 2.1 An actor with a goal calls on the responsibilities of another24
Goals Can Fail25
Interactions Are Compound25
A Use Case Collects Scenarios27
Figure 2.2 Striped trousers:Scenarios Succeed or fail28
Figure 2.3 The striped trousers showing subgoals29
2.2 Contract between Stakeholders with Interests29
Figure 2.4 The SuD serves the Primary actor,protecting offstage stakeholders30
2.3 The Graphical Model31
Figure 2.5 Actors and stakeholders32
Figure 2.6 Behavior32
Figure 2.7 Use Case as responsibility invocation33
Figure 2.8 Interactions as composite33
Chapter 3 Scope35
Table 3.1 A Sample In/Out List36
3.1 Functional Scope36
The Actor-Goal List36
The Use Case Briefs37
Table 3.2 A Sample Actor-Goal List37
3.2 Design Scope38
Table 3.3 Sample Use Case Briefs38
Figure 3.1 Design scope can be any size40
Using Graphical Icons to Highlight the Design Scope40
Design Scope Examples41
Enterprise-to,System Examples41
Use Case 6 ?Add New Service (Enterprise)?42
Use Case 7 ?Add New Service(Acura)?42
Use Case 8 ?Enter and Update Requests (Joint System)?43
Many Computers to One Application43
Use Case 9 ?Add New Service (into Acura)?44
Use Case 10 ?Note New Service Request (in BSSO)?44
Use Case 11?Update Service Request (in Bsso)?44
Use Case 12 ?Note Updated Request (in Acura)?44
Figure 3.2 Use case diagrams for Acura-BSSO45
Figure 3.3 A combined use case diagram for Acura-Bsso45
Nuts and Bolts Use Cases46
Use Case 13 ?Serialize Access to a Resource?46
Use Case 14 ?Apply a Lock Conversion Policy?47
Use Case 15 ?Apply an Access Compatibility Policy?48
Use Case 16 ?Apply an Access Selection Policy?48
Use Case 17 ?Make Service Client Wait for Resource Access?49
3.3 The Outermost Use Cases49
3.4 Using the Scope-Defining Work Products51
3.5 Exercises51
Chapter 4 Stakeholders and Actors53
4.1 Stakeholders53
4.2 The Primary Actor54
Why Primary Actors Are Unimportant (and Important)55
Table 4.1 A Sample Actor Profile Table56
Actors versus Roles57
Characterizing the Primary Actors58
4.3 Supporting Actors59
4.4 The System Under Discussion59
4.5 Internal Actors and White-Box Use Cases59
4.6 Exercises60
Chapter 5 Three Named Goal Levels61
5.1 User Goals (Blue,Sea-Level)62
Figure 5.1 Use case levels62
Two Levels of Blue63
5.2 Summary Level(White,Cloud/Kite)64
Use Case 18 ?Operate an Insurance Policy+?65
The Outermost Use Cases Revisited65
5.3 Subfunctions (Indigo/Black,Underwater/Clam)66
Summarizing Goal Levels66
5.4 Using Graphical Icons to Highlight Goal Levels67
5.5 Finding the Right Goal Level68
Finding the User s Goal68
Figure 5.2 Ask why to shift Levels69
Raising and Lowering Goal Levels69
5.6 A Longer Writing Sample:”Handle a Claim”at Several Levels70
Use Case 19 ?Handle a Claim (Business)?71
Use Case 20 ?Evaluate Work Comp Claim?72
Use Case 21 ?Handle a Claim(Systems)+?73
Use Case 22 ?Register a Loss?75
Use Case 23 ?Find a Whatever (Problem Statement)?79
5.7 Exercises79
6.1 Preconditions81
Chapter 6 Preconditions,Triggers,and Guarantees81
6.2 Minimal Guarantees83
6.3 Success Guarantee84
6.4 Triggers84
6.5 Exercises85
Chapter 7 Scenarios and Steps87
7.1 The Main Success Scenario87
The Common Surrounding Structure87
The Scenario Body89
Guideline 1:Use Simple Grammar90
Guideline 2:Show Clearly Who Has the Ball90
7.2 Action Steps90
Guidelines90
Guideline 3:Write from a Bird s Eye View91
Guideline 4:Show the Process Moving Forward91
Guideline 5:Show the Actor s Intent,Not the Movements92
Guideline 6:Include a Reasonable Set of Actions93
Figure 7.1 Atransaction has four parts93
Guideline 8:Optionally Mention the Timing95
Guideline 7:”Validate,”Don t Check Whether95
Guideline 9:Idiom: User Has System A Kick System B96
Guideline 10:Idiom: Do Steps x-y until Condition”96
To Number or Not to Number97
7.3 Exercises98
Chapter 8 Extensions99
8.1 Extension Basics99
8.2 The Extension Conditions100
Brainstorm All Conceivable Failures and Alternative Courses101
Guideline 11:Make the Condition Say What Was Detected102
Rationalize the Extensions List104
Rollup Failures105
8.3 Extension Handling106
Guideline 12:Indent Condition Handling108
Failures within Failures109
Creating a New Use Case from an Extension109
8.4 Exercises110
Chapter 9 Technology and Data Variations111
Figure 9.1 Technology variations using specialization in UML112
10.1 Sub Use Cases113
Chapter 10 Linking Use Cases113
10.2 Extension Use Cases114
Figure 10.1 UML diagram of extension use cases115
When to Use Extension Use Cases116
10.3 Exercises117
Chapter 11 Use Case Formats119
11.1Formats to Choose From119
Fully Dressed119
Use Case 24 Fully Dressed Use Case Template
Use Case 25 ?Actually Login (Casual Version)?120
Casual120
OneColumn Table121
Table 11.1 One-Column Table Format of a Use Case121
Two-Column Table122
Table 11.2 Two-Column Table122
RUP Style123
Use Case 26 ?Register for Courses?124
If-Statement Style126
Occam Style126
Diagram Style127
11.2 Forces Affecting Use Case Writing Styles128
The UML Use Case Diagram128
Consistency130
Complexity130
11.3 Standards for Five Project Types132
For Requirements Elicitation133
Use Case 27 ?Elicitation Template一Oble a New Biscum?133
For Business Process Modeling134
Use Case 28 ?Business Process Template一Symp a Carstromming?134
For Sizing the Requirements135
Use Case 29 ?Sizing Template一Burble the Tramling?135
Use Case 30 ?High-Pressure Template:Kree a Ranfath?136
For a Short,High-Pressure Project136
For Detailed Functional Requirements137
Use Case 31 ?Use Case Name一Nathorize a Permion?137
11.4 Conclusion137
11.5 Exercise138
Part 2 Frequently Discussed Topics139
Chapter 12 When Are We Done?141
On Being Done142
Chapter 13 Scaling Up to Many Use Cases143
Say Less about Each One (Low-Precision Representation)143
Create Clusters of Use Cases143
14.1 CRUD Use Cases145
Figure 13.1 Design scopes for the ATM145
Chapter 14 CRUD and Parameterized Use Cases145
Use Case 32 ?Manage Reports?146
Use Case 33 ?Save Report?148
14.2 Parameterized Use Cases150
Chapter 15 Business Process Modeling153
15.1 Modeling versus Designing153
Work from the Core Business154
Figure 15.1 Core business black box155
Figure 15.2 New business design in white box155
Work from Business Process to Technology155
Figure 15.3 New Business design in white box(again)156
Figure 15.4 New Business process in black-box system use cases156
15.2 Linking Business and System Use Cases157
Work from Technology to Business Process157
◆Rusty Walters:Business Modeling and System Requirements159
Chapter 16 The Missing Requirements161
16.1 Precision in Data Requirements162
16.2 Cross-linking from Use Cases to Other Requirements164
Figure 16.1 Recap of Figure 1.1, Hub-and-Spoke model of requirements164
Chapter 17 Use Cases in the Overall Process167
17.1 Use Cases in Project Organization167
Organize by Use Case Titles167
Table 17.1 Sample Planning Table168
Handle Use Cases Crossing Releases169
Deliver Complete Scenarios170
17.2 Use Cases to Task or Feature Lists171
Use Case 34 ?Capture Trade-In?172
Table 17.2 Work List for Capture Trade-In173
17.3 Use Cases to Design174
A Special Note to Object-Oriented Designers176
17.4 Use Cases to UI Design177
Use Case 35 ?Order Goods,Generate Invoice (Testing Example)?178
17.5 Use Cases to Test Cases178
Table 17.3 Main Success Scenario Tests(Good Credit Risk)179
Table 17.4 Main Success Scenario Tests(Bad Credit Risk)180
17.6 The Actual Writing180
A Branch-and-Join Process180
◆Andy Kraus:Collecting Use Ca??s from a Large,Dlverse Lay Group184
Collecting Use Cases from Large Groups184
Time Required per Use Case184
Chapter 18 Use Case Briefs and Extreme Programming187
Chapter 19 Mistakes Fixed189
19.1 No System189
19.2 No Primary Actor190
19.3 Too Many User Interface Details191
19.4 Very Low Goal Levels192
19.5 Purpose and Content Not Aligned193
19.6 Advanced Example of Too Much Ul194
Use Case 36 ?Research a Solution一Before?194
Use Case 37 ?Research Possible Solutions一After?199
Part 3 Reminders for the Busy203
Reminder 2:Make the Use Case Easy to Read205
Reminder 1:A Use Case Is a Prose Essay205
Chapter 20 Reminders for Each Use Case205
Reminder 3:Just One Sentence Form206
Reminder 5:Who Has the Ball?207
Reminder 4: Include Sub Use Cases207
Reminder 6:Get the Goal Level Right208
Figure 20.1 Ask why to shift levels208
Reminder 7:Keep the GUI Out209
Reminder 8:Two Endings209
Reminder 9:Stakeholders Need Guarantees210
Reminder 10:Preconditions211
Reminder 11:Pass/Fail Tests for One Use Case211
Table 20.1 Pass/Fail Tests for One Use Case212
Chapter 21 Reminders for the Use Case Set215
Reminder 12:An Ever-Unfolding Story215
Reminder 13:Both Corporate Scope and System Scope216
Reminder 14:Core Values and Variations216
Reminder 15:Quality Questions across the Use Case Set219
Reminder 17:Work Breadth First221
Reminder 16:It s Just Chapter 3 (Where s Chapter 4?)221
Chapter 22 Reminders for Working on the Use Cases221
Figure 22.1 Work expands with precision222
Reminder 18:The 12-Step Recipe223
Reminder 19:Know the Cost of Mistakes223
Reminder 20:Blue Jeans Preferred224
Reminder 21:Handle Failures225
Reminder 22:Job Titles Sooner and Later225
Reminder 23:Actors Play Roles226
Figure 22.2 Mommy,I want to go home.227
Reminder 24:The Great Drawing Hoax227
Figure 22.3 Context diagram in ellipse figure form228
Table 22.1 Actor-Goal List for Context Diagram228
Reminder 25:The Great Tool Debate229
Reminder 26:Project Planning Using Titles and Briefs230
Appendices233
Appendix A Use Cases in UML233
A.1 Ellipses and Stick Figures233
A.2 UML s Includes Relation234
Figure A.1 Drawing Includes234
A.3 UML s Extends Relation235
Guideline 13:Draw Higher Goals Higher235
Guideline 15:Use Different Arrow Shapes236
Figure A.2 Drawing Extends236
Guideline 14:Draw Extending Use Cases Lower236
Correct Use of Extends237
Figure A.3 Three interrupting use cases extending a base use case237
Extension Points237
A.4 UML s Generalizes Relations239
Correct Use of Generalizes239
Figure A.4 Drawing Generalizes240
Hazards of Generalizes240
Guideline 16:Draw General Goals Higher240
Figure A.5 Hazardous generalization一closing a big deal241
Figure A.6 Correctly closing a big deal241
A.5 Subordinate versus Sub Use Cases242
A.6 Drawing Use Case Diagrams242
Guideline 17:User Goals in a Context Diagram243
Guideline18: Supporting Actors on the Right243
A.7 Write Text-based Use Cases Instead243
Chapter 3, page 51245
Appendix B Answers to (Some)Exercises245
Chapter 4, page 60246
Chapter 5, page 79247
Chapter 6, page 85248
Chapter 7, page 98249
Use Case 38 ?Use the Order Processing System?250
Use Case 39 ?Buy Stocks Over the Web?251
Chapter 11, page 138252
Use Case 40 ?Perform Clean Spark Plugs Service?252
Chapter 8, page 110252
Appendix C Glossary253
Main Terms253
Use Case Types255
Diagrams256
Appendix D Readings257
Books Referenced in the Text257
Articles Referenced in the Text257
Useful Online Resources258
Index259