Software requirements:
Gespeichert in:
| Hauptverfasser: | , |
|---|---|
| Format: | Buch |
| Sprache: | English |
| Veröffentlicht: |
Redmond, Washington
Microsoft Press
[2013]
|
| Ausgabe: | Third edition |
| Schriftenreihe: | Best practices
|
| Schlagworte: | |
| Online-Zugang: | Inhaltsverzeichnis |
| Beschreibung: | xxxii, 637 Seiten Illustrationen |
| ISBN: | 9780735679665 0735679665 |
Internformat
MARC
| LEADER | 00000nam a22000002c 4500 | ||
|---|---|---|---|
| 001 | BV041342863 | ||
| 003 | DE-604 | ||
| 005 | 20241217 | ||
| 007 | t| | ||
| 008 | 131004s2013 xx a||| |||| 00||| eng d | ||
| 010 | |a 2013942928 | ||
| 020 | |a 9780735679665 |c kart. : ca. EUR 56.00 (DE) |9 978-0-7356-7966-5 | ||
| 020 | |a 0735679665 |9 0-7356-7966-5 | ||
| 035 | |a (OCoLC)862807775 | ||
| 035 | |a (DE-599)BVBBV041342863 | ||
| 040 | |a DE-604 |b ger |e rda | ||
| 041 | 0 | |a eng | |
| 049 | |a DE-91G |a DE-473 |a DE-2070s |a DE-20 |a DE-19 |a DE-739 |a DE-860 |a DE-703 | ||
| 050 | 0 | |a QA76.76.D47 W517 2013 | |
| 082 | 0 | |a 005.1 | |
| 084 | |a ST 230 |0 (DE-625)143617: |2 rvk | ||
| 084 | |a DAT 335f |2 stub | ||
| 100 | 1 | |a Wiegers, Karl E. |d 1953- |e Verfasser |0 (DE-588)130013692 |4 aut | |
| 245 | 1 | 0 | |a Software requirements |c Karl Wiegers and Joy Beatty |
| 250 | |a Third edition | ||
| 264 | 1 | |a Redmond, Washington |b Microsoft Press |c [2013] | |
| 300 | |a xxxii, 637 Seiten |b Illustrationen | ||
| 336 | |b txt |2 rdacontent | ||
| 337 | |b n |2 rdamedia | ||
| 338 | |b nc |2 rdacarrier | ||
| 490 | 0 | |a Best practices | |
| 650 | 4 | |a Computer software |v Development | |
| 650 | 0 | 7 | |a Softwareentwicklung |0 (DE-588)4116522-6 |2 gnd |9 rswk-swf |
| 650 | 0 | 7 | |a Anforderungsdefinition |0 (DE-588)4193804-5 |2 gnd |9 rswk-swf |
| 650 | 0 | 7 | |a Software Engineering |0 (DE-588)4116521-4 |2 gnd |9 rswk-swf |
| 650 | 0 | 7 | |a Requirements engineering |0 (DE-588)4213997-1 |2 gnd |9 rswk-swf |
| 689 | 0 | 0 | |a Softwareentwicklung |0 (DE-588)4116522-6 |D s |
| 689 | 0 | 1 | |a Requirements engineering |0 (DE-588)4213997-1 |D s |
| 689 | 0 | 2 | |a Software Engineering |0 (DE-588)4116521-4 |D s |
| 689 | 0 | |8 1\p |5 DE-604 | |
| 689 | 1 | 0 | |a Softwareentwicklung |0 (DE-588)4116522-6 |D s |
| 689 | 1 | 1 | |a Anforderungsdefinition |0 (DE-588)4193804-5 |D s |
| 689 | 1 | |8 2\p |5 DE-604 | |
| 700 | 1 | |a Beatty, Joy |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=026791596&sequence=000001&line_number=0001&func_code=DB_RECORDS&service_type=MEDIA |3 Inhaltsverzeichnis |
| 883 | 1 | |8 1\p |a cgwrk |d 20201028 |q DE-101 |u https://d-nb.info/provenance/plan#cgwrk | |
| 883 | 1 | |8 2\p |a cgwrk |d 20201028 |q DE-101 |u https://d-nb.info/provenance/plan#cgwrk | |
| 943 | 1 | |a oai:aleph.bib-bvb.de:BVB01-026791596 | |
Datensatz im Suchindex
| _version_ | 1818677540935434240 |
|---|---|
| adam_text |
Titel: Software requirements
Autor: Wiegers, Karl E
Jahr: 2013
j Microsoft
Software Requirements,
Third Edition
Karl Wiegers and Joy Beatty
Contents
Introduction xxv
Acknowledgments xxxi
PART I SOFTWARE REQUIREMENTS: WHAT, WHY, AND WHO
Chapter 1 The essential software requirement 3
Software requirements defined 5
Some interpretations of "requirement" 6
Levels and types of requirements 7
Working with the three levels 12
Product vs. project requirements 14
Requirements development and management 15
Requirements development 15
Requirements management 17
Every project has requirements 18
When bad requirements happen to good people 19
Insufficient user involvement 20
Inaccurate planning 20
Creeping user requirements 20
Ambiguous requirements 21
Gold plating 21
Overlooked stakeholders 22
Benefits from a high-quality requirements process 22
Chapter 2 Requirements from the customer's perspective 25
The expectation gap 26
Who is the customer? 27
The customer-development partnership 29
Requirements Bill of Rights for Software Customers 31
Requirements Bill of Responsibilities for Software Customers 33
Creating a culture that respects requirements 36
Identifying decision makers 38
Reaching agreement on requirements 38
The requirements baseline 39
What if you don't reach agreement? 40
Agreeing on requirements on agile projects 41
Chapter 3 Good practices for requirements engineering 43
A requirements development process framework 45
Good practices: Requirements elicitation 48
Good practices: Requirements analysis 50
Good practices: Requirements specification 51
Good practices: Requirements validation 52
Good practices: Requirements management 53
Good practices: Knowledge 54
Good practices: Project management 56
Getting started with new practices 57
Chapter 4 The business analyst 61
The business analyst role 62
The business analyst's tasks 63
Essential analyst skills 65
Essential analyst knowledge 68
The making of a business analyst 68
The former user 68
The former developer or tester 69
The former (or concurrent) project manager 70
The subject matter expert 70
The rookie 71
The analyst role on agile projects 71
Creating a collaborative team 72
x Contents
PART il REQUIREMENTS DEVELOPMENT
Chapter 5 Establishing the business requirements 77
Defining business requirements 78
Identifying desired business benefits 78
Product vision and project scope 78
Conflicting business requirements 80
Vision and scope document 81
1. Business requirements 83
2. Scope and limitations 88
3. Business context 90
Scope representation techniques 92
Context diagram 92
Ecosystem map 94
Feature tree 95
Event list 96
Keeping the scope in focus 97
Using business objectives to make scoping decisions 97
Assessing the impact of scope changes 98
Vision and scope on agile projects 98
Using business objectives to determine completion 99
Chapter 6 Finding the voice of the user 101
User classes 102
Classifying users 102
Identifying your user classes 105
User personas 107
Connecting with user representatives 108
The product champion 109
External product champions 110
Product champion expectations I l l
Multiple product champions 112
Selling the product champion idea 113
Product champion traps to avoid 114
User representation on agile projects 115
Resolving conflicting requirements 116
Chapter 7 Requirements eiicitation 119
Requirements eiicitation techniques 121
Interviews 121
Workshops 122
Focus groups 124
Observations 125
Questionnaires 127
System interface analysis 127
User interface analysis 128
Document analysis 128
Planning eiicitation on your project 129
Preparing for eiicitation 130
Performing eiicitation activities 132
Following up after eiicitation 134
Organizing and sharing the notes 134
Documenting open issues 135
Classifying customer input 135
How do you know when you're done? 138
Some cautions about eiicitation 139
Assumed and implied requirements 140
Finding missing requirements 141
Chapter 8 Understanding user requirements 143
Use cases and user stories 144
The use case approach 147
Use cases and usage scenarios 149
Identifying use cases 157
Exploring use cases 158
Validating use cases 160
Use cases and functional requirements 161
Use case traps to avoid 163
Benefits of usage-centric requirements 164
Chapter 9 Playing by the rules 167
A business rules taxonomy 169
Facts 170
Constraints 170
Action enablers 171
Inferences 173
Computations 173
Atomic business rules 174
Documenting business rules 175
Discovering business rules 177
Business rules and requirements 178
Tying everything together 180
Chapter 10 Documenting the requirements 181
The software requirements specification 183
Labeling requirements 186
Dealing with incompleteness 188
User interfaces and the SRS 189
A software requirements specification template 190
1. Introduction 192
2. Overall description 193
3. System features 194
4. Data requirements 195
5. External interface requirements 196
6. Quality attributes 197
7. Internationalization and localization requirements 198
8. [Other requirements] 199
Contents xiii
Appendix A: Glossary 199
Appendix B: Analysis models 199
Requirements specification on agile projects 199
Chapter 11 Writing excellent requirements 203
Characteristics of excellent requirements 203
Characteristics of requirement statements 204
Characteristics of requirements collections 205
Guidelines for writing requirements 207
System or user perspective 207
Writing style 208
Level of detail 211
Representation techniques 212
Avoiding ambiguity 213
Avoiding incompleteness 216
Sample requirements, before and after 217
Chapter 12 A picture is worth 1024 words 221
Modeling the requirements 222
From voice of the customer to analysis models 223
Selecting the right representations 225
Data flow diagram 226
Swimlane diagram 230
State-transition diagram and state table 232
Dialog map 235
Decision tables and decision trees 239
Event-response tables 240
A few words about UML diagrams 243
Modeling on agile projects 243
A final reminder 244
xiv Contents
Chapter 13 Specifying data requirements 245
Modeling data relationships 245
The data dictionary 248
Data analysis 251
Specifying reports 252
Eliciting reporting requirements 253
Report specification considerations 254
A report specification template 255
Dashboard reporting 257
Chapter 14 Beyond functionality 261
Software quality attributes 262
Exploring quality attributes 263
Defining quality requirements 267
External quality attributes 267
Internal quality attributes 281
Specifying quality requirements with Planguage 287
Quality attribute trade-offs 288
Implementing quality attribute requirements 290
Constraints 291
Handling quality attributes on agile projects 293
Chapter 15 Risk reduction through prototyping 295
Prototyping: What and why 296
Mock-ups and proofs of concept 297
Throwaway and evolutionary prototypes 298
Paper and electronic prototypes 301
Working with prototypes 303
Prototype evaluation 306
Contents xv
Risks of prototyping 307
Pressure to release the prototype 308
Distraction by details 308
Unrealistic performance expectations 309
Investing excessive effort in prototypes 309
Prototyping success factors 310
Chapter 16 First things first: Setting requirement priorities 313
Why prioritize requirements? 314
Some prioritization pragmatics 315
Games people play with priorities 316
Some prioritization techniques 317
In or out 318
Pairwise comparison and rank ordering 318
Three-level scale 319
MoSCoW 320
$100 321
Prioritization based on value, cost, and risk 322
Chapter 17 Validating the requirements 329
Validation and verification 331
Reviewing requirements 332
The inspection process 333
Defect checklist 338
Requirements review tips 339
Requirements review challenges 340
Prototyping requirements 342
Testing the requirements 342
Validating requirements with acceptance criteria 347
Acceptance criteria 347
Acceptance tests 348
xvi Contents
Chapter 18 Requirements reuse 351
Why reuse requirements? 352
Dimensions of requirements reuse 352
Extent of reuse 353
Extent of modification 354
Reuse mechanism 354
Types of requirements information to reuse 355
Common reuse scenarios 356
Software product lines 356
Reengineered and replacement systems 357
Other likely reuse opportunities 357
Requirement patterns 358
Tools to facilitate reuse 359
Making requirements reusable 360
Requirements reuse barriers and success factors 362
Reuse barriers 362
Reuse success factors 363
Chapter 19 Beyond requirements development 365
Estimating requirements effort 366
From requirements to project plans 369
Estimating project size and effort from requirements 370
Requirements and scheduling 372
From requirements to designs and code 373
Architecture and allocation 373
Software design 374
User interface design 375
From requirements to tests 377
From requirements to success 379
PART HI REQUIREMENTS FOR SPECIFIC PROJECT CLASSES
Chapter 20 Agile projects 383
Limitations of the waterfall 384
The agile development approach 385
Essential aspects of an agile approach to requirements 385
Customer involvement 386
Documentation detail 386
The backlog and prioritization 387
Timing 387
Epics, user stories, and features, oh my! 388
Expect change 389
Adapting requirements practices to agile projects 390
Transitioning to agile: Now what? 390
Chapter 21 Enhancement and replacement projects 393
Expected challenges 394
Requirements techniques when there is an existing system 394
Prioritizing by using business objectives 396
Mind the gap 396
Maintaining performance levels 397
When old requirements don't exist 398
Which requirements should you specify? 398
How to discover the requirements of an existing system 400
Encouraging new system adoption 401
Can we iterate? 402
Chapter 22 Packaged solution projects 405
Requirements for selecting packaged solutions 406
Developing user requirements 406
Considering business rules 407
Identifying data needs 407
Defining quality requirements 408
Evaluating solutions 408
Requirements for implementing packaged solutions 411
Configuration requirements 411
Integration requirements 412
Extension requirements 412
Data requirements 412
Business process changes 413
Common challenges with packaged solutions 413
Chapter 23 Outsourced projects 415
Appropriate levels of requirements detail 416
Acquirer-supplier interactions 418
Change management 419
Acceptance criteria 420
Chapter 24 Business process automation projects 421
Modeling business processes 422
Using current processes to derive requirements 423
Designing future processes first 424
Modeling business performance metrics 424
Good practices for business process automation projects 426
Chapter 25 Business analytics projects 427
Overview of business analytics projects 427
Requirements development for business analytics projects 429
Prioritizing work by using decisions 430
Defining how information will be used 431
Specifying data needs 432
Defining analyses that transform the data 435
The evolutionary nature of analytics 436
Chapter 26 Embedded and other real-time systems projects 439
System requirements, architecture, and allocation 440
Modeling real-time systems 441
Context diagram 442
State-transition diagram 442
Event-response table 443
Architecture diagram 445
Prototyping 446
Interfaces 446
Timing requirements 447
Quality attributes for embedded systems 449
The challenges of embedded systems 453
PART IV REQUIREMENTS MANAGEMENT
Chapter 27 Requirements management practices 457
Requirements management process 458
The requirements baseline 459
Requirements version control 460
Requirement attributes 462
Tracking requirements status 464
Resolving requirements issues 466
Measuring requirements effort 467
Managing requirements on agile projects 468
Why manage requirements? 470
Chapter 28 Change happens 471
Why manage changes? 471
Managing scope creep 472
Change control policy 474
Basic concepts of the change control process 474
XX Contents
A change control process description 475
1. Purpose and scope 476
2. Roles and responsibilities 476
3. Change request status 477
4. Entry criteria 478
5. Tasks 478
6. Exit criteria 479
7. Change control status reporting 479
Appendix: Attributes stored for each request 479
The change control board 480
CCB composition 480
CCB charter 481
Renegotiating commitments 482
Change control tools 482
Measuring change activity 483
Change impact analysis 484
Impact analysis procedure 484
Impact analysis template 488
Change management on agile projects 488
Chapter 29 Links in the requirements chain 491
Tracing requirements 491
Motivations for tracing requirements 494
The requirements traceability matrix 495
Tools for requirements tracing 498
A requirements tracing procedure 499
Is requirements tracing feasible? Is it necessary? 501
Chapter 30 Tools for requirements engineering 503
Requirements development tools 505
Elicitation tools 505
Prototyping tools 505
Modeling tools 506
Contents xxi
Requirements management tools 506
Benefits of using an RM tool 506
RM tool capabilities 508
Selecting and implementing a requirements tool 510
Selecting a tool 511
Setting up the tool and processes 511
Facilitating user adoption 513
PART V IMPLEMENTING REQUIREMENTS ENGINEERING
Chapter 31 Improving your requirements processes 517
How requirements relate to other project processes 518
Requirements and various stakeholder groups 520
Gaining commitment to change 521
Fundamentals of software process improvement 522
Root cause analysis 524
The process improvement cycle 526
Assess current practices 526
Plan improvement actions 527
Create, pilot, and roll out processes 528
Evaluate results 529
Requirements engineering process assets 530
Requirements development process assets 531
Requirements management process assets 532
Are we there yet? 533
Creating a requirements process improvement road map 535
Chapter 32 Software requirements and risk management 537
Fundamentals of software risk management 538
Elements of risk management 538
Documenting project risks 539
Planning for risk management 542
xxii Contents
Requirements-related risks 542
Requirements elicitation 543
Requirements analysis 544
Requirements specification 545
Requirements validation 545
Requirements management 546
Risk management is your friend 546
Epilogue 549
Appendix A 551
Appendix B 559
Appendix C 575
Glossary 597
References 605
Index 619
Contents xxiii |
| any_adam_object | 1 |
| author | Wiegers, Karl E. 1953- Beatty, Joy |
| author_GND | (DE-588)130013692 |
| author_facet | Wiegers, Karl E. 1953- Beatty, Joy |
| author_role | aut aut |
| author_sort | Wiegers, Karl E. 1953- |
| author_variant | k e w ke kew j b jb |
| building | Verbundindex |
| bvnumber | BV041342863 |
| callnumber-first | Q - Science |
| callnumber-label | QA76 |
| callnumber-raw | QA76.76.D47 W517 2013 |
| callnumber-search | QA76.76.D47 W517 2013 |
| callnumber-sort | QA 276.76 D47 W517 42013 |
| callnumber-subject | QA - Mathematics |
| classification_rvk | ST 230 |
| classification_tum | DAT 335f |
| ctrlnum | (OCoLC)862807775 (DE-599)BVBBV041342863 |
| dewey-full | 005.1 |
| dewey-hundreds | 000 - Computer science, information, general works |
| dewey-ones | 005 - Computer programming, programs, data, security |
| dewey-raw | 005.1 |
| dewey-search | 005.1 |
| dewey-sort | 15.1 |
| dewey-tens | 000 - Computer science, information, general works |
| discipline | Informatik |
| edition | Third edition |
| format | Book |
| fullrecord | <?xml version="1.0" encoding="UTF-8"?><collection xmlns="http://www.loc.gov/MARC21/slim"><record><leader>00000nam a22000002c 4500</leader><controlfield tag="001">BV041342863</controlfield><controlfield tag="003">DE-604</controlfield><controlfield tag="005">20241217</controlfield><controlfield tag="007">t|</controlfield><controlfield tag="008">131004s2013 xx a||| |||| 00||| eng d</controlfield><datafield tag="010" ind1=" " ind2=" "><subfield code="a">2013942928</subfield></datafield><datafield tag="020" ind1=" " ind2=" "><subfield code="a">9780735679665</subfield><subfield code="c">kart. : ca. EUR 56.00 (DE)</subfield><subfield code="9">978-0-7356-7966-5</subfield></datafield><datafield tag="020" ind1=" " ind2=" "><subfield code="a">0735679665</subfield><subfield code="9">0-7356-7966-5</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(OCoLC)862807775</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-599)BVBBV041342863</subfield></datafield><datafield tag="040" ind1=" " ind2=" "><subfield code="a">DE-604</subfield><subfield code="b">ger</subfield><subfield code="e">rda</subfield></datafield><datafield tag="041" ind1="0" ind2=" "><subfield code="a">eng</subfield></datafield><datafield tag="049" ind1=" " ind2=" "><subfield code="a">DE-91G</subfield><subfield code="a">DE-473</subfield><subfield code="a">DE-2070s</subfield><subfield code="a">DE-20</subfield><subfield code="a">DE-19</subfield><subfield code="a">DE-739</subfield><subfield code="a">DE-860</subfield><subfield code="a">DE-703</subfield></datafield><datafield tag="050" ind1=" " ind2="0"><subfield code="a">QA76.76.D47 W517 2013</subfield></datafield><datafield tag="082" ind1="0" ind2=" "><subfield code="a">005.1</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">DAT 335f</subfield><subfield code="2">stub</subfield></datafield><datafield tag="100" ind1="1" ind2=" "><subfield code="a">Wiegers, Karl E.</subfield><subfield code="d">1953-</subfield><subfield code="e">Verfasser</subfield><subfield code="0">(DE-588)130013692</subfield><subfield code="4">aut</subfield></datafield><datafield tag="245" ind1="1" ind2="0"><subfield code="a">Software requirements</subfield><subfield code="c">Karl Wiegers and Joy Beatty</subfield></datafield><datafield tag="250" ind1=" " ind2=" "><subfield code="a">Third edition</subfield></datafield><datafield tag="264" ind1=" " ind2="1"><subfield code="a">Redmond, Washington</subfield><subfield code="b">Microsoft Press</subfield><subfield code="c">[2013]</subfield></datafield><datafield tag="300" ind1=" " ind2=" "><subfield code="a">xxxii, 637 Seiten</subfield><subfield code="b">Illustrationen</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">Best practices</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Computer software</subfield><subfield code="v">Development</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">Anforderungsdefinition</subfield><subfield code="0">(DE-588)4193804-5</subfield><subfield code="2">gnd</subfield><subfield code="9">rswk-swf</subfield></datafield><datafield tag="650" ind1="0" ind2="7"><subfield code="a">Software Engineering</subfield><subfield code="0">(DE-588)4116521-4</subfield><subfield code="2">gnd</subfield><subfield code="9">rswk-swf</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="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">Requirements engineering</subfield><subfield code="0">(DE-588)4213997-1</subfield><subfield code="D">s</subfield></datafield><datafield tag="689" ind1="0" ind2="2"><subfield code="a">Software Engineering</subfield><subfield code="0">(DE-588)4116521-4</subfield><subfield code="D">s</subfield></datafield><datafield tag="689" ind1="0" ind2=" "><subfield code="8">1\p</subfield><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">Anforderungsdefinition</subfield><subfield code="0">(DE-588)4193804-5</subfield><subfield code="D">s</subfield></datafield><datafield tag="689" ind1="1" ind2=" "><subfield code="8">2\p</subfield><subfield code="5">DE-604</subfield></datafield><datafield tag="700" ind1="1" ind2=" "><subfield code="a">Beatty, Joy</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=026791596&sequence=000001&line_number=0001&func_code=DB_RECORDS&service_type=MEDIA</subfield><subfield code="3">Inhaltsverzeichnis</subfield></datafield><datafield tag="883" ind1="1" ind2=" "><subfield code="8">1\p</subfield><subfield code="a">cgwrk</subfield><subfield code="d">20201028</subfield><subfield code="q">DE-101</subfield><subfield code="u">https://d-nb.info/provenance/plan#cgwrk</subfield></datafield><datafield tag="883" ind1="1" ind2=" "><subfield code="8">2\p</subfield><subfield code="a">cgwrk</subfield><subfield code="d">20201028</subfield><subfield code="q">DE-101</subfield><subfield code="u">https://d-nb.info/provenance/plan#cgwrk</subfield></datafield><datafield tag="943" ind1="1" ind2=" "><subfield code="a">oai:aleph.bib-bvb.de:BVB01-026791596</subfield></datafield></record></collection> |
| id | DE-604.BV041342863 |
| illustrated | Illustrated |
| indexdate | 2024-12-17T09:01:00Z |
| institution | BVB |
| isbn | 9780735679665 0735679665 |
| language | English |
| lccn | 2013942928 |
| oai_aleph_id | oai:aleph.bib-bvb.de:BVB01-026791596 |
| oclc_num | 862807775 |
| open_access_boolean | |
| owner | DE-91G DE-BY-TUM DE-473 DE-BY-UBG DE-2070s DE-20 DE-19 DE-BY-UBM DE-739 DE-860 DE-703 |
| owner_facet | DE-91G DE-BY-TUM DE-473 DE-BY-UBG DE-2070s DE-20 DE-19 DE-BY-UBM DE-739 DE-860 DE-703 |
| physical | xxxii, 637 Seiten Illustrationen |
| publishDate | 2013 |
| publishDateSearch | 2013 |
| publishDateSort | 2013 |
| publisher | Microsoft Press |
| record_format | marc |
| series2 | Best practices |
| spelling | Wiegers, Karl E. 1953- Verfasser (DE-588)130013692 aut Software requirements Karl Wiegers and Joy Beatty Third edition Redmond, Washington Microsoft Press [2013] xxxii, 637 Seiten Illustrationen txt rdacontent n rdamedia nc rdacarrier Best practices Computer software Development Softwareentwicklung (DE-588)4116522-6 gnd rswk-swf Anforderungsdefinition (DE-588)4193804-5 gnd rswk-swf Software Engineering (DE-588)4116521-4 gnd rswk-swf Requirements engineering (DE-588)4213997-1 gnd rswk-swf Softwareentwicklung (DE-588)4116522-6 s Requirements engineering (DE-588)4213997-1 s Software Engineering (DE-588)4116521-4 s 1\p DE-604 Anforderungsdefinition (DE-588)4193804-5 s 2\p DE-604 Beatty, Joy Verfasser aut HBZ Datenaustausch application/pdf http://bvbr.bib-bvb.de:8991/F?func=service&doc_library=BVB01&local_base=BVB01&doc_number=026791596&sequence=000001&line_number=0001&func_code=DB_RECORDS&service_type=MEDIA Inhaltsverzeichnis 1\p cgwrk 20201028 DE-101 https://d-nb.info/provenance/plan#cgwrk 2\p cgwrk 20201028 DE-101 https://d-nb.info/provenance/plan#cgwrk |
| spellingShingle | Wiegers, Karl E. 1953- Beatty, Joy Software requirements Computer software Development Softwareentwicklung (DE-588)4116522-6 gnd Anforderungsdefinition (DE-588)4193804-5 gnd Software Engineering (DE-588)4116521-4 gnd Requirements engineering (DE-588)4213997-1 gnd |
| subject_GND | (DE-588)4116522-6 (DE-588)4193804-5 (DE-588)4116521-4 (DE-588)4213997-1 |
| title | Software requirements |
| title_auth | Software requirements |
| title_exact_search | Software requirements |
| title_full | Software requirements Karl Wiegers and Joy Beatty |
| title_fullStr | Software requirements Karl Wiegers and Joy Beatty |
| title_full_unstemmed | Software requirements Karl Wiegers and Joy Beatty |
| title_short | Software requirements |
| title_sort | software requirements |
| topic | Computer software Development Softwareentwicklung (DE-588)4116522-6 gnd Anforderungsdefinition (DE-588)4193804-5 gnd Software Engineering (DE-588)4116521-4 gnd Requirements engineering (DE-588)4213997-1 gnd |
| topic_facet | Computer software Development Softwareentwicklung Anforderungsdefinition Software Engineering Requirements engineering |
| url | http://bvbr.bib-bvb.de:8991/F?func=service&doc_library=BVB01&local_base=BVB01&doc_number=026791596&sequence=000001&line_number=0001&func_code=DB_RECORDS&service_type=MEDIA |
| work_keys_str_mv | AT wiegerskarle softwarerequirements AT beattyjoy softwarerequirements |