Mastering the requirements process: getting requirements right
Gespeichert in:
| Beteiligte Personen: | , |
|---|---|
| Format: | Buch |
| Sprache: | Englisch |
| Veröffentlicht: |
Upper Saddle River, NJ [u.a.]
Addison-Wesley
2013
|
| Ausgabe: | 3. ed. |
| Schlagwörter: | |
| Links: | http://bvbr.bib-bvb.de:8991/F?func=service&doc_library=BVB01&local_base=BVB01&doc_number=025295534&sequence=000004&line_number=0001&func_code=DB_RECORDS&service_type=MEDIA |
| Beschreibung: | Includes bibliographical references and index |
| Umfang: | XXVI, 541 S. Ill., graph. Darst. |
| ISBN: | 9780321815743 0321815742 |
Internformat
MARC
| LEADER | 00000nam a2200000zc 4500 | ||
|---|---|---|---|
| 001 | BV040447823 | ||
| 003 | DE-604 | ||
| 005 | 20190923 | ||
| 007 | t| | ||
| 008 | 120928s2013 xxuad|| |||| 00||| eng d | ||
| 010 | |a 2012018961 | ||
| 020 | |a 9780321815743 |c hardcover : alk. paper |9 978-0-321-81574-3 | ||
| 020 | |a 0321815742 |9 0-321-81574-2 | ||
| 020 | |a 9780321815743 |9 978-0-321-81574-3 | ||
| 035 | |a (OCoLC)930802387 | ||
| 035 | |a (DE-599)BVBBV040447823 | ||
| 040 | |a DE-604 |b ger |e aacr | ||
| 041 | 0 | |a eng | |
| 044 | |a xxu |c US | ||
| 049 | |a DE-91G |a DE-473 |a DE-83 |a DE-384 |a DE-M347 |a DE-92 |a DE-2070s |a DE-739 |a DE-859 | ||
| 050 | 0 | |a TA190 | |
| 082 | 0 | |a 005.1068/4 | |
| 084 | |a SR 870 |0 (DE-625)143368: |2 rvk | ||
| 084 | |a ST 237 |0 (DE-625)143623: |2 rvk | ||
| 084 | |a DAT 335f |2 stub | ||
| 100 | 1 | |a Robertson, Suzanne |e Verfasser |4 aut | |
| 245 | 1 | 0 | |a Mastering the requirements process |b getting requirements right |c Suzanne Robertson ; James Robertson |
| 250 | |a 3. ed. | ||
| 264 | 1 | |a Upper Saddle River, NJ [u.a.] |b Addison-Wesley |c 2013 | |
| 300 | |a XXVI, 541 S. |b Ill., graph. Darst. | ||
| 336 | |b txt |2 rdacontent | ||
| 337 | |b n |2 rdamedia | ||
| 338 | |b nc |2 rdacarrier | ||
| 500 | |a Includes bibliographical references and index | ||
| 650 | 4 | |a Project management | |
| 650 | 4 | |a Computer software |x Development | |
| 650 | 0 | 7 | |a Requirements engineering |0 (DE-588)4213997-1 |2 gnd |9 rswk-swf |
| 650 | 0 | 7 | |a Anforderung |0 (DE-588)4135103-4 |2 gnd |9 rswk-swf |
| 650 | 0 | 7 | |a Projektmanagement |0 (DE-588)4047441-0 |2 gnd |9 rswk-swf |
| 650 | 0 | 7 | |a Systemanalyse |0 (DE-588)4116673-5 |2 gnd |9 rswk-swf |
| 650 | 0 | 7 | |a Softwareentwicklung |0 (DE-588)4116522-6 |2 gnd |9 rswk-swf |
| 689 | 0 | 0 | |a Softwareentwicklung |0 (DE-588)4116522-6 |D s |
| 689 | 0 | 1 | |a Projektmanagement |0 (DE-588)4047441-0 |D s |
| 689 | 0 | 2 | |a Anforderung |0 (DE-588)4135103-4 |D s |
| 689 | 0 | 3 | |a Systemanalyse |0 (DE-588)4116673-5 |D s |
| 689 | 0 | |5 DE-604 | |
| 689 | 1 | 0 | |a Requirements engineering |0 (DE-588)4213997-1 |D s |
| 689 | 1 | |5 DE-604 | |
| 700 | 1 | |a Robertson, James |e Verfasser |4 aut | |
| 856 | 4 | 2 | |m HBZ Datenaustausch |q application/pdf |u http://bvbr.bib-bvb.de:8991/F?func=service&doc_library=BVB01&local_base=BVB01&doc_number=025295534&sequence=000004&line_number=0001&func_code=DB_RECORDS&service_type=MEDIA |3 Inhaltsverzeichnis |
| 943 | 1 | |a oai:aleph.bib-bvb.de:BVB01-025295534 | |
Datensatz im Suchindex
| DE-BY-TUM_call_number | 0104 DAT 345f 2001 A 28714(3) 0303 DAT 335f 2009 L 256(3) |
|---|---|
| DE-BY-TUM_katkey | 1875435 |
| DE-BY-TUM_location | 01 03 |
| DE-BY-TUM_media_number | 040071469013 040071469068 040071469057 040071469046 040071469035 040071469024 |
| _version_ | 1821933903852601344 |
| adam_text | Titel: Mastering the requirements process
Autor: Robertson, Suzanne
Jahr: 2013
Contents
Preface to the Third Edition xxi
Foreword to the First Edition xxiii
Acknowledgments xxv
1 Some Fundamental Truths 1
in which we consider the essential contribution of requirements
Truth 1 1
Truth 2 2
Truth 3 3
Truth 4 4
Truth 5 5
Truth 6 6
Truth 7 7
Truth 8 7
Truth 9 8
Truth 10 8
Truth 11 9
What Are These Requirements Anyway? 9
Functional Requirements 10
Non-functional Requirements 10
Constraints 11
The Volere Requirements Process 11
2 The Requirements Process 13
in which we present a process for discovering requirements and
discuss how you might use it
The Requirements Process in Context 14
A Case Study 15
Project Blastoff 15
Trawling for Requirements 17
Quick and Dirty Modeling 19
Scenarios 20
Writing the Requirements 20
vii
viii • Contents
Quality Gateway
Reusing Requirements
Reviewing the Requirements
Iterative and Incremental Processes
Requirements Retrospective
Evolution of Requirements
The Template
The Snow Card
Your Own Requirements Process
Formality Guide
The Rest of This Book
3 Scoping the Business Problem
in which we establish a definition of the business area to be
changed, thereby ensuring that the project team has a clear
vision of what their project is meant to achieve
Project Blastoff
Formality Guide
Setting the Scope
Separate the Work from its Environment
IceBreaker
First-Cut Work Context
Scope, Stakeholders, and Goals
Stakeholders
The Sponsor
The Customer
Users: Understand Them
Other Stakeholders
Consultants
Management
Subject-Matter Experts
Core Team
Inspectors
Market Forces
Legal Experts
Negative Stakeholders
Industry Standard Setters
Public Opinion
Government ;
Special-Interest Groups
Technical Experts
Cultural Interests
Adjacent Systems
Finding the Stakeholders
Goals: What Do You Want to Achieve?
Purpose
Advantage
Measurement
22
23
23
24
25
26
27
29
31
32
33
35
35
38
38
40
41
42
43
44
45
47
48
50
51
51
51
51
52
52
52
52
52
53
53
53
53
53
53
54
54
55
56
56
Contents • ix
Constraints
Solution Constraints
Project Constraints
Naming Conventions and Definitions
How Much Is This Going to Cost?
Risks
To Go or Not to Go
Blastoff Meetings
Summary
4 Business Use Cases
in which we discuss a fail-safe way of partitioning the work and so
smooth the way for your requirements investigation
Understanding the Work 67
Formality Guide 69
Use Cases and Their Scope 69
The Scope of the Work 70
The Outside World 72
Business Events 73
Time-Triggered Business Events 74
Why Business Events and Business Use Cases Are a Good Idea 75
The System Cannot Be Assumed 76
Step Back 77
Finding the Business Events 78
Business Use Cases 80
Business Use Cases and Product Use Cases 82
Actors 84
Summary 85
5 Investigating the Work 87
in which we come to an understanding of what the business is
doing, and start to think about what it might like to do
Trawling the Business 87
Formality Guide /. 89
Trawl for Knowledge 89
The Business Analyst 91
Trawling and Business Use Cases 92
The Brown Cow Model 93
The Current Way of Doing Things (How-Now) 94
Apprenticing 98
Business Use Case Workshops 99
Outcome 101
Scenarios 101
Business Rules 101
Interviewing the Stakeholders 102
Asking the Right Questions 104
Listening to the Answers 105
59
59
60
60
61
62
63
64
65
67
x • Contents
Looking for Reusable Requirements 106
Quick and Dirty Process Modeling 107
Prototypes and Sketches 109
Low-Fidelity Prototypes 111
High-Fidelity Prototypes 115
Mind Maps 116
The Murder Book 119
Video and Photographs 120
Wikis, Blogs, Discussion Forums 122
Document Archeology 123
Family Therapy 125
Choosing the Best Trawling Technique 125
Finally... 127
6 Scenarios 129
in which we look at scenarios, and how the business analyst
uses them to communicate with the stakeholders
Formality Guide 129
Scenarios 130
The Essence of the Business 135
Diagramming the Scenario 138
Alternatives 139
Exceptions 140
What if? Scenarios 142
Misuse Cases and Negative Scenarios 142
Scenario Template 143
Summary 145
7 Understanding the Real Problem 147
in which we think above the line to find the true essence of
the business, and so deliver the right product—one that solves
the right problem
Formality Guide 149
The Brown Cow Model: Thinking Above the Line 149
The Essence 150
Abstraction 153
Swim Lanes Begone 154
Solving the Right Problem 156
Moving into the Future 157
How to Be Innovative 160
Systemic Thinking 162
Value 165
Personas 166
Challenging Constraints 169
Innovation Workshops 171
Brainstorming 173
Back to the Future 174
Contents • xi
8 Starting the Solution 177
in which we bring the essence of the business into the
technological world of the implementation
Iterative Development 179
Essential Business 179
Determine the Extent of the Product 180
Consider the Users 181
Designing the User Experience 183
Innovation 184
Convenience 184
Connections 185
Information 186
Feeling 187
Sketching the Interface 188
The Real Origin of the Business Event 189
Adjacent Systems and External Technology 190
Active Adjacent Systems 190
Autonomous Adjacent Systems 192
Cooperative Adjacent Systems 193
Cost, Benefit, and Risks 194
Document Your Design Decisions 195
Product Use Case Scenarios 196
Putting It All Together 199
9 Strategies for Today s Business Analyst 203
in which we consider strategies for the business analyst to guide
requirements discovery in today s changing environments
Balancing Knowledge, Activities, and People
Common Project Requirements Profiles
How Much Knowledge Is Needed Before Each Breakout?
External Strategy
Conception to Scoping
Scoping to Work Investigation
Work Investigation to Product Determination
Work Investigation to Atomic Requirements Definition
Work Investigation to Building
Product Determination to Atomic Requirements Definition
Product Determination to Construction
Atomic Requirements Definition to Building
Iterative Strategy
Conception to Scoping
Scoping to Work Investigation
Work Investigation to Product Determination
Work Investigation to Requirements Definition
Product Determination to Requirements Definition
Requirements Definition to Construction
Sequential Strategy
Conception to Scoping
Scoping to Work Investigation
204
204
205
206
207
207
208
208
208
209
209
209
210
210
210
211
211
212
212
212
213
213
xii • Contents
Work Investigation to Product Determination 214
Product Determination to Requirements Definition 214
Requirements Definition to Building 214
Your Own Strategy 215
Sharpening Your Requirements Skills 215
No Longer a Stenographer 216
Limiting the Number of Requirements That Are Written 217
Reusing Requirements 217
Innovation and the Business Analyst 218
Looking for Business Rules 218
The Business Analyst as Ideas Broker 219
Systemic Thinking and the Business Analyst 220
The Business Analyst as Visualizer 221
Summary 222
10 Functional Requirements 223
in which we look at those requirements that cause the product
to do something
11
Formality Guide 224
Functional Requirements 225
Uncovering the Functional Requirements 225
Level of Detail or Granularity 228
Description and Rationale 229
Data, Your Secret Weapon 231
Data Models 231
Data Dictionary 232
Exceptions and Alternatives 233
Conditional Requirements 234
Avoiding Ambiguity 234
Technological Requirements 237
Grouping Requirements 237
Alternatives to Functional Requirements 238
Scenarios 239
User Stories 239
Business Process Models 240
Requirements for COTS 241
Summary 242
Non-functional Requirements 245
in which we look at the requirements that specify how well
your product does what it does
An Introduction to Non-functional Requirements 246
Formality Guide 246
Functional Versus Non-functional Requirements 247
Use Cases and Non-functional Requirements 248
The Non-functional Requirements Types 249
Look and Feel Requirements: Type 10 250
Usability and Humanity Requirements: Type 11 253
Contents • xiii
Performance Requirements: Type 12 257
Operational and Environmental Requirements: Type 13 259
Maintainability and Support Requirements: Type 14 261
Security Requirements: Type 15 262
Access 263
Privacy 263
Integrity 264
Auditing 265
... And No More 265
Cultural Requirements: Type 16 266
Legal Requirements: Type 17 268
Sarbanes-Oxley Act 269
Other Legal Obligations 270
Standards 271
Finding the Non-functional Requirements 271
Blogging the Requirements 271
Use Cases 272
The Template 274
Prototypes and Non-functional Requirements 274
The Client 275
Don t Write a Solution 276
Summary 277
12 Fit Criteria and Rationale 279
in which we show how measuring requirements makes them
unambiguous, understandable, communicable; and testable
Formality Guide 280
Why Does Fit Need a Criterion? 280
The Rationale for the Rationale 282
Deriving Fit Criteria 284
Scale of Measurement 285
Fit Criteria for Non-functional Requirements 286
Product Failure 288
Subjective Tests 289
Standards 289
Look and Feel Requirements 290
Usability and Humanity Requirements 291
Performance Requirements 292
Operational Requirements 293
Maintainability Requirements 294
Security Requirements 294
Cultural Requirements 294
Legal Requirements 295
Fit Criteria for Functional Requirements 295
Test Cases 296
Forms of Fit Criteria 296
Defining the Data 297
Graphic Fit Criteria 297
Decision Tables 297
Graphs 298
xiv • Contents
Use Cases and Fit Criteria 299
Fit Criterion for Project Purpose 299
Fit Criteria for Solution Constraints 300
Summary 301
13 The Quality Gateway 303
in which we prevent unsuitable requirements from becoming
part of the specification
Formality Guide 304
Requirements Quality 305
Using the Quality Gateway 306
Within Scope? 307
Relevancy 309
Testing Completeness 311
Are There Any Missing Attributes? 311
Meaningful to Stakeholders? 312
Testing the Fit Criterion 312
Consistent Terminology 313
Viable within Constraints? 314
Requirement or Solution? 316
Requirement Value 316
Gold Plating 317
Requirements Creep 317
Implementing the Quality Gateway 319
Alternative Quality Gateways 320
Summary 321
14 Requirements and Iterative Development 323
in which we look at how to discover and implement requirements
in an iterative development environment
The Need for Iterative Development 323
An Iterative Requirements Process 324
The Work 324
Analyze Business Needs 324
Write User Stories 325
Develop Product 326
Business Value Analysis and Prioritization 327
How to Write a Good User Story 329
Questions to Ask 329
Formalizing Your User Stories 331
Fleshing out the Story 332
Iterative Requirements Roles 333
Business Knowledge 333
Analytical and Communication Knowledge 334
Technical Knowledge 334
Summary 335
Contents • xv
15 Reusing Requirements 337
in which we look for requirements that have already been
written and explore ways to make use of them
What Is Reusing Requirements? 338
Sources of Reusable Requirements 341
Requirements Patterns 342
Christopher Alexander s Patterns 343
A Business Event Pattern 344
Context of Event Response 344
Processing for Event Response 345
Data for Event Response 345
Forming Patterns by Abstracting 346
Patterns for Specific Domains 348
Patterns Across Domains 349
Domain Analysis 351
Summary 351
16 Communicating the Requirements 353
in which we turn the requirements into communicable form
Formality Guide 353
Turning Potential Requirements into Written Requirements 354
Knowledge Versus Specification 354
The Volere Requirements Specification Template 357
Template Table of Contents 357
Template Divisions 358
Discovering Atomic Requirements 359
Snow Cards 359
Attributes of Atomic Requirements 361
Requirement Number 361
Requirement Type 361
Event/BUC/PUC # 361
Description 362
Rationale 362
Originator 363
Fit Criterion 363
Customer Satisfaction and Customer Dissatisfaction 363
Priority 364
Conflicts 364
Supporting Materials 365
History 365
Assembling the Specification 365
Automated Requirements Tools 3 66
Functional Requirements 367
Non-functional Requirements 368
Project Issues 369
Summary 369
xvi • Contents
17 Requirements Completeness 371
in which we decide whether our specification is complete,
and set the priorities of the requirements
Formality Guide 372
Reviewing the Specification 373
Inspections 373
Find Missing Requirements 374
Have All Business Use Cases Been Discovered? 376
1. Define the Scope 376
2. Identify Business Events and Non-events 377
Non-events 378
3. Model the Business Use Case 378
4. Define the Business Data 378
5. CRUD Check 380
6. Check for Custodial Processes 381
Repeat Until Done 382
Prioritizing the Requirements 382
Prioritization Factors 382
When to Prioritize 383
Requirement Priority Grading 384
Prioritization Spreadsheet 385
Conflicting Requirements 386
Ambiguous Specifications 388
Risk Assessment 388
Project Drivers 389
Project Constraints 390
Functional Requirements 390
Measure the Required Cost 391
Summary 391
Appendix A Volere Requirements Specification Template 393
a guide for writing a rigorous and complete requirements
specification
Contents 393
Project Drivers 393
Project Constraints 393
Functional Requirements 393
Non-functional Requirements 393
Project Issues 394
Use of This Template 394
Volere 394
Requirements Types 395
Testing Requirements 396
Atomic Requirements Shell 396
1. The Purpose of the Project 397
la. The User Business or Background of the Project Effort 397
lb. Goals of the Project 398
2. The Stakeholders 400
2a. The Client 400
Contents • xvii
2b. The Customer 401
2c. Other Stakeholders 401
2d. The Hands-on Users of the Product 403
2e. Personas 404
2f. Priorities Assigned to Users 405
2g. User Participation 406
2h. Maintenance Users and Service Technicians 407
3. Mandated Constraints 407
3a. Solution Constraints 407
3b. Implementation Environment of the Current System 409
3c. Partner or Collaborative Applications 410
3d. Off-the-Shelf Software 410
3e. Anticipated Workplace Environment 412
3f. Schedule Constraints 413
3g. Budget Constraints 414
3h. Enterprise Constraints 414
4. Naming Conventions and Terminology 415
4a. Definitions of All Terms, Including Acronyms, Used by
Stakeholders Involved in the Project 415
5. Relevant Facts and Assumptions 416
5a. Relevant Facts 417
5b. Business Rules 417
5c. Assumptions 418
6. The Scope of the Work 420
6a. The Current Situation 420
6b. The Context of the Work 420
6c. Work Partitioning 422
6d. Specifying a Business Use Case 424
7. Business Data Model and Data Dictionary 425
7a. Data Model 425
7b. Data Dictionary 427
8. The Scope of the Product 429
8a. Product Boundary 429
8b. Product Use Case Table 431
8c. Individual Product Use Cases 432
9. Functional and Data Requirements 433
9a. Functional Requirements 433
Non-functional Requirements 435
10. Look and Feel Requirements 435
10a. Appearance Requirements 435
10b. Style Requirements 436
11. Usability and Humanity Requirements 437
11a. Ease of Use Requirements 437
lib. Personalization and Internationalization Requirements 438
11c. Learning Requirements 439
lid. Understandability and Politeness Requirements 440
lie. Accessibility Requirements 441
12. Performance Requirements 441
12a. Speed and Latency Requirements 441
12b. Safety-Critical Requirements 442
12c. Precision or Accuracy Requirements 443
xviii • Contents
12d. Reliability and Availability Requirements 444
12e. Robustness or Fault-Tolerance Requirements 445
12f. Capacity Requirements 445
12g. Scalability or Extensibility Requirements 446
12h. Longevity Requirements 446
13. Operational and Environmental Requirements 447
13a. Expected Physical Environment 447
13b. Requirements for Interfacing with Adjacent Systems 447
13c. Productization Requirements 448
13d. Release Requirements 449
14. Maintainability and Support Requirements 449
14a. Maintenance Requirements 449
14b. Supportability Requirements 450
14c. Adaptability Requirements 450
15. Security Requirements 451
15a. Access Requirements 451
15b. Integrity Requirements 452
15c. Privacy Requirements 453
15d. Audit Requirements 454
15e. Immunity Requirements 454
16. Cultural Requirements 454
16a. Cultural Requirements 454
17. Legal Requirements 455
17a. Compliance Requirements 455
17b. Standards Requirements 456
Project Issues 457
18. Open Issues 457
19. Off-the-Shelf Solutions 458
19a. Ready-Made Products 458
19b. Reusable Components 459
19c. Products That Can Be Copied 459
20. New Problems 460
20a. Effects on the Current Environment 460
20b. Effects on the Installed Systems 460
20c. Potential User Problems 461
20d. Limitations in the Anticipated Implementation Environment
That May Inhibit the New Product 461
20e. Follow-Up Problems 462
21. Tasks 462
21a. Project Planning 462
21b. Planning of the Development Phases 463
22. Migration to the New Product 463
22a. Requirements for Migration to the New Product 464
22b. Data That Must Be Modified or Translated for the New System 465
23. Risks 465
24. Costs 467
25. User Documentation and Training 468
25a. User Documentation Requirements 468
25b. Training Requirements 469
26. Waiting Room 470
27. Ideas for Solutions 471
Contents • xix
Appendix B Stakeholder Management Templates 473
Stakeholder Map 473
Stakeholder Template 475
Appendix C Function Point Counting: A Simplified
Introduction 479
in which we look at a way to accurately measure the size or
functionality of the work area, with a view toward using the
measurement to estimate the requirements effort
Measuring the Work 479
A Quick Primer on Counting Function Points 481
Scope of the Work 481
Data Stored by the Work 482
Business Use Cases 483
Counting Function Points for Business Use Cases 484
Counting Input Business Use Cases 484
Counting Output Business Use Cases 485
Counting Time-Triggered Business Use Cases 487
Counting the Stored Data 489
Internal Stored Data 489
Externally Stored Data 490
Adjust for What You Don t Know 492
Now That I Have Counted Function Points, What s Next? 492
Appendix D Volere Requirements Knowledge Model 495
Definitions of Requirements Knowledge Classes and Associations 495
Knowledge Classes 496
Associations 505
Knowledge Model Annotated with Template Section Numbers 508
Glossary 511
Bibliography 517
Index 523
|
| any_adam_object | 1 |
| author | Robertson, Suzanne Robertson, James |
| author_facet | Robertson, Suzanne Robertson, James |
| author_role | aut aut |
| author_sort | Robertson, Suzanne |
| author_variant | s r sr j r jr |
| building | Verbundindex |
| bvnumber | BV040447823 |
| callnumber-first | T - Technology |
| callnumber-label | TA190 |
| callnumber-raw | TA190 |
| callnumber-search | TA190 |
| callnumber-sort | TA 3190 |
| callnumber-subject | TA - General and Civil Engineering |
| classification_rvk | SR 870 ST 237 |
| classification_tum | DAT 335f |
| ctrlnum | (OCoLC)930802387 (DE-599)BVBBV040447823 |
| dewey-full | 005.1068/4 |
| dewey-hundreds | 000 - Computer science, information, general works |
| dewey-ones | 005 - Computer programming, programs, data, security |
| dewey-raw | 005.1068/4 |
| dewey-search | 005.1068/4 |
| dewey-sort | 15.1068 14 |
| dewey-tens | 000 - Computer science, information, general works |
| discipline | Informatik |
| edition | 3. ed. |
| format | Book |
| fullrecord | <?xml version="1.0" encoding="UTF-8"?><collection xmlns="http://www.loc.gov/MARC21/slim"><record><leader>02319nam a2200577zc 4500</leader><controlfield tag="001">BV040447823</controlfield><controlfield tag="003">DE-604</controlfield><controlfield tag="005">20190923 </controlfield><controlfield tag="007">t|</controlfield><controlfield tag="008">120928s2013 xxuad|| |||| 00||| eng d</controlfield><datafield tag="010" ind1=" " ind2=" "><subfield code="a">2012018961</subfield></datafield><datafield tag="020" ind1=" " ind2=" "><subfield code="a">9780321815743</subfield><subfield code="c">hardcover : alk. paper</subfield><subfield code="9">978-0-321-81574-3</subfield></datafield><datafield tag="020" ind1=" " ind2=" "><subfield code="a">0321815742</subfield><subfield code="9">0-321-81574-2</subfield></datafield><datafield tag="020" ind1=" " ind2=" "><subfield code="a">9780321815743</subfield><subfield code="9">978-0-321-81574-3</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(OCoLC)930802387</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-599)BVBBV040447823</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-91G</subfield><subfield code="a">DE-473</subfield><subfield code="a">DE-83</subfield><subfield code="a">DE-384</subfield><subfield code="a">DE-M347</subfield><subfield code="a">DE-92</subfield><subfield code="a">DE-2070s</subfield><subfield code="a">DE-739</subfield><subfield code="a">DE-859</subfield></datafield><datafield tag="050" ind1=" " ind2="0"><subfield code="a">TA190</subfield></datafield><datafield tag="082" ind1="0" ind2=" "><subfield code="a">005.1068/4</subfield></datafield><datafield tag="084" ind1=" " ind2=" "><subfield code="a">SR 870</subfield><subfield code="0">(DE-625)143368:</subfield><subfield code="2">rvk</subfield></datafield><datafield tag="084" ind1=" " ind2=" "><subfield code="a">ST 237</subfield><subfield code="0">(DE-625)143623:</subfield><subfield code="2">rvk</subfield></datafield><datafield tag="084" ind1=" " ind2=" "><subfield code="a">DAT 335f</subfield><subfield code="2">stub</subfield></datafield><datafield tag="100" ind1="1" ind2=" "><subfield code="a">Robertson, Suzanne</subfield><subfield code="e">Verfasser</subfield><subfield code="4">aut</subfield></datafield><datafield tag="245" ind1="1" ind2="0"><subfield code="a">Mastering the requirements process</subfield><subfield code="b">getting requirements right</subfield><subfield code="c">Suzanne Robertson ; James Robertson</subfield></datafield><datafield tag="250" ind1=" " ind2=" "><subfield code="a">3. ed.</subfield></datafield><datafield tag="264" ind1=" " ind2="1"><subfield code="a">Upper Saddle River, NJ [u.a.]</subfield><subfield code="b">Addison-Wesley</subfield><subfield code="c">2013</subfield></datafield><datafield tag="300" ind1=" " ind2=" "><subfield code="a">XXVI, 541 S.</subfield><subfield code="b">Ill., graph. Darst.</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="500" ind1=" " ind2=" "><subfield code="a">Includes bibliographical references and index</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Project management</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Computer software</subfield><subfield code="x">Development</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">Anforderung</subfield><subfield code="0">(DE-588)4135103-4</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">Systemanalyse</subfield><subfield code="0">(DE-588)4116673-5</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="689" ind1="0" 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="0" 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="0" 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="0" ind2="3"><subfield code="a">Systemanalyse</subfield><subfield code="0">(DE-588)4116673-5</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">Requirements engineering</subfield><subfield code="0">(DE-588)4213997-1</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">Robertson, James</subfield><subfield code="e">Verfasser</subfield><subfield code="4">aut</subfield></datafield><datafield tag="856" ind1="4" ind2="2"><subfield code="m">HBZ Datenaustausch</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=025295534&sequence=000004&line_number=0001&func_code=DB_RECORDS&service_type=MEDIA</subfield><subfield code="3">Inhaltsverzeichnis</subfield></datafield><datafield tag="943" ind1="1" ind2=" "><subfield code="a">oai:aleph.bib-bvb.de:BVB01-025295534</subfield></datafield></record></collection> |
| id | DE-604.BV040447823 |
| illustrated | Illustrated |
| indexdate | 2024-12-20T16:15:13Z |
| institution | BVB |
| isbn | 9780321815743 0321815742 |
| language | English |
| lccn | 2012018961 |
| oai_aleph_id | oai:aleph.bib-bvb.de:BVB01-025295534 |
| oclc_num | 930802387 |
| open_access_boolean | |
| owner | DE-91G DE-BY-TUM DE-473 DE-BY-UBG DE-83 DE-384 DE-M347 DE-92 DE-2070s DE-739 DE-859 |
| owner_facet | DE-91G DE-BY-TUM DE-473 DE-BY-UBG DE-83 DE-384 DE-M347 DE-92 DE-2070s DE-739 DE-859 |
| physical | XXVI, 541 S. Ill., graph. Darst. |
| publishDate | 2013 |
| publishDateSearch | 2013 |
| publishDateSort | 2013 |
| publisher | Addison-Wesley |
| record_format | marc |
| spellingShingle | Robertson, Suzanne Robertson, James Mastering the requirements process getting requirements right Project management Computer software Development Requirements engineering (DE-588)4213997-1 gnd Anforderung (DE-588)4135103-4 gnd Projektmanagement (DE-588)4047441-0 gnd Systemanalyse (DE-588)4116673-5 gnd Softwareentwicklung (DE-588)4116522-6 gnd |
| subject_GND | (DE-588)4213997-1 (DE-588)4135103-4 (DE-588)4047441-0 (DE-588)4116673-5 (DE-588)4116522-6 |
| title | Mastering the requirements process getting requirements right |
| title_auth | Mastering the requirements process getting requirements right |
| title_exact_search | Mastering the requirements process getting requirements right |
| title_full | Mastering the requirements process getting requirements right Suzanne Robertson ; James Robertson |
| title_fullStr | Mastering the requirements process getting requirements right Suzanne Robertson ; James Robertson |
| title_full_unstemmed | Mastering the requirements process getting requirements right Suzanne Robertson ; James Robertson |
| title_short | Mastering the requirements process |
| title_sort | mastering the requirements process getting requirements right |
| title_sub | getting requirements right |
| topic | Project management Computer software Development Requirements engineering (DE-588)4213997-1 gnd Anforderung (DE-588)4135103-4 gnd Projektmanagement (DE-588)4047441-0 gnd Systemanalyse (DE-588)4116673-5 gnd Softwareentwicklung (DE-588)4116522-6 gnd |
| topic_facet | Project management Computer software Development Requirements engineering Anforderung Projektmanagement Systemanalyse Softwareentwicklung |
| url | http://bvbr.bib-bvb.de:8991/F?func=service&doc_library=BVB01&local_base=BVB01&doc_number=025295534&sequence=000004&line_number=0001&func_code=DB_RECORDS&service_type=MEDIA |
| work_keys_str_mv | AT robertsonsuzanne masteringtherequirementsprocessgettingrequirementsright AT robertsonjames masteringtherequirementsprocessgettingrequirementsright |
Inhaltsverzeichnis
Paper/Kapitel scannen lassen
Paper/Kapitel scannen lassen
Teilbibliothek Mathematik & Informatik
| Signatur: |
0104 DAT 345f 2001 A 28714(3)
Lageplan |
|---|---|
| Exemplar 1 | Nicht ausleihbar Am Standort |
Teilbibliothek Chemie, Lehrbuchsammlung
| Signatur: |
0303 DAT 335f 2009 L 256(3)
Lageplan |
|---|---|
| Exemplar 1 | Ausleihbar Am Standort |
| Exemplar 2 | Ausleihbar Am Standort |
| Exemplar 3 | Ausleihbar Am Standort |
| Exemplar 4 | Ausleihbar Am Standort |
| Exemplar 5 | Ausleihbar Am Standort |