Verfügbarkeit: Mastering the requirements process

Mastering the requirements process:

Gespeichert in:

Bibliographische Detailangaben
Hauptverfasser:	Robertson, Suzanne (VerfasserIn), Robertson, James (VerfasserIn)
Format:	Buch
Sprache:	English
Veröffentlicht:	Harlow [u.a.] Addison-Wesley 2006
Ausgabe:	2nd. ed.
Schriftenreihe:	ACM Press books
Schlagworte:	Project management Anforderung Softwareentwicklung Systemanalyse Projektmanagement Requirements engineering
Online-Zugang:	Inhaltsverzeichnis
Beschreibung:	Hier auch später erschienene, unveränderte Nachdrucke
Beschreibung:	XXIV, 560 S. Ill.
ISBN:	9780321419491

Internformat

MARC


LEADER	00000nam a2200000 c 4500
001	BV022782500
003	DE-604
005	20140109
007	t
008	070919s2006 a\|\|\| \|\|\|\| 00\|\|\| eng d
020			\|a 9780321419491 \|9 978-0-321-41949-1
035			\|a (OCoLC)62697079
035			\|a (DE-599)BVBBV022782500
040			\|a DE-604 \|b ger \|e rakwb
041	0		\|a eng
049			\|a DE-1049 \|a DE-83 \|a DE-859 \|a DE-473 \|a DE-B768 \|a DE-91G \|a DE-703
050		0	\|a TA190
082	0		\|a 005.10684 \|2 22
084			\|a QH 500 \|0 (DE-625)141607: \|2 rvk
084			\|a SR 870 \|0 (DE-625)143368: \|2 rvk
084			\|a ST 237 \|0 (DE-625)143623: \|2 rvk
084			\|a DAT 345f \|2 stub
100	1		\|a Robertson, Suzanne \|e Verfasser \|4 aut
245	1	0	\|a Mastering the requirements process \|c Suzanne Robertson ; James Robertson
250			\|a 2nd. ed.
264		1	\|a Harlow [u.a.] \|b Addison-Wesley \|c 2006
300			\|a XXIV, 560 S. \|b Ill.
336			\|b txt \|2 rdacontent
337			\|b n \|2 rdamedia
338			\|b nc \|2 rdacarrier
490	0		\|a ACM Press books
500			\|a Hier auch später erschienene, unveränderte Nachdrucke
650		4	\|a Project management
650	0	7	\|a Anforderung \|0 (DE-588)4135103-4 \|2 gnd \|9 rswk-swf
650	0	7	\|a Softwareentwicklung \|0 (DE-588)4116522-6 \|2 gnd \|9 rswk-swf
650	0	7	\|a Systemanalyse \|0 (DE-588)4116673-5 \|2 gnd \|9 rswk-swf
650	0	7	\|a Projektmanagement \|0 (DE-588)4047441-0 \|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 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 Digitalisierung UB Bamberg \|q application/pdf \|u http://bvbr.bib-bvb.de:8991/F?func=service&doc_library=BVB01&local_base=BVB01&doc_number=015987983&sequence=000002&line_number=0001&func_code=DB_RECORDS&service_type=MEDIA \|3 Inhaltsverzeichnis
943	1		\|a oai:aleph.bib-bvb.de:BVB01-015987983

Datensatz im Suchindex

_version_	1811705390779334656
adam_text	Contents Preface to the Second Edition xxi Foreword to the First Edition xxiii Acknowledgments xxiv 1 What Are Requirements? 1 in which we consider why we are interested in requirements Requirements Gathering and Systems Modeling 3 Agile Software Development 4 Why Do I Need Requirements? 8 What Is a Requirement? 9 Functional Requirements 9 Nonfunctional Requirements 10 Constraints 10 Evolution of Requirements 11 The Template 11 The Shell 14 The Volere Requirements Process 15 2 The Requirements Process 17 in which we look at a process for gathering requirements and discuss how you might use it Agility Guide 19 Requirements Process in Context 20 The Process 21 A Case Study 21 Project Blastoff 22 Trawling for Requirements 24 Prototyping the Requirements 25 Scenarios 25 Writing the Requirements 26 The Quality Gateway 28 Reusing Requirements 29 Reviewing the Specification 29 Iterative and Incremental Processes 30 Requirements Retrospective 31 Your Own Requirements Process 31 In Conclusion 33 vii Contents Project Blastoff 35 in which we establish a solid foundation for the requirements, and ensure that the members of the project team all start rowing in the same direction Agility Guide 38 IceBreaker 38 Scope, Stakeholders, Goals 40 Setting the Scope 40 Domains of Interest 42 First-Cut Work Context 44 Stakeholders 45 The Client 47 The Customer 48 The Users: Get to Know Them 49 Other Stakeholders 51 Consultants 52 Management 52 Subject Matter Experts 52 Core Team 52 Inspectors 53 Market Forces 53 Legal 53 Negative Stakeholders 53 Industry Standard Setters 53 Public Opinion 53 Government 53 Special-Interest Groups 54 Technical Experts 54 Cultural Interests 54 Adjacent Systems 54 Finding the Stakeholders 54 Goals: What Do You Want to Achieve? ■ 55 Keeping Track of the Purpose 59 Requirements Constraints 60 Solution Constraints 60 Project Constraints 61 Naming Conventions and Definitions 61 How Much Is This Going to Cost? 62 Risks 63 To Go or Not to Go 64 Blastoff Alternatives 65 Summary 65 Event-Driven Use Cases 67 in which we discuss a fail-safe way of partitioning the work into use cases, and along the way discover the best product to build Agility Guide 67 Understanding the Work 67 Contents Use Cases and Their Scope 69 The Work 70 The Context 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 Finding the Business Events 76 Business Use Cases 78 The Role of Adjacent Systems 79 Active Adjacent Systems 80 Autonomous Adjacent Systems 83 Cooperative Adjacent Systems 85 Business Use Cases and Product Use Cases 86 Actors 89 Summary 90 IX Trawling for Requirements 93 in which we drag the net through the work area looking for requirements, and discuss some useful techniques for doing so Agility Guide 93 Responsibility 94 The Requirements Analyst 94 Trawling and Business Use Cases 96 The Role of the Current Situation 98 Apprenticing 101 Observing Structures and Patterns 103 Interviewing the Stakeholders 104 Asking the Right Questions 106 Getting to the Essence of the Work 107 Solving the Right Problem 109 Innovative Products 110 Business Use Case Workshops 113 Outcome 114 Scenarios 115 Business Rules 115 Creativity Workshops 116 Brainstorming 117 Personas 119 Mind Maps 122 Wallpaper 124 Video and Photographs 124 Wikis, Blogs, and Discussion Forums 125 Document Archeology 126 Some Other Requirements-Gathering Techniques 128 Family Therapy 128 Soft Systems and Viewpoints 129 Determining What the Product Should Be 129 The True Origin of the Business Event 131 Does Technology Matter? 131 χ · Contents Choosing the Best Trawling Technique 132 Summary 134 6 Scenarios and Requirements 135 in which we look at scenarios as a way of helping the stakeholders to discover their requirements Agility Guide 135 Scenarios 136 Normal Case Scenarios 140 Diagramming the Scenario 142 Alternative Cases 144 Exception Cases 145 What If? Scenarios 146 Misuse Cases and Negative Scenarios 147 Scenario Template 148 Product Use Case Scenarios 150 Summary 152 7 Functional Requirements 155 in which we look at those requirements that cause the product to do something Agility Guide 155 Functional Requirements 157 Finding the Functional Requirements 157 Level of Detail or Granularity 160 Exceptions and Alternatives 161 Avoiding Ambiguity 162 Technological Requirements 164 Requirements, Not Solutions 165 Grouping Requirements 166 Alternatives to Functional Requirements 167 Summary 169 8 Nonfunctional Requirements 171 in which we look at those requirements that specify how well your product does what it does Agility Guide 172 Nonfunctional Requirements 173 Use Cases and Nonfunctional Requirements 174 The Nonfunctional Requirements 174 Look and Feel Requirements: Type 10 176 Usability and Humanity Requirements: Type 11 178 Performance Requirements: Type 12 182 Operational and Environmental Requirements: Type 13 184 Maintainability and Support Requirements: Type 14 186 Security Requirements: Type 15 187 Contents · x¡ Confidentiality 187 Availability 188 Integrity 188 Auditing 189 . . . And No More 189 Cultural and Political Requirements: Type 16 190 Legal Requirements: Type 17 192 Sarbanes-Oxley Act 194 Other Legal Obligations 194 Standards 194 Finding the Nonfunctional Requirements 195 Blogging the Requirements 19 S Use Cases 195 The Template 197 Prototypes and Nonfunctional Requirements 197 The Client 198 Don't Write a Solution 199 Summary 201 9 Fit Criteria 203 in which we show how measuring a requirement makes it unambiguous, understandable, and, importantly, testable Agility Guide 203 Why Does Fit Need a Criterion? 204 Scale of Measurement 206 Rationale 206 Fit Criteria for Nonfunctional Requirements 208 Product Failure? 209 Subjective Tests 210 Look and Feel Requirements 211 Usability and Humanity Requirements 212 Performance Requirements 213 Operational Requirements 214 Maintainability Requirements 215 Security Requirements 215 Cultural and Political Requirements 216 Legal Requirements 216 Fit Criteria for Functional Requirements 217 TestCases 218 Use Cases and Fit Criteria 218 Fit Criterion for Project Purpose 219 Fit Criteria for Solution Constraints 219 Summary 220 10 Writing the Requirements 223 in which we turn the requirements into written form Agility Guide 223 Turning Potential Requirements into Written Requirements 225 Knowledge Versus Specification 225 xii · Contents The Volere Requirements Specification Template 227 1 The Purpose of the Project 229 la The User Business or Background of the Project Effort 229 lb Goals of the Project 230 2 The Client, the Customer, and Other Stakeholders 232 2a The Client 232 2b The Customer 233 2c Other Stakeholders 233 3 Users of the Product 233 4 Mandated Constraints 234 4a Solution Constraints 235 4b Implementation Environment of the Current System 235 4c Partner or Collaborative Applications 236 4d Off-the-Shelf Software 236 4e Anticipated Workplace Environment 236 4f Schedule Constraints 236 4g Budget Constraints 237 5 Naming Conventions and Definitions 237 Sa Definitions of All Terms, Including Acronyms, Used in the Project 237 5b Data Dictionary for Any Included Models 238 6 Relevant Facts and Assumptions 238 6a Facts 238 6b Assumptions 239 7 The Scope of the Work 240 7c Work Partitioning 240 8 The Scope of the Product 241 8a Product Boundary 241 8b Product Use Case List 241 8c Individual Product Use Cases 241 The Shell 241 Snow Cards 242 Automated Requirements Tools 243 The Atomic Requirement 243 Requirement Number 244 Requirement Type 244 Event/Use Case Number 244 Description 245 Rationale 245 Originator 245 Fit Criterion 245 Customer Satisfaction and Customer Dissatisfaction 246 Priority 247 Conflicts 247 Supporting Materials 248 History 248 Writing the Specification 248 9 Functional Requirements 249 Description 250 Nonfunctional Requirements 251 Contents · xiii Project Issues 252 18 Open Issues 252 19 Off-the-Shelf Solutions 253 20 New Problems 254 21 Tasks 254 22 Migration to the New Product 254 23 Risks 254 24 Costs 255 25 User Documentation and Training 256 26 Waiting Room 256 27 Ideas for Solutions 257 Summary 257 11 The Quality Gateway 259 in which we prevent unworthy requirements becoming part of the specification Agility Guide 260 Requirements Quality 261 Using the Quality Gateway 262 Testing Completeness 263 Are There Any Missing Components? 264 Meaningful to All Stakeholders? 265 Testing Traceability 265 Consistent Terminology 267 Relevant to Purpose? 268 Testing the Fit Criterion 270 Viable within Constraints? 272 Requirement or Solution? 273 Customer Value 274 Gold Plating 275 Requirements Creep 276 Requirements Leakage 278 Implementing the Quality Gateway 279 Alternative Quality Gateways 280 Summary 281 12 Prototyping the Requirements 283 in which we use simulations to help find requirements Agility Guide 285 Prototypes and Reality 286 Low-Fidelity Prototypes 288 High-Fidelity Prototypes 292 Storyboards 294 Object Life History 296 The Prototyping Loop 297 Design and Build 298 Testing in the User Environment 299 Analyzing the Results 300 Summary 301 xiv · Contents 13 Reusing Requirements 303 in which we look for requirements that have already been written and explore ways to reuse them What Is Reusing Requirements? 303 Sources of Reusable Requirements 306 Requirements Patterns 307 Christopher Alexander's Patterns 308 A Business Event Pattern 309 Context of Event Response 310 Processing for Event Response 311 Data for Event Response 312 Forming Patterns by Abstracting 313 Patterns for Specific Domains 314 Patterns Across Domains 315 Domain Analysis 317 Trends in Reuse 318 Reuse and Objects 318 Reuse Is Now a fob? 318 Summary 319 14 Reviewing the Specification 321 in which we decide whether our specification is correct and complete, and set the priorities of the requirements Agility Guide 322 Reviewing the Specification 323 Inspections 323 Find Missing Requirements 324 Have All Business Use Cases Been Discovered? 325 1. Define the Scope 326 2. Identify Business Events and Non-Events 326 3. Model the Business Use Case 328 4. Define the Business Data 328 5. CRUD Check 330 6. Check for Custodial Processes 331 Repeat Until Done 331 Customer Value 332 Prioritizing the Requirements 333 Prioritization Factors 333 When to Prioritize 334 Requirement Priority Grading 335 Prioritization Spreadsheet 335 Conflicting Requirements 337 Ambiguous Specifications 339 Risk Analysis 340 Project Drivers 340 Project Constraints 341 Functional Requirements 341 Contents · xv Measure the Required Effort 342 Summary 342 15 Whither Requirements? 345 in which we consider some other issues for the requirements Adapting the Process 345 What About Requirements Tools? 347 Mapping Tools to Purpose 348 Publishing the Requirements 350 Contractual Document 351 Management Summary 351 Marketing Summary 352 User Review 352 Reviewing the Specification 353 Requirements Traceability 353 Tracing a Business Event 353 Dealing with Change 357 Changes in the World 358 Requirements Feedback 358 Requirements Retrospective 360 What to Look For 360 Running the Retrospective 360 Retrospective Report 362 Your Notebook 363 The End 363 Appendix A Volere Requirements Process Model 365 in which we present, for your reference, the complete Volere Requirements Process The Volere Requirements Process Model 365 Making This Work for You 366 Finding More Information 367 Define Blastoff Objectives (Process Notes 1.1.1) 371 Plan Physical Arrangements (Process Notes 1.1.2) 371 Communicate with Participants (Process Notes 1.1.3) 372 Determine Project Purpose (Process Notes 1.2.1) 374 Determine the Work Context (Process Notes 1.2.2) 374 Do First-Cut Risk Analysis (Process Notes 1.2.3) 375 Identify the Stakeholders (Process Notes 1.2.4) 376 Partition the Context (Process Notes 1.2.5) 377 Consider Non-Events (Process Notes 1.2.6) 377 Determine Business Terminology (Process Notes 1.2.7) 377 Define Project Constraints (Process Notes 1.2.8) 378 Identify Domains of Interest (Process Notes 1.2.9) 378 Write Blastoff Report (Process Notes 1.3.1) 380 Review Blastoff Results (Process Notes 1.3.2) 380 Hold Follow-Up Blastoff (Process Notes 1.3.3) 381 Make Initial Estimate (Process Notes 1.3.4) 382 Review Current Situation (Process Notes 2.1.1) 385 xvi · Contents Apprentice with the User (Process Notes 2.1.2) 385 Determine Essential Requirements (Process Notes 2.1.3) 386 Brainstorm the Requirements (Process Notes 2.1.4) 386 Interview the Users (Process Notes 2.1.5) 387 Do Document Archaeology (Process Notes 2.1.6) 388 Make Requirements Video (Process Notes 2.1.7) 389 Run Use Case Workshop (Process Notes 2.1.8) 389 Build Event Models (Process Notes 2.1.9) 390 Build Scenario Models (Process Notes 2.1.10) 391 Run Creativity Workshop (Process Notes 2.1.11) 391 Study the Adjacent Systems (Process Notes 2.2.1) 393 Define Use Case Boundary (Process Notes 2.2.2) 393 Gather Business Event Knowledge (Process Notes 2.3.1) 395 Choose Appropriate Trawling Techniques (Process Notes 2.3.2) 395 Ask Clarification Questions (Process Notes 2.4) 396 Identify Potential Requirements (Process Notes 3.1) 399 Identify Functional Requirements (Process Notes 3.2) 399 Identify Composite Requirements (Process Notes 3.3) 400 Formalize Requirement (Process Notes 3.4) 400 Formalize System Constraints (Process Notes 3.5) 400 Identify Nonfunctional Requirements (Process Notes 3.6) 401 Write Functional Fit Criteria (Process Notes 3.7) 401 Write Nonfunctional Fit Criteria (Process Notes 3.8) 402 Define Customer Value (Process Notes 3.9) 402 Identify Dependencies and Conflicts (Process Notes 3.10) 403 Review Requirement Fit Criteria (Process Notes 4.1) 405 Review Requirement Relevance (Process Notes 4.2) 406 Review Requirement Viability (Process Notes 4.3) 406 Identify Gold-Plated Requirements (Process Notes 4.4) 406 Review Requirement Completeness (Process Notes 4.5) 406 Plan the Prototype (Process Notes 5.1) 408 Build Low-Fidelity Prototype (Process Notes 5.2.1) 410 Build High-Fidelity Prototype (Process Notes 5.2.2) 410 Test High-Fidelity Prototype with Users (Process Notes 5.3.1) 413 Test Low-Fidelity Prototype with Users (Process Notes 5.3.2) 413 Identify New and Changed Requirements (Process Notes 5.3.3) 414 Evaluate Prototyping Effort (Process Notes 5.3.4) 414 Conduct Private Individual Reviews (Process Notes 6.1.1) 417 Conduct Separate Meetings with Groups (Process Notes 6.1.2) 417 Facilitator Reviews Facts (Process Notes 6.1.3) 417 Hold Retrospective Review Meeting (Process Notes 6.2.1) 420 Produce Retrospective Report (Process Notes 6.2.2) 420 Retrospective Report on Requirements Specification 420 Identify Filtration Criteria (Process Notes 6.3.1) 423 Select Relevant Requirement Types (Process Notes 6.3.2) 423 Add New Filtration Criteria (Process Notes 6.3.3) 423 Identify Missing Requirements (Process Notes 7.1.1) 427 Identify Customer Value Ratings (Process Notes 7.1.2) 427 Identify Requirement Interaction (Process Notes 7.1.3) 428 Contents · xvii Identify Prototyping Opportunity (Process Notes 7.1.4) 428 Find Missing Custodial Requirements (Process Notes 7.1.5) 429 Look for Likely Risks (Process Notes 7.2.1) 431 Quantify Each Risk (Process Notes 7.2.2) 431 Identify Estimation Input (Process Notes 7.3.1) 434 Estimate Effort for Events (Process Notes 7.3.2) 434 Estimate Requirements Effort (Process Notes 7.3.3) 435 Design Form of Specification (Process Notes 7.4.1) 437 Assemble the Specification (Process Notes 7.4.2) 437 Dictionary of Terms Used in the Requirements Process Model 437 Appendix В Volere Requirements Specification Template 451 a guide for writing a rigorous ana complete requirements specification Contents 451 Project Drivers 451 Project Constraints 451 Functional Requirements 451 Nonfunctional Requirements 451 Project Issues 452 Preamble 452 Volere 452 Requirements Types 453 Testing Requirements 453 Requirements Shell 454 1 The Purpose of the Project 454 1 a The User Business or Background of the Project Effort 454 lb Goals of the Project 455 2 The Client, the Customer, and Other Stakeholders 456 2a The Client 456 2b The Customer 456 2c Other Stakeholders 457 3 Users of the Product 457 3a The Hands-On Users of the Product 457 3b Priorities Assigned to Users 458 3c User Participation 459 3d Maintenance Users and Service Technicians 459 4 Mandated Constraints 460 4a Solution Constraints 460 4b Implementation Environment of the Current System 461 4c Partner or Collaborative Applications 462 4d Off-the-Shelf Software 462 4e Anticipated Workplace Environment 463 4f Schedule Constraints 464 4g Budget Constraints 465 5 Naming Conventions and Definitions 465 5a Definitions of All Terms, Including Acronyms, Used in the Project 465 5b Data Dictionary for Any Included Models 466 6 Relevant Facts and Assumptions 467 xviii · Contents 6a Facts 467 6b Assumptions 467 7 The Scope of the Work 468 7a The Current Situation 468 7b The Context of the Work 469 7c Work Partitioning 470 8 The Scope of the Product 472 8a Product Boundary 472 8b Product Use Case List 472 8c Individual Product Use Cases 473 9 Functional and Data Requirements 473 9a Functional Requirements 473 9b Data Requirements 475 10 Look and Feel Requirements 476 10a Appearance Requirements 476 10b Style Requirements 476 11 Usability and Humanity Requirements 477 Ila Ease of Use Requirements 477 lib Personalization and Internationalization Requirements 479 lie Learning Requirements 479 lid Understandability and Politeness Requirements 480 lie Accessibility Requirements 481 12 Performance Requirements 482 12a Speed and Latency Requirements 482 12b Safety-Critical Requirements 483 12c Precision or Accuracy Requirements 484 12d Reliability and Availability Requirements 484 12e Robustness or Fault-Tolerance Requirements 485 12f Capacity Requirements 485 12g Scalability or Extensibility Requirements 486 12h Longevity Requirements 486 13 Operational and Environmental Requirements 487 13a Expected Physical Environment 487 13b Requirements for Interfacing with Adjacent Systems 487 13c Productization Requirements 488 13d Release Requirements 489 14 Maintainability and Support Requirements 489 14a Maintenance Requirements 489 14b Supportability Requirements 490 14c Adaptability Requirements 490 15 Security Requirements 491 15a Access Requirements 491 15b Integrity Requirements 492 15c Privacy Requirements 492 15d Audit Requirements 493 15e Immunity Requirements 493 16 Cultural and Political Requirements 494 16a Cultural Requirements 494 16b Political Requirements 494 Contents · xix 17 Legal Requirements 495 17a Compliance Requirements 495 17b Standards Requirements 496 18 Open Issues 496 19 Off-the-Shelf Solutions 497 19a Ready-Made Products 497 19b Reusable Components 497 19c Products That Can Be Copied 498 20 New Problems 498 20a Effects on the Cunent Environment 498 20b Effects on the Installed Systems 499 20c Potential User Problems 499 20d Limitations in the Anticipated Implementation Environment That May Inhibit the New Product 499 20e Follow-Up Problems 500 21 Tasks 500 21 a Project Planning 500 21b Planning of the Development Phases 501 22 Migration to the New Product 501 22a Requirements for Migration to the New Product 501 22b Data That Has to Be Modified or Translated for the New System 502 23 Risks 502 24 Costs 503 25 User Documentation and Training 504 25a User Documentation Requirements 504 25b Training Requirements 505 26 Waiting Room 505 27 Ideas for Solutions 506 Appendix С Function Point Counting: A Simplified Introduction 507 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 507 A Quick Primer on Counting Function Points 509 Scope of the Work 509 Data Stored by the Work 510 Business Use Cases 511 Counting Function Points for Business Use Cases 512 Counting Input Business Use Cases 512 Counting Output Business Use Cases 514 Counting Time-Triggered Business Use Cases 515 Counting the Stored Data 517 Internal Stored Data 517 Externally Stored Data 518 Adjust for What You Don't Know 520 What's Next After Counting Function Points? 521 xx · Contents Appendix D Project Sociology Analysis Templates 523 in which we provide some help with finding the stakeholders for your project Stakeholder Map Template 523 Stakeholder Analysis Template 523 Glossary 531 Bibliography 535 Index 539
adam_txt	Contents Preface to the Second Edition xxi Foreword to the First Edition xxiii Acknowledgments xxiv 1 What Are Requirements? 1 in which we consider why we are interested in requirements Requirements Gathering and Systems Modeling 3 Agile Software Development 4 Why Do I Need Requirements? 8 What Is a Requirement? 9 Functional Requirements 9 Nonfunctional Requirements 10 Constraints 10 Evolution of Requirements 11 The Template 11 The Shell 14 The Volere Requirements Process 15 2 The Requirements Process 17 in which we look at a process for gathering requirements and discuss how you might use it Agility Guide 19 Requirements Process in Context 20 The Process 21 A Case Study 21 Project Blastoff 22 Trawling for Requirements 24 Prototyping the Requirements 25 Scenarios 25 Writing the Requirements 26 The Quality Gateway 28 Reusing Requirements 29 Reviewing the Specification 29 Iterative and Incremental Processes 30 Requirements Retrospective 31 Your Own Requirements Process 31 In Conclusion 33 vii Contents Project Blastoff 35 in which we establish a solid foundation for the requirements, and ensure that the members of the project team all start rowing in the same direction Agility Guide 38 IceBreaker 38 Scope, Stakeholders, Goals 40 Setting the Scope 40 Domains of Interest 42 First-Cut Work Context 44 Stakeholders 45 The Client 47 The Customer 48 The Users: Get to Know Them 49 Other Stakeholders 51 Consultants 52 Management 52 Subject Matter Experts 52 Core Team 52 Inspectors 53 Market Forces 53 Legal 53 Negative Stakeholders 53 Industry Standard Setters 53 Public Opinion 53 Government 53 Special-Interest Groups 54 Technical Experts 54 Cultural Interests 54 Adjacent Systems 54 Finding the Stakeholders 54 Goals: What Do You Want to Achieve? ■ 55 Keeping Track of the Purpose 59 Requirements Constraints 60 Solution Constraints 60 Project Constraints 61 Naming Conventions and Definitions 61 How Much Is This Going to Cost? 62 Risks 63 To Go or Not to Go 64 Blastoff Alternatives 65 Summary 65 Event-Driven Use Cases 67 in which we discuss a fail-safe way of partitioning the work into use cases, and along the way discover the best product to build Agility Guide 67 Understanding the Work 67 Contents Use Cases and Their Scope 69 The Work 70 The Context 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 Finding the Business Events 76 Business Use Cases 78 The Role of Adjacent Systems 79 Active Adjacent Systems 80 Autonomous Adjacent Systems 83 Cooperative Adjacent Systems 85 Business Use Cases and Product Use Cases 86 Actors 89 Summary 90 IX Trawling for Requirements 93 in which we drag the net through the work area looking for requirements, and discuss some useful techniques for doing so Agility Guide 93 Responsibility 94 The Requirements Analyst 94 Trawling and Business Use Cases 96 The Role of the Current Situation 98 Apprenticing 101 Observing Structures and Patterns 103 Interviewing the Stakeholders 104 Asking the Right Questions 106 Getting to the Essence of the Work 107 Solving the Right Problem 109 Innovative Products 110 Business Use Case Workshops 113 Outcome 114 Scenarios 115 Business Rules 115 Creativity Workshops 116 Brainstorming 117 Personas 119 Mind Maps 122 Wallpaper 124 Video and Photographs 124 Wikis, Blogs, and Discussion Forums 125 Document Archeology 126 Some Other Requirements-Gathering Techniques 128 Family Therapy 128 Soft Systems and Viewpoints 129 Determining What the Product Should Be 129 The True Origin of the Business Event 131 Does Technology Matter? 131 χ · Contents Choosing the Best Trawling Technique 132 Summary 134 6 Scenarios and Requirements 135 in which we look at scenarios as a way of helping the stakeholders to discover their requirements Agility Guide 135 Scenarios 136 Normal Case Scenarios 140 Diagramming the Scenario 142 Alternative Cases 144 Exception Cases 145 What If? Scenarios 146 Misuse Cases and Negative Scenarios 147 Scenario Template 148 Product Use Case Scenarios 150 Summary 152 7 Functional Requirements 155 in which we look at those requirements that cause the product to do something Agility Guide 155 Functional Requirements 157 Finding the Functional Requirements 157 Level of Detail or Granularity 160 Exceptions and Alternatives 161 Avoiding Ambiguity 162 Technological Requirements 164 Requirements, Not Solutions 165 Grouping Requirements 166 Alternatives to Functional Requirements 167 Summary 169 8 Nonfunctional Requirements 171 in which we look at those requirements that specify how well your product does what it does Agility Guide 172 Nonfunctional Requirements 173 Use Cases and Nonfunctional Requirements 174 The Nonfunctional Requirements 174 Look and Feel Requirements: Type 10 176 Usability and Humanity Requirements: Type 11 178 Performance Requirements: Type 12 182 Operational and Environmental Requirements: Type 13 184 Maintainability and Support Requirements: Type 14 186 Security Requirements: Type 15 187 Contents · x¡ Confidentiality 187 Availability 188 Integrity 188 Auditing 189 . . . And No More 189 Cultural and Political Requirements: Type 16 190 Legal Requirements: Type 17 192 Sarbanes-Oxley Act 194 Other Legal Obligations 194 Standards 194 Finding the Nonfunctional Requirements 195 Blogging the Requirements 19 S Use Cases 195 The Template 197 Prototypes and Nonfunctional Requirements 197 The Client 198 Don't Write a Solution 199 Summary 201 9 Fit Criteria 203 in which we show how measuring a requirement makes it unambiguous, understandable, and, importantly, testable Agility Guide 203 Why Does Fit Need a Criterion? 204 Scale of Measurement 206 Rationale 206 Fit Criteria for Nonfunctional Requirements 208 Product Failure? 209 Subjective Tests 210 Look and Feel Requirements 211 Usability and Humanity Requirements 212 Performance Requirements 213 Operational Requirements 214 Maintainability Requirements 215 Security Requirements 215 Cultural and Political Requirements 216 Legal Requirements 216 Fit Criteria for Functional Requirements 217 TestCases 218 Use Cases and Fit Criteria 218 Fit Criterion for Project Purpose 219 Fit Criteria for Solution Constraints 219 Summary 220 10 Writing the Requirements 223 in which we turn the requirements into written form Agility Guide 223 Turning Potential Requirements into Written Requirements 225 Knowledge Versus Specification 225 xii · Contents The Volere Requirements Specification Template 227 1 The Purpose of the Project 229 la The User Business or Background of the Project Effort 229 lb Goals of the Project 230 2 The Client, the Customer, and Other Stakeholders 232 2a The Client 232 2b The Customer 233 2c Other Stakeholders 233 3 Users of the Product 233 4 Mandated Constraints 234 4a Solution Constraints 235 4b Implementation Environment of the Current System 235 4c Partner or Collaborative Applications 236 4d Off-the-Shelf Software 236 4e Anticipated Workplace Environment 236 4f Schedule Constraints 236 4g Budget Constraints 237 5 Naming Conventions and Definitions 237 Sa Definitions of All Terms, Including Acronyms, Used in the Project 237 5b Data Dictionary for Any Included Models 238 6 Relevant Facts and Assumptions 238 6a Facts 238 6b Assumptions 239 7 The Scope of the Work 240 7c Work Partitioning 240 8 The Scope of the Product 241 8a Product Boundary 241 8b Product Use Case List 241 8c Individual Product Use Cases 241 The Shell 241 Snow Cards 242 Automated Requirements Tools 243 The Atomic Requirement 243 Requirement Number 244 Requirement Type 244 Event/Use Case Number 244 Description 245 Rationale 245 Originator 245 Fit Criterion 245 Customer Satisfaction and Customer Dissatisfaction 246 Priority 247 Conflicts 247 Supporting Materials 248 History 248 Writing the Specification 248 9 Functional Requirements 249 Description 250 Nonfunctional Requirements 251 Contents · xiii Project Issues 252 18 Open Issues 252 19 Off-the-Shelf Solutions 253 20 New Problems 254 21 Tasks 254 22 Migration to the New Product 254 23 Risks 254 24 Costs 255 25 User Documentation and Training 256 26 Waiting Room 256 27 Ideas for Solutions 257 Summary 257 11 The Quality Gateway 259 in which we prevent unworthy requirements becoming part of the specification Agility Guide 260 Requirements Quality 261 Using the Quality Gateway 262 Testing Completeness 263 Are There Any Missing Components? 264 Meaningful to All Stakeholders? 265 Testing Traceability 265 Consistent Terminology 267 Relevant to Purpose? 268 Testing the Fit Criterion 270 Viable within Constraints? 272 Requirement or Solution? 273 Customer Value 274 Gold Plating 275 Requirements Creep 276 Requirements Leakage 278 Implementing the Quality Gateway 279 Alternative Quality Gateways 280 Summary 281 12 Prototyping the Requirements 283 in which we use simulations to help find requirements Agility Guide 285 Prototypes and Reality 286 Low-Fidelity Prototypes 288 High-Fidelity Prototypes 292 Storyboards 294 Object Life History 296 The Prototyping Loop 297 Design and Build 298 Testing in the User Environment 299 Analyzing the Results 300 Summary 301 xiv · Contents 13 Reusing Requirements 303 in which we look for requirements that have already been written and explore ways to reuse them What Is Reusing Requirements? 303 Sources of Reusable Requirements 306 Requirements Patterns 307 Christopher Alexander's Patterns 308 A Business Event Pattern 309 Context of Event Response 310 Processing for Event Response 311 Data for Event Response 312 Forming Patterns by Abstracting 313 Patterns for Specific Domains 314 Patterns Across Domains 315 Domain Analysis 317 Trends in Reuse 318 Reuse and Objects 318 Reuse Is Now a fob? 318 Summary 319 14 Reviewing the Specification 321 in which we decide whether our specification is correct and complete, and set the priorities of the requirements Agility Guide 322 Reviewing the Specification 323 Inspections 323 Find Missing Requirements 324 Have All Business Use Cases Been Discovered? 325 1. Define the Scope 326 2. Identify Business Events and Non-Events 326 3. Model the Business Use Case 328 4. Define the Business Data 328 5. CRUD Check 330 6. Check for Custodial Processes 331 Repeat Until Done 331 Customer Value 332 Prioritizing the Requirements 333 Prioritization Factors 333 When to Prioritize 334 Requirement Priority Grading 335 Prioritization Spreadsheet 335 Conflicting Requirements 337 Ambiguous Specifications 339 Risk Analysis 340 Project Drivers 340 Project Constraints 341 Functional Requirements 341 Contents · xv Measure the Required Effort 342 Summary 342 15 Whither Requirements? 345 in which we consider some other issues for the requirements Adapting the Process 345 What About Requirements Tools? 347 Mapping Tools to Purpose 348 Publishing the Requirements 350 Contractual Document 351 Management Summary 351 Marketing Summary 352 User Review 352 Reviewing the Specification 353 Requirements Traceability 353 Tracing a Business Event 353 Dealing with Change 357 Changes in the World 358 Requirements Feedback 358 Requirements Retrospective 360 What to Look For 360 Running the Retrospective 360 Retrospective Report 362 Your Notebook 363 The End 363 Appendix A Volere Requirements Process Model 365 in which we present, for your reference, the complete Volere Requirements Process The Volere Requirements Process Model 365 Making This Work for You 366 Finding More Information 367 Define Blastoff Objectives (Process Notes 1.1.1) 371 Plan Physical Arrangements (Process Notes 1.1.2) 371 Communicate with Participants (Process Notes 1.1.3) 372 Determine Project Purpose (Process Notes 1.2.1) 374 Determine the Work Context (Process Notes 1.2.2) 374 Do First-Cut Risk Analysis (Process Notes 1.2.3) 375 Identify the Stakeholders (Process Notes 1.2.4) 376 Partition the Context (Process Notes 1.2.5) 377 Consider Non-Events (Process Notes 1.2.6) 377 Determine Business Terminology (Process Notes 1.2.7) 377 Define Project Constraints (Process Notes 1.2.8) 378 Identify Domains of Interest (Process Notes 1.2.9) 378 Write Blastoff Report (Process Notes 1.3.1) 380 Review Blastoff Results (Process Notes 1.3.2) 380 Hold Follow-Up Blastoff (Process Notes 1.3.3) 381 Make Initial Estimate (Process Notes 1.3.4) 382 Review Current Situation (Process Notes 2.1.1) 385 xvi · Contents Apprentice with the User (Process Notes 2.1.2) 385 Determine Essential Requirements (Process Notes 2.1.3) 386 Brainstorm the Requirements (Process Notes 2.1.4) 386 Interview the Users (Process Notes 2.1.5) 387 Do Document Archaeology (Process Notes 2.1.6) 388 Make Requirements Video (Process Notes 2.1.7) 389 Run Use Case Workshop (Process Notes 2.1.8) 389 Build Event Models (Process Notes 2.1.9) 390 Build Scenario Models (Process Notes 2.1.10) 391 Run Creativity Workshop (Process Notes 2.1.11) 391 Study the Adjacent Systems (Process Notes 2.2.1) 393 Define Use Case Boundary (Process Notes 2.2.2) 393 Gather Business Event Knowledge (Process Notes 2.3.1) 395 Choose Appropriate Trawling Techniques (Process Notes 2.3.2) 395 Ask Clarification Questions (Process Notes 2.4) 396 Identify Potential Requirements (Process Notes 3.1) 399 Identify Functional Requirements (Process Notes 3.2) 399 Identify Composite Requirements (Process Notes 3.3) 400 Formalize Requirement (Process Notes 3.4) 400 Formalize System Constraints (Process Notes 3.5) 400 Identify Nonfunctional Requirements (Process Notes 3.6) 401 Write Functional Fit Criteria (Process Notes 3.7) 401 Write Nonfunctional Fit Criteria (Process Notes 3.8) 402 Define Customer Value (Process Notes 3.9) 402 Identify Dependencies and Conflicts (Process Notes 3.10) 403 Review Requirement Fit Criteria (Process Notes 4.1) 405 Review Requirement Relevance (Process Notes 4.2) 406 Review Requirement Viability (Process Notes 4.3) 406 Identify Gold-Plated Requirements (Process Notes 4.4) 406 Review Requirement Completeness (Process Notes 4.5) 406 Plan the Prototype (Process Notes 5.1) 408 Build Low-Fidelity Prototype (Process Notes 5.2.1) 410 Build High-Fidelity Prototype (Process Notes 5.2.2) 410 Test High-Fidelity Prototype with Users (Process Notes 5.3.1) 413 Test Low-Fidelity Prototype with Users (Process Notes 5.3.2) 413 Identify New and Changed Requirements (Process Notes 5.3.3) 414 Evaluate Prototyping Effort (Process Notes 5.3.4) 414 Conduct Private Individual Reviews (Process Notes 6.1.1) 417 Conduct Separate Meetings with Groups (Process Notes 6.1.2) 417 Facilitator Reviews Facts (Process Notes 6.1.3) 417 Hold Retrospective Review Meeting (Process Notes 6.2.1) 420 Produce Retrospective Report (Process Notes 6.2.2) 420 Retrospective Report on Requirements Specification 420 Identify Filtration Criteria (Process Notes 6.3.1) 423 Select Relevant Requirement Types (Process Notes 6.3.2) 423 Add New Filtration Criteria (Process Notes 6.3.3) 423 Identify Missing Requirements (Process Notes 7.1.1) 427 Identify Customer Value Ratings (Process Notes 7.1.2) 427 Identify Requirement Interaction (Process Notes 7.1.3) 428 Contents · xvii Identify Prototyping Opportunity (Process Notes 7.1.4) 428 Find Missing Custodial Requirements (Process Notes 7.1.5) 429 Look for Likely Risks (Process Notes 7.2.1) 431 Quantify Each Risk (Process Notes 7.2.2) 431 Identify Estimation Input (Process Notes 7.3.1) 434 Estimate Effort for Events (Process Notes 7.3.2) 434 Estimate Requirements Effort (Process Notes 7.3.3) 435 Design Form of Specification (Process Notes 7.4.1) 437 Assemble the Specification (Process Notes 7.4.2) 437 Dictionary of Terms Used in the Requirements Process Model 437 Appendix В Volere Requirements Specification Template 451 a guide for writing a rigorous ana complete requirements specification Contents 451 Project Drivers 451 Project Constraints 451 Functional Requirements 451 Nonfunctional Requirements 451 Project Issues 452 Preamble 452 Volere 452 Requirements Types 453 Testing Requirements 453 Requirements Shell 454 1 The Purpose of the Project 454 1 a The User Business or Background of the Project Effort 454 lb Goals of the Project 455 2 The Client, the Customer, and Other Stakeholders 456 2a The Client 456 2b The Customer 456 2c Other Stakeholders 457 3 Users of the Product 457 3a The Hands-On Users of the Product 457 3b Priorities Assigned to Users 458 3c User Participation 459 3d Maintenance Users and Service Technicians 459 4 Mandated Constraints 460 4a Solution Constraints 460 4b Implementation Environment of the Current System 461 4c Partner or Collaborative Applications 462 4d Off-the-Shelf Software 462 4e Anticipated Workplace Environment 463 4f Schedule Constraints 464 4g Budget Constraints 465 5 Naming Conventions and Definitions 465 5a Definitions of All Terms, Including Acronyms, Used in the Project 465 5b Data Dictionary for Any Included Models 466 6 Relevant Facts and Assumptions 467 xviii · Contents 6a Facts 467 6b Assumptions 467 7 The Scope of the Work 468 7a The Current Situation 468 7b The Context of the Work 469 7c Work Partitioning 470 8 The Scope of the Product 472 8a Product Boundary 472 8b Product Use Case List 472 8c Individual Product Use Cases 473 9 Functional and Data Requirements 473 9a Functional Requirements 473 9b Data Requirements 475 10 Look and Feel Requirements 476 10a Appearance Requirements 476 10b Style Requirements 476 11 Usability and Humanity Requirements 477 Ila Ease of Use Requirements 477 lib Personalization and Internationalization Requirements 479 lie Learning Requirements 479 lid Understandability and Politeness Requirements 480 lie Accessibility Requirements 481 12 Performance Requirements 482 12a Speed and Latency Requirements 482 12b Safety-Critical Requirements 483 12c Precision or Accuracy Requirements 484 12d Reliability and Availability Requirements 484 12e Robustness or Fault-Tolerance Requirements 485 12f Capacity Requirements 485 12g Scalability or Extensibility Requirements 486 12h Longevity Requirements 486 13 Operational and Environmental Requirements 487 13a Expected Physical Environment 487 13b Requirements for Interfacing with Adjacent Systems 487 13c Productization Requirements 488 13d Release Requirements 489 14 Maintainability and Support Requirements 489 14a Maintenance Requirements 489 14b Supportability Requirements 490 14c Adaptability Requirements 490 15 Security Requirements 491 15a Access Requirements 491 15b Integrity Requirements 492 15c Privacy Requirements 492 15d Audit Requirements 493 15e Immunity Requirements 493 16 Cultural and Political Requirements 494 16a Cultural Requirements 494 16b Political Requirements 494 Contents · xix 17 Legal Requirements 495 17a Compliance Requirements 495 17b Standards Requirements 496 18 Open Issues 496 19 Off-the-Shelf Solutions 497 19a Ready-Made Products 497 19b Reusable Components 497 19c Products That Can Be Copied 498 20 New Problems 498 20a Effects on the Cunent Environment 498 20b Effects on the Installed Systems 499 20c Potential User Problems 499 20d Limitations in the Anticipated Implementation Environment That May Inhibit the New Product 499 20e Follow-Up Problems 500 21 Tasks 500 21 a Project Planning 500 21b Planning of the Development Phases 501 22 Migration to the New Product 501 22a Requirements for Migration to the New Product 501 22b Data That Has to Be Modified or Translated for the New System 502 23 Risks 502 24 Costs 503 25 User Documentation and Training 504 25a User Documentation Requirements 504 25b Training Requirements 505 26 Waiting Room 505 27 Ideas for Solutions 506 Appendix С Function Point Counting: A Simplified Introduction 507 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 507 A Quick Primer on Counting Function Points 509 Scope of the Work 509 Data Stored by the Work 510 Business Use Cases 511 Counting Function Points for Business Use Cases 512 Counting Input Business Use Cases 512 Counting Output Business Use Cases 514 Counting Time-Triggered Business Use Cases 515 Counting the Stored Data 517 Internal Stored Data 517 Externally Stored Data 518 Adjust for What You Don't Know 520 What's Next After Counting Function Points? 521 xx · Contents Appendix D Project Sociology Analysis Templates 523 in which we provide some help with finding the stakeholders for your project Stakeholder Map Template 523 Stakeholder Analysis Template 523 Glossary 531 Bibliography 535 Index 539
any_adam_object	1
any_adam_object_boolean	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	BV022782500
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	QH 500 SR 870 ST 237
classification_tum	DAT 345f
ctrlnum	(OCoLC)62697079 (DE-599)BVBBV022782500
dewey-full	005.10684
dewey-hundreds	000 - Computer science, information, general works
dewey-ones	005 - Computer programming, programs, data, security
dewey-raw	005.10684
dewey-search	005.10684
dewey-sort	15.10684
dewey-tens	000 - Computer science, information, general works
discipline	Informatik Wirtschaftswissenschaften
discipline_str_mv	Informatik Wirtschaftswissenschaften
edition	2nd. ed.
format	Book
fullrecord	<?xml version="1.0" encoding="UTF-8"?><collection xmlns="http://www.loc.gov/MARC21/slim"><record><leader>00000nam a2200000 c 4500</leader><controlfield tag="001">BV022782500</controlfield><controlfield tag="003">DE-604</controlfield><controlfield tag="005">20140109</controlfield><controlfield tag="007">t</controlfield><controlfield tag="008">070919s2006 a\|\|\| \|\|\|\| 00\|\|\| eng d</controlfield><datafield tag="020" ind1=" " ind2=" "><subfield code="a">9780321419491</subfield><subfield code="9">978-0-321-41949-1</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(OCoLC)62697079</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-599)BVBBV022782500</subfield></datafield><datafield tag="040" ind1=" " ind2=" "><subfield code="a">DE-604</subfield><subfield code="b">ger</subfield><subfield code="e">rakwb</subfield></datafield><datafield tag="041" ind1="0" ind2=" "><subfield code="a">eng</subfield></datafield><datafield tag="049" ind1=" " ind2=" "><subfield code="a">DE-1049</subfield><subfield code="a">DE-83</subfield><subfield code="a">DE-859</subfield><subfield code="a">DE-473</subfield><subfield code="a">DE-B768</subfield><subfield code="a">DE-91G</subfield><subfield code="a">DE-703</subfield></datafield><datafield tag="050" ind1=" " ind2="0"><subfield code="a">TA190</subfield></datafield><datafield tag="082" ind1="0" ind2=" "><subfield code="a">005.10684</subfield><subfield code="2">22</subfield></datafield><datafield tag="084" ind1=" " ind2=" "><subfield code="a">QH 500</subfield><subfield code="0">(DE-625)141607:</subfield><subfield code="2">rvk</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 345f</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="c">Suzanne Robertson ; James Robertson</subfield></datafield><datafield tag="250" ind1=" " ind2=" "><subfield code="a">2nd. ed.</subfield></datafield><datafield tag="264" ind1=" " ind2="1"><subfield code="a">Harlow [u.a.]</subfield><subfield code="b">Addison-Wesley</subfield><subfield code="c">2006</subfield></datafield><datafield tag="300" ind1=" " ind2=" "><subfield code="a">XXIV, 560 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">ACM Press books</subfield></datafield><datafield tag="500" ind1=" " ind2=" "><subfield code="a">Hier auch später erschienene, unveränderte Nachdrucke</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Project management</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">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">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">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">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">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">Digitalisierung UB Bamberg</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=015987983&sequence=000002&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-015987983</subfield></datafield></record></collection>
id	DE-604.BV022782500
illustrated	Illustrated
index_date	2024-07-02T18:36:47Z
indexdate	2024-10-01T10:01:40Z
institution	BVB
isbn	9780321419491
language	English
oai_aleph_id	oai:aleph.bib-bvb.de:BVB01-015987983
oclc_num	62697079
open_access_boolean
owner	DE-1049 DE-83 DE-859 DE-473 DE-BY-UBG DE-B768 DE-91G DE-BY-TUM DE-703
owner_facet	DE-1049 DE-83 DE-859 DE-473 DE-BY-UBG DE-B768 DE-91G DE-BY-TUM DE-703
physical	XXIV, 560 S. Ill.
publishDate	2006
publishDateSearch	2006
publishDateSort	2006
publisher	Addison-Wesley
record_format	marc
series2	ACM Press books
spelling	Robertson, Suzanne Verfasser aut Mastering the requirements process Suzanne Robertson ; James Robertson 2nd. ed. Harlow [u.a.] Addison-Wesley 2006 XXIV, 560 S. Ill. txt rdacontent n rdamedia nc rdacarrier ACM Press books Hier auch später erschienene, unveränderte Nachdrucke Project management Anforderung (DE-588)4135103-4 gnd rswk-swf Softwareentwicklung (DE-588)4116522-6 gnd rswk-swf Systemanalyse (DE-588)4116673-5 gnd rswk-swf Projektmanagement (DE-588)4047441-0 gnd rswk-swf Requirements engineering (DE-588)4213997-1 gnd rswk-swf Softwareentwicklung (DE-588)4116522-6 s Projektmanagement (DE-588)4047441-0 s Anforderung (DE-588)4135103-4 s Systemanalyse (DE-588)4116673-5 s DE-604 Requirements engineering (DE-588)4213997-1 s Robertson, James Verfasser aut Digitalisierung UB Bamberg application/pdf http://bvbr.bib-bvb.de:8991/F?func=service&doc_library=BVB01&local_base=BVB01&doc_number=015987983&sequence=000002&line_number=0001&func_code=DB_RECORDS&service_type=MEDIA Inhaltsverzeichnis
spellingShingle	Robertson, Suzanne Robertson, James Mastering the requirements process Project management Anforderung (DE-588)4135103-4 gnd Softwareentwicklung (DE-588)4116522-6 gnd Systemanalyse (DE-588)4116673-5 gnd Projektmanagement (DE-588)4047441-0 gnd Requirements engineering (DE-588)4213997-1 gnd
subject_GND	(DE-588)4135103-4 (DE-588)4116522-6 (DE-588)4116673-5 (DE-588)4047441-0 (DE-588)4213997-1
title	Mastering the requirements process
title_auth	Mastering the requirements process
title_exact_search	Mastering the requirements process
title_exact_search_txtP	Mastering the requirements process
title_full	Mastering the requirements process Suzanne Robertson ; James Robertson
title_fullStr	Mastering the requirements process Suzanne Robertson ; James Robertson
title_full_unstemmed	Mastering the requirements process Suzanne Robertson ; James Robertson
title_short	Mastering the requirements process
title_sort	mastering the requirements process
topic	Project management Anforderung (DE-588)4135103-4 gnd Softwareentwicklung (DE-588)4116522-6 gnd Systemanalyse (DE-588)4116673-5 gnd Projektmanagement (DE-588)4047441-0 gnd Requirements engineering (DE-588)4213997-1 gnd
topic_facet	Project management Anforderung Softwareentwicklung Systemanalyse Projektmanagement Requirements engineering
url	http://bvbr.bib-bvb.de:8991/F?func=service&doc_library=BVB01&local_base=BVB01&doc_number=015987983&sequence=000002&line_number=0001&func_code=DB_RECORDS&service_type=MEDIA
work_keys_str_mv	AT robertsonsuzanne masteringtherequirementsprocess AT robertsonjames masteringtherequirementsprocess

Verfügbarkeit

Es ist kein Print-Exemplar vorhanden.

Fernleihe Bestellen Achtung: Nicht im THWS-Bestand! Inhaltsverzeichnis

MARC

Datensatz im Suchindex

Es ist kein Print-Exemplar vorhanden.

Ähnliche Einträge