Use case modeling:
Gespeichert in:
| Hauptverfasser: | , |
|---|---|
| Format: | Buch |
| Sprache: | English |
| Veröffentlicht: |
Boston, MA [u.a.]
Addison Wesley
2008
|
| Ausgabe: | 10. print. |
| Schriftenreihe: | The Addison-Wesley object technology series
|
| Schlagworte: | |
| Online-Zugang: | Inhaltsverzeichnis |
| Beschreibung: | Includes bibliographical references (p. 337-338) and index |
| Beschreibung: | XIX, 347 S. Ill. |
| ISBN: | 9780201709131 0201709139 |
Internformat
MARC
| LEADER | 00000nam a2200000 c 4500 | ||
|---|---|---|---|
| 001 | BV036954962 | ||
| 003 | DE-604 | ||
| 005 | 20110505 | ||
| 007 | t | ||
| 008 | 110113s2008 xxua||| |||| 00||| eng d | ||
| 020 | |a 9780201709131 |9 978-0-201-70913-1 | ||
| 020 | |a 0201709139 |9 0-201-70913-9 | ||
| 035 | |a (OCoLC)706966979 | ||
| 035 | |a (DE-599)BVBBV036954962 | ||
| 040 | |a DE-604 |b ger |e aacr | ||
| 041 | 0 | |a eng | |
| 044 | |a xxu |c US | ||
| 049 | |a DE-355 |a DE-11 |a DE-2070s | ||
| 084 | |a ST 230 |0 (DE-625)143617: |2 rvk | ||
| 084 | |a ZA 76000 |0 (DE-625)154306: |2 rvk | ||
| 100 | 1 | |a Bittner, Kurt |e Verfasser |4 aut | |
| 245 | 1 | 0 | |a Use case modeling |c Kurt Bittner ; Ian Spence |
| 250 | |a 10. print. | ||
| 264 | 1 | |a Boston, MA [u.a.] |b Addison Wesley |c 2008 | |
| 300 | |a XIX, 347 S. |b Ill. | ||
| 336 | |b txt |2 rdacontent | ||
| 337 | |b n |2 rdamedia | ||
| 338 | |b nc |2 rdacarrier | ||
| 490 | 0 | |a The Addison-Wesley object technology series | |
| 500 | |a Includes bibliographical references (p. 337-338) and index | ||
| 650 | 0 | 7 | |a Requirements engineering |0 (DE-588)4213997-1 |2 gnd |9 rswk-swf |
| 650 | 0 | 7 | |a Softwareentwicklung |0 (DE-588)4116522-6 |2 gnd |9 rswk-swf |
| 650 | 0 | 7 | |a Projektmanagement |0 (DE-588)4047441-0 |2 gnd |9 rswk-swf |
| 650 | 0 | 7 | |a Anforderung |0 (DE-588)4135103-4 |2 gnd |9 rswk-swf |
| 689 | 0 | 0 | |a Requirements engineering |0 (DE-588)4213997-1 |D s |
| 689 | 0 | 1 | |a Softwareentwicklung |0 (DE-588)4116522-6 |D s |
| 689 | 0 | |5 DE-604 | |
| 689 | 1 | 0 | |a Softwareentwicklung |0 (DE-588)4116522-6 |D s |
| 689 | 1 | 1 | |a Projektmanagement |0 (DE-588)4047441-0 |D s |
| 689 | 1 | 2 | |a Anforderung |0 (DE-588)4135103-4 |D s |
| 689 | 1 | |5 DE-604 | |
| 700 | 1 | |a Spence, Ian |e Verfasser |4 aut | |
| 856 | 4 | 2 | |m Digitalisierung UB Regensburg |q application/pdf |u http://bvbr.bib-bvb.de:8991/F?func=service&doc_library=BVB01&local_base=BVB01&doc_number=020869956&sequence=000002&line_number=0001&func_code=DB_RECORDS&service_type=MEDIA |3 Inhaltsverzeichnis |
| 999 | |a oai:aleph.bib-bvb.de:BVB01-020869956 | ||
Datensatz im Suchindex
| _version_ | 1804143677495312384 |
|---|---|
| adam_text | Contents
Foreword
xiii
Preface
xv
Why Bother with Use Cases?
What Are Use Cases All About?
xv
Who Should Be Interested in Use Cases?
xvi
How to Read This Book
xvii
Acknowledgments
xix
Part I Getting Started with Use-Case Modeling
1
Chapter
1 3
A Brief Introduction to Use-Case Modeling
Actors and Use Cases
3
Use-Case Diagrams
4
The Relationship Between Use Cases and Requirements
5
Types of Requirements
5
Functional and Nonfunctional Requirements
8
The Role of Use Cases
9
Use Cases Place Software Requirements in Context
10
To Use Case or Not to Use Case
12
When Are Use Cases Useful?
13
Use Cases Provide a Conceptual Model of the System
13
Use Cases Describe How the System Is Used and What It Does for Its Stakeholders
14
Does Everything the System Does Have to Be Described in a Use Case?
14
General Principles of Use-Case Modeling
15
Use Cases Do Not Exist in Isolation
15
Use Cases Are a Synthetic Rather Than an Analytic Technique
17
Rules of Thumb
17
Summary
18
VI
Contents
Chapter
2 ________________________________________ 19
Fundamentals of Use-Case Modeling
The Use-Case Model
20
The Basic Building Blocks of a Use-Case Model
21
Actors
11
Use Cases
23
Connecting Actors and Use Cases
25
Use-Case Diagrams
28
Brief Descriptions
29
Use-Case Descriptions
30
Supporting Artifacts
39
The Glossary and/or the Domain Model
39
Supplementary Specifications
43
Declarative and Special Requirements
46
Summary
47
Chapter
3 49
Establishing the Vision
Introducing Stakeholders and Users
50
What Are Stakeholders?
51
The Role of Stakeholders and Stakeholder Representatives
55
Users: A Very Important Class of Stakeholder
58
Stakeholders and Use-Case Modeling
61
Involving Stakeholders and Users in Your Project
63
Step
1:
Identify Stakeholder and User Types
63
Step
2:
Identify and Recruit the Stakeholder Representatives
64
Step
3:
Involve the Stakeholder Representatives in the Project
67
Creating a Shared Vision
68
Analyze the Problem
69
Understand the Key Stakeholder and User Needs
72
Describe the Features and Other Righ-Level Product Requirements
74
Provide an Overview of the Product
80
Bringing It All Together: The Vision Document
82
Do You Really Need to Do All of This?
85
Summary
85
Contents
vii
Chapter
4 87
Finding Actors and Use Cases
Finding Actors
88
Start by Identifying the Primary Actors
88
Work from the Specific to the General
89
Don t Forget the Supporting Actors
90
Consider All Existing Requirements Information
91
Remember That Actors Are Not Always People
91
Focus on the System Boundary
93
Don t Preempt the Design
94
Don t Confuse the Actors with the Devices They Use
95
When you Can t Find the Actors, Start with the Use Cases
96
Focus First on the Familiar
97
Evolve
the Set of Actors Alongside the Set of Use Cases
97
Documenting Actors
98
How to Name Actors
98
Don t Confuse Actors with Organizational Roles or Job Titles
99
Don t Overgeneralize
100
Give Every Actor a Brief Description
101
Characterize the Actors
101
Trace the Actors to the User Types, Stakeholders, and Stakeholder Roles
103
Finding Use Cases
104
Start by Identifying the Actor Goals
104
Consider the Information Needs of the System and Its Users
105
Don t Worry About Commonality (at least at first)
106
Don t Confuse Use Cases with Functions
106
Focus on Value
108
Derive the Use Cases from the System s Vision
109
Don t Forget the Supporting and Operational Use Cases
110
Evolve the Set of Use Cases Alongside the Set of Actors and the
Supplementary Specification 111
Documenting Use Cases 111
Associate the Use Cases to Their Actors 111
Name the Use Cases 111
Give Every Use Case a Brief Description
113
Outline the Use Cases
113
Trace the Use Cases to Stakeholders and Stakeholder Roles
116
Trace the Use Cases to the Features and Constraints
116
Summary
117
viii Contents
Chapter
5
Getting Started with a Use-Case Modeling Workshop
Reasons for Having a Workshop
119
To Transfer Expertise
120
To Build a Team
120
To Create Shared Understanding
120
To Tap into the Creative Power of a Group
121
Preparing for the Workshop
121
Train the Participants
121
Understand the Vision
122
Keep the Group Small and Involved
122
Vary the Composition of the Group
123
Select a Facilitator
124
Set Objectives for the Workshop
125
Schedule the Workshop and Organize the Facilities
126
Finding a Mentor
127
Find an Effective Communicator
127
Find a Skilled Motivator and Manager
127
Find a Mentor with Full Life-Cycle Experience
128
Don t Use the Mentor as a Crutch
129
Structuring the Workshop
129
Define the Ground Rules for the Workshop
129
Understand the Problem
131
Define the Boundary of the System
131
Identify Actors
133
Identify Use Cases
134
Consolidate the Model and Validate the Results
134
Wrap Up the Workshop and Plan the Next Steps
135
Supporting Activities
136
Capture Terminology in a Glossary
136
Capture Nonfunctional Requirements
138
Capture Issues, Risks, and Assumptions
138
Handling Common Problems
138
Avoid Functional Decomposition and Dataflow Modeling
139
Maintain Focus
139
Synthesize, Don t Analyze
140
Don t Describe What Happens Outside the System
141
Don t Just Draw Pictures
141
Don t Mix Business Use Cases and System Use Cases
142
Summary
143
Contents
ix
Part
II
Writing and Reviewing Use-Case Descriptions
145
Chapter
6 147
The Life Cycle of a Use Case
The Software Development Life Cycle
148
The Authoring Life Cycle
152
State
1:
Discovered
153
State
2:
Briefly Described
154
State
3: Bulleted
Outline
154
State
4:
Essential Outline
155
State
5:
Detailed Description
157
State
6:
Fully Described
159
Team Working
160
The Use-Case Modeling Process
161
Establish the Vision
163
Produce an Overview of the System
164
Reach Agreement on System Scope
164
PacMge the Use-Case Model
165
Address Areas of Instability and Author Stable Use Cases and
Supplementary Specifications
168
Consolidate and Review the Use-Case Model
169
Summary
169
Chapter
7 173
The Structure and Contents of a Use Case
Use Cases and System State
175
The System and External Events
175
The System State: More about Preconditions and Postconditions
177
How Use Cases Interact
180
The Side Effects of Using Preconditions
181
The Nature of the Flow of Events
182
The Structure of the Flow of Events
183
Managing Scope Using Alternative Flows
190
The Complexity of the Use-Case Model Versus the Complexity of the Design
192
Visualizing the Flow of Events
193
What Is a Scenario?
196
Wmt Is a Use-Case Realization?
197
Summary
199
Contents
Chapter
8__________________________________________ 201
Writing Use-Case Descriptions: An Overview
Who Writes Use-Case Descriptions?
202
Programmers Write Poor Descriptions
202
The Characteristics of a Good Use-Case Author
203
How Long Does It Take to Write a Use Case?
205
Getting Started
206
Use a Style Guide
206
Write Simply, Directly, and Deliberately
206
Treat the Use Case Like a Story
207
Make a Conscious Decision about the Depth of Detail Required
209
Describe What Happens When the Actors and the System Interact
210
Don t Rely on Just Text
210
Prototype the User Interface
211
Managing Detail
212
Good Use-Case Models Have No Levels
213
Adapt the Description to Your Intended Audience
214
Use the Glossary and Domain Model to Capture Definitions
215
Capture Business Rules in a Domain Model
218
Use Subflows to Simplify Complex Descriptions
219
Use Alternative Flows to Capture Unusual or Complex Behavior
220
Don t Fill Your Use Cases with
CRUD
221
Don t Be Afraid of Capturing the Detail
223
Summary
223
Chapter
9 225
Writing Use-Case Descriptions: Revisited
How Much Detail Is Enough?
226
Describing Preconditions
227
Deciding Whether a Precondition Is Needed
227
Describing Preconditions
227
Describing Postconditions
228
Deciding Whether Postconditions Are Needed
228
Describing Postconditions
229
Writing the Flow of Events
229
Writing the Basic
Нош
of Events
230
Рац
Attention to What s Behind the Screen
231
Contents
xi
Using the Glossary and the Domain Model
236
Writing Named Subflows
239
Writing Optional, Alternative, and Exception Flows
242
Identifying Alternative Flows
242
Representing Alternative Flows in Separate Sections
243
Naming Alternative Flows
244
Using Extension Points to Target Alternative Behavior
245
Describing Alternative Flows That Can Occur Anywhere in the Use Case
245
Resuming the Use Case After the Alternative Flow Completes
246
Alternative Flows for Alternative Flows and Named Subflows
247
Writing Special and Supplementary Specifications
247
Capturing Use-Case Scenarios
248
Summary
249
Chapter
10_________________________________________________252
Here There Be Dragons
Using Named Subflows and Alternative Flows to Structure Text
252
Defining Relationships Between Use Cases
252
Using the Include Relationship
253
Common Errors Using the Include Relationship
258
Using the Extends Relationship
259
Extension Points, Revisited
264
Evaluating the Resulting Use-Case Model
266
Using Generalization Between Use Cases
266
Defining Relationships Between Actors
272
Summary
274
Chapter
11_____________________________________________ 277
Reviewing Use Cases
Why Focus on Presenting and Reviewing Use Cases?
278
Types of Reviews
279
Informal Reviews
279
Formal Reviews
280
What to Review, and When to Review It
280
Who Should Review the Use Cases
282
Understanding the Audience
282
Setting Expectations
282
Preparing for the Review
283
xii Contents
Running the Review Meeting
284
Handling Issues
285
What to Look for When Reviewing
285
Reviewing Diagrams
285
Reviewing Brief Descriptions
287
Reviewing Use-Case Descriptions
287
Reviewing Preconditions and Postconditions
287
Reviewing the Glossary and Domain Model
288
The Role of Prototypes and
Storyboards in
Use-Case Reviews
288
Summary
288
Chapter
12____________________________________________
Wrapping Up
Use Cases and the Project Team
291
Developers and Use Cases
292
Testers and Use Cases
293
Use Cases and the User Experience
293
Use Cases and Documentation
294
Managers, Use Cases, and Planning
294
Use Cases Across the Life Cycle
295
Use
Ceses
and Iterative Development
296
Traceability, Completeness, and Coverage
298
What s Next?
300
Appendix
301
Glossary
331
Bibliography
337
Index
339
|
| any_adam_object | 1 |
| author | Bittner, Kurt Spence, Ian |
| author_facet | Bittner, Kurt Spence, Ian |
| author_role | aut aut |
| author_sort | Bittner, Kurt |
| author_variant | k b kb i s is |
| building | Verbundindex |
| bvnumber | BV036954962 |
| classification_rvk | ST 230 ZA 76000 |
| ctrlnum | (OCoLC)706966979 (DE-599)BVBBV036954962 |
| discipline | Informatik Agrar-/Forst-/Ernährungs-/Haushaltswissenschaft / Gartenbau |
| edition | 10. print. |
| format | Book |
| fullrecord | <?xml version="1.0" encoding="UTF-8"?><collection xmlns="http://www.loc.gov/MARC21/slim"><record><leader>01951nam a2200493 c 4500</leader><controlfield tag="001">BV036954962</controlfield><controlfield tag="003">DE-604</controlfield><controlfield tag="005">20110505 </controlfield><controlfield tag="007">t</controlfield><controlfield tag="008">110113s2008 xxua||| |||| 00||| eng d</controlfield><datafield tag="020" ind1=" " ind2=" "><subfield code="a">9780201709131</subfield><subfield code="9">978-0-201-70913-1</subfield></datafield><datafield tag="020" ind1=" " ind2=" "><subfield code="a">0201709139</subfield><subfield code="9">0-201-70913-9</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(OCoLC)706966979</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-599)BVBBV036954962</subfield></datafield><datafield tag="040" ind1=" " ind2=" "><subfield code="a">DE-604</subfield><subfield code="b">ger</subfield><subfield code="e">aacr</subfield></datafield><datafield tag="041" ind1="0" ind2=" "><subfield code="a">eng</subfield></datafield><datafield tag="044" ind1=" " ind2=" "><subfield code="a">xxu</subfield><subfield code="c">US</subfield></datafield><datafield tag="049" ind1=" " ind2=" "><subfield code="a">DE-355</subfield><subfield code="a">DE-11</subfield><subfield code="a">DE-2070s</subfield></datafield><datafield tag="084" ind1=" " ind2=" "><subfield code="a">ST 230</subfield><subfield code="0">(DE-625)143617:</subfield><subfield code="2">rvk</subfield></datafield><datafield tag="084" ind1=" " ind2=" "><subfield code="a">ZA 76000</subfield><subfield code="0">(DE-625)154306:</subfield><subfield code="2">rvk</subfield></datafield><datafield tag="100" ind1="1" ind2=" "><subfield code="a">Bittner, Kurt</subfield><subfield code="e">Verfasser</subfield><subfield code="4">aut</subfield></datafield><datafield tag="245" ind1="1" ind2="0"><subfield code="a">Use case modeling</subfield><subfield code="c">Kurt Bittner ; Ian Spence</subfield></datafield><datafield tag="250" ind1=" " ind2=" "><subfield code="a">10. print.</subfield></datafield><datafield tag="264" ind1=" " ind2="1"><subfield code="a">Boston, MA [u.a.]</subfield><subfield code="b">Addison Wesley</subfield><subfield code="c">2008</subfield></datafield><datafield tag="300" ind1=" " ind2=" "><subfield code="a">XIX, 347 S.</subfield><subfield code="b">Ill.</subfield></datafield><datafield tag="336" ind1=" " ind2=" "><subfield code="b">txt</subfield><subfield code="2">rdacontent</subfield></datafield><datafield tag="337" ind1=" " ind2=" "><subfield code="b">n</subfield><subfield code="2">rdamedia</subfield></datafield><datafield tag="338" ind1=" " ind2=" "><subfield code="b">nc</subfield><subfield code="2">rdacarrier</subfield></datafield><datafield tag="490" ind1="0" ind2=" "><subfield code="a">The Addison-Wesley object technology series</subfield></datafield><datafield tag="500" ind1=" " ind2=" "><subfield code="a">Includes bibliographical references (p. 337-338) and index</subfield></datafield><datafield tag="650" ind1="0" ind2="7"><subfield code="a">Requirements engineering</subfield><subfield code="0">(DE-588)4213997-1</subfield><subfield code="2">gnd</subfield><subfield code="9">rswk-swf</subfield></datafield><datafield tag="650" ind1="0" ind2="7"><subfield code="a">Softwareentwicklung</subfield><subfield code="0">(DE-588)4116522-6</subfield><subfield code="2">gnd</subfield><subfield code="9">rswk-swf</subfield></datafield><datafield tag="650" ind1="0" ind2="7"><subfield code="a">Projektmanagement</subfield><subfield code="0">(DE-588)4047441-0</subfield><subfield code="2">gnd</subfield><subfield code="9">rswk-swf</subfield></datafield><datafield tag="650" ind1="0" ind2="7"><subfield code="a">Anforderung</subfield><subfield code="0">(DE-588)4135103-4</subfield><subfield code="2">gnd</subfield><subfield code="9">rswk-swf</subfield></datafield><datafield tag="689" ind1="0" ind2="0"><subfield code="a">Requirements engineering</subfield><subfield code="0">(DE-588)4213997-1</subfield><subfield code="D">s</subfield></datafield><datafield tag="689" ind1="0" ind2="1"><subfield code="a">Softwareentwicklung</subfield><subfield code="0">(DE-588)4116522-6</subfield><subfield code="D">s</subfield></datafield><datafield tag="689" ind1="0" ind2=" "><subfield code="5">DE-604</subfield></datafield><datafield tag="689" ind1="1" ind2="0"><subfield code="a">Softwareentwicklung</subfield><subfield code="0">(DE-588)4116522-6</subfield><subfield code="D">s</subfield></datafield><datafield tag="689" ind1="1" ind2="1"><subfield code="a">Projektmanagement</subfield><subfield code="0">(DE-588)4047441-0</subfield><subfield code="D">s</subfield></datafield><datafield tag="689" ind1="1" ind2="2"><subfield code="a">Anforderung</subfield><subfield code="0">(DE-588)4135103-4</subfield><subfield code="D">s</subfield></datafield><datafield tag="689" ind1="1" ind2=" "><subfield code="5">DE-604</subfield></datafield><datafield tag="700" ind1="1" ind2=" "><subfield code="a">Spence, Ian</subfield><subfield code="e">Verfasser</subfield><subfield code="4">aut</subfield></datafield><datafield tag="856" ind1="4" ind2="2"><subfield code="m">Digitalisierung UB Regensburg</subfield><subfield code="q">application/pdf</subfield><subfield code="u">http://bvbr.bib-bvb.de:8991/F?func=service&doc_library=BVB01&local_base=BVB01&doc_number=020869956&sequence=000002&line_number=0001&func_code=DB_RECORDS&service_type=MEDIA</subfield><subfield code="3">Inhaltsverzeichnis</subfield></datafield><datafield tag="999" ind1=" " ind2=" "><subfield code="a">oai:aleph.bib-bvb.de:BVB01-020869956</subfield></datafield></record></collection> |
| id | DE-604.BV036954962 |
| illustrated | Illustrated |
| indexdate | 2024-07-09T22:51:28Z |
| institution | BVB |
| isbn | 9780201709131 0201709139 |
| language | English |
| oai_aleph_id | oai:aleph.bib-bvb.de:BVB01-020869956 |
| oclc_num | 706966979 |
| open_access_boolean | |
| owner | DE-355 DE-BY-UBR DE-11 DE-2070s |
| owner_facet | DE-355 DE-BY-UBR DE-11 DE-2070s |
| physical | XIX, 347 S. Ill. |
| publishDate | 2008 |
| publishDateSearch | 2008 |
| publishDateSort | 2008 |
| publisher | Addison Wesley |
| record_format | marc |
| series2 | The Addison-Wesley object technology series |
| spelling | Bittner, Kurt Verfasser aut Use case modeling Kurt Bittner ; Ian Spence 10. print. Boston, MA [u.a.] Addison Wesley 2008 XIX, 347 S. Ill. txt rdacontent n rdamedia nc rdacarrier The Addison-Wesley object technology series Includes bibliographical references (p. 337-338) and index Requirements engineering (DE-588)4213997-1 gnd rswk-swf Softwareentwicklung (DE-588)4116522-6 gnd rswk-swf Projektmanagement (DE-588)4047441-0 gnd rswk-swf Anforderung (DE-588)4135103-4 gnd rswk-swf Requirements engineering (DE-588)4213997-1 s Softwareentwicklung (DE-588)4116522-6 s DE-604 Projektmanagement (DE-588)4047441-0 s Anforderung (DE-588)4135103-4 s Spence, Ian Verfasser aut Digitalisierung UB Regensburg application/pdf http://bvbr.bib-bvb.de:8991/F?func=service&doc_library=BVB01&local_base=BVB01&doc_number=020869956&sequence=000002&line_number=0001&func_code=DB_RECORDS&service_type=MEDIA Inhaltsverzeichnis |
| spellingShingle | Bittner, Kurt Spence, Ian Use case modeling Requirements engineering (DE-588)4213997-1 gnd Softwareentwicklung (DE-588)4116522-6 gnd Projektmanagement (DE-588)4047441-0 gnd Anforderung (DE-588)4135103-4 gnd |
| subject_GND | (DE-588)4213997-1 (DE-588)4116522-6 (DE-588)4047441-0 (DE-588)4135103-4 |
| title | Use case modeling |
| title_auth | Use case modeling |
| title_exact_search | Use case modeling |
| title_full | Use case modeling Kurt Bittner ; Ian Spence |
| title_fullStr | Use case modeling Kurt Bittner ; Ian Spence |
| title_full_unstemmed | Use case modeling Kurt Bittner ; Ian Spence |
| title_short | Use case modeling |
| title_sort | use case modeling |
| topic | Requirements engineering (DE-588)4213997-1 gnd Softwareentwicklung (DE-588)4116522-6 gnd Projektmanagement (DE-588)4047441-0 gnd Anforderung (DE-588)4135103-4 gnd |
| topic_facet | Requirements engineering Softwareentwicklung Projektmanagement Anforderung |
| url | http://bvbr.bib-bvb.de:8991/F?func=service&doc_library=BVB01&local_base=BVB01&doc_number=020869956&sequence=000002&line_number=0001&func_code=DB_RECORDS&service_type=MEDIA |
| work_keys_str_mv | AT bittnerkurt usecasemodeling AT spenceian usecasemodeling |