Engineering and Managing Software Requirements

ENGINEERING AND MANAGING SOFTWARE REQUIREMENTS......Page 1
Springerlink......Page 0
Half-title......Page 2
Title Page......Page 3
Copyright Page......Page 4
Pericles Loucopoulos......Page 6
Author Biography......Page 7
Introduction......Page 8
Book Overview......Page 9
Part 3: Studies and Industrial Experience......Page 10
Acknowledgements......Page 11
Contents......Page 12
List of Contributors......Page 16
1.1 Introduction......Page 20
1.2.1 What is a Requirement?......Page 22
1.2.2 Requirements Engineering Process......Page 23
1.3 The Role of Stakeholders in Requirements Engineering......Page 25
1.4 Different Levels of Requirements......Page 26
1.5 Requirements Management......Page 28
1.6 New Trends and the Next Practice......Page 30
1.8 Conclusion......Page 31
References......Page 32
Author Biography......Page 34
Part I: State-of-the-Art Surveys of Requirements Engineering Process Research......Page 36
2.1 Introduction......Page 38
2.2.1 The Process of Requirements Elicitation......Page 40
2.2.2 Roles of the Requirements Engineer During Elicitation......Page 43
2.3 Techniques and Approaches for Requirements Elicitation......Page 44
2.3.1 Comparison of Techniques and Approaches......Page 50
2.4 Methodology Based Requirements Elicitation......Page 53
2.5 Tool Support for Requirements Elicitation......Page 54
2.6 Issues and Pitfalls of Requirements Elicitation......Page 55
2.7 Trends and Challenges in Requirements Elicitation......Page 57
2.7.2 Trends in Requirements Elicitation Practice......Page 58
2.7.4 Challenges in Requirements Elicitation Practice......Page 59
2.9 Summary......Page 60
References......Page 61
Author Biography......Page 64
3.1 Introduction......Page 66
3.2 Modeling vs. Specification......Page 67
3.3.1 State Oriented Meta-Models......Page 69
3.3.4 Data Oriented Meta-Models......Page 71
3.3.5 Heterogeneous Meta-Models......Page 72
3.3.6 Multiple-View Approach......Page 74
3.4.1 Specification Language......Page 75
3.4.2 Complexity Control......Page 76
3.4.4 Non-Functional Requirements......Page 77
3.5 Requirements Transformation......Page 78
3.5.1 User Requirements Modeling......Page 79
3.5.2 4SRS Technique......Page 80
3.5.3 System Requirements Modeling......Page 82
3.6 Conclusion......Page 83
References......Page 84
Author Biography......Page 86
4.1 Introduction......Page 88
4.2 What is Requirements Prioritization?......Page 89
4.3.1 Importance......Page 91
4.3.5 Risk......Page 92
4.3.8 Combining Different Aspects......Page 93
4.4.1 Analytical Hierarchy Process (AHP)......Page 94
4.4.3 Numerical Assignment (Grouping)......Page 95
4.4.5 Top-Ten Requirements......Page 96
4.4.7 Combining Different Techniques......Page 97
4.5.1 One Customer......Page 98
4.5.3 Mass-Market......Page 99
4.5.5 Trade-Off between Different Stakeholders......Page 100
4.6.1 Abstraction Level......Page 101
4.6.3 Non-Functional Requirements......Page 102
4.6.5 Evaluating Prioritization......Page 103
4.6.6 Using the Results of Requirements Prioritization......Page 104
4.7 An Example of a Requirements Prioritization......Page 105
4.8 Future Research in the Area of Requirements Prioritization......Page 108
References......Page 110
Author Biography......Page 113
5.1 Introduction......Page 114
5.2 Requirements Traceability: A Basis for Understanding Requirements Interdependencies......Page 115
5.2.1 Why Requirements Traceability?......Page 116
5.2.2 Different Types of Requirements Traceability......Page 117
5.2.3 A Meta-Model of Requirements Traceability......Page 118
5.3 An Overview of Interdependency Types......Page 119
5.3.1 Structural Interdependencies......Page 121
5.3.2 Constraining Interdependencies......Page 122
5.3.3 Cost/Value Interdependencies......Page 123
5.4.1 Requirements Management......Page 124
5.4.3 Release Planning......Page 125
5.4.5 Reuse of Requirements......Page 126
5.4.6 Design and Implementation......Page 127
5.5 Research Issues......Page 128
5.5.2 How can we Identify Requirements Interdependencies?......Page 129
5.5.3 How can we Describe Requirements Interdependencies?......Page 130
5.5.5 Relations Between the Research Issues......Page 131
References......Page 132
Author Biography......Page 135
6.1 Introduction......Page 136
6.1.1 Concepts and Terms......Page 138
6.1.2 Software Change and Impact Analysis......Page 139
6.1.3 History and Trends......Page 141
6.2 Strategies for Impact Analysis......Page 143
6.2.1.1 Traceability/Dependency Analysis......Page 144
6.2.1.2 Slicing Techniques......Page 146
6.2.2.1 Design Documentation......Page 147
6.2.2.2 Interviews......Page 148
6.3 Non-Functional Requirements......Page 149
6.4 Impact Analysis Metrics......Page 150
6.4.1 Metrics for Quantifying Change Impact......Page 151
6.4.2 Metrics for Evaluation of Impact Analysis......Page 152
6.5 Tool Support......Page 156
6.6 Future of Impact Analysis......Page 157
6.7 Summary......Page 158
References......Page 159
Author Biography......Page 161
7.1 Introduction......Page 162
7.2 The Negotiation Process......Page 164
7.2.1 Pre-Negotiation......Page 165
7.2.2 Negotiation......Page 166
7.3 Dimensions of Requirements Negotiation......Page 167
7.3.1 Conflict Resolution Strategy......Page 168
7.3.2 Collaboration Situation......Page 171
7.3.3 Negotiation Tool Support......Page 172
7.4.1 Aspire......Page 173
7.4.3 EasyWinWin......Page 174
7.4.4 SmartSettle......Page 175
7.5 Conclusions......Page 177
References......Page 178
Author Biography......Page 181
8.1 The Importance of Early Quality Assurance......Page 182
8.2.1 Quality of Requirements......Page 184
8.2.2 Requirements Quality Strategy......Page 187
8.2.3 Quality Assurance Approaches for Requirements......Page 190
8.3.1 Elicitation Techniques......Page 191
8.3.2 Specification Techniques......Page 192
8.3.3 Prototyping......Page 193
8.4.1 Requirements Inspections......Page 194
8.4.2 Requirements-Based Testing......Page 197
8.4.3 Automated Approaches and Formal Methods......Page 198
8.5 Open Research Questions......Page 199
Acknowledgements......Page 201
References......Page 202
Author Biography......Page 204
Part II: The Next Practice in Requirements Engineering......Page 206
9.1 Introduction......Page 208
9.2.2 Motivation for Goal-Based RE Approaches......Page 209
9.2.2.1 What Are Goals?......Page 211
9.2.3.1 Modeling Goals......Page 212
9.2.3.2 Formulating Goals......Page 215
9.2.3.3 Reasoning with Goals......Page 216
9.2.4 Weaknesses of Goal-Driven Approaches......Page 217
9.3.1.1 Motivations for Maps......Page 218
9.3.1.2 The Map Representation Formalism......Page 219
9.3.1.3 Illustrating Map with the SAP R3 Material Management Map......Page 223
9.3.2 Matching Maps to Support Multi-Purpose System Customization......Page 227
References......Page 230
Author Biography......Page 235
10.1 Introduction......Page 238
10.2 The Role of Natural Language Requirements......Page 239
10.3.1 Domain and Requirements Understanding......Page 241
10.3.2 Requirements Verification and Validation......Page 242
10.4 Requirements Similarity......Page 244
10.5 Case 1: Keeping the Repository in Shape......Page 247
10.5.2 Evaluation......Page 248
10.6 Case 2: Linking Customer Wishes to Product Requirements......Page 251
10.6.1 Case Study Requirements Data......Page 252
10.6.2 Evaluation......Page 253
10.7 Case 3: Managing Redundant Customer Requests......Page 255
10.7.1 Evaluation......Page 257
10.8 Conclusions......Page 259
References......Page 260
Author Biography......Page 263
11.1 Introduction......Page 264
11.2 Related Work......Page 266
11.3.1 Linguistic Ambiguity......Page 267
11.3.2 Software Engineering Ambiguity......Page 268
11.4.1 Sources of Ambiguity......Page 269
11.4.3 Design of Formalization Study......Page 270
11.4.4 Results of Formalization Study......Page 273
11.5.1 A Scenario-Based Reading Technique for Ambiguity......Page 276
11.5.2 Design and Results of Inspection Study......Page 279
11.5.3 Combination of Specification and Inspection Results......Page 280
11.6 How to Live with Ambiguity......Page 282
11.7 Summary and Conclusion......Page 283
References......Page 284
Author Biography......Page 285
12.1 Introduction......Page 286
12.2.1 Formulation of Decision Problems......Page 287
12.2.2 Structured versus Unstructured Decision Problems......Page 288
12.2.4 Requirement-Centric versus Activity-Centric Decision Problems......Page 289
12.2.6 A Collection of Requirements Engineering Decision Problems......Page 290
12.3.1 The Two Schools of Thinking......Page 292
12.3.2 Decision Making versus Decision Support for Software Release Planning......Page 293
12.4.1 Classification Scheme......Page 294
12.4.2 Scope......Page 295
12.4.3 Classification......Page 296
12.4.4 Main Observations......Page 298
12.5 Conclusion and Future Research......Page 300
Acknowledgements......Page 301
References......Page 302
Author Biography......Page 305
13.1 Introduction......Page 306
13.2.1 Basic Concepts......Page 308
13.2.2 Characteristics of MDRE......Page 310
13.2.3 Challenges in MDRE......Page 311
13.3.1 Process Quality......Page 312
13.4 MDRE Data Management......Page 315
13.4.1 Requirements State Model......Page 316
13.5 Market Analysis and Requirements Elicitation......Page 319
13.6 Roadmapping and Release Planning......Page 320
13.7 Conclusion......Page 323
Acknowledgements......Page 324
References......Page 325
Author Biography......Page 327
14.1 Introduction......Page 328
14.2 Agile Methods......Page 329
14.2.1 The Agile Manifesto......Page 330
14.2.2 Team Size in Agile Methods......Page 332
14.2.4 Applicability of Agile Methods across Application Domains......Page 333
14.3 Traditional and Agile Requirement Engineering......Page 334
14.4.1 The Customer......Page 335
14.4.2 Waste in Requirements......Page 336
14.4.3 Requirements Evolution......Page 338
14.5.1 The Customer......Page 340
14.6 Tools for Requirements Management in AMs......Page 341
Acknowledgements......Page 342
References......Page 343
Author Biography......Page 344
15.1 Introduction......Page 346
15.2.1 Web Engineering......Page 348
15.2.3 Howcroft’s Methodology......Page 349
15.2.5 Web Information Systems Development Methodology (WISDM)......Page 350
15.2.6 Comparison of Approaches......Page 351
15.3.1 Stakeholder Analysis......Page 353
15.3.2 Viewpoint Analysis......Page 355
15.3.3 Concern Analysis......Page 356
15.4 A Model of Concern-Driven Requirements Evolution......Page 358
15.5 Summary and Conclusion......Page 362
References......Page 363
Author Biography......Page 368
Part III: Studies and Industrial Experience......Page 370
16.1 Introduction......Page 372
16.2 The ABS Case Study Setting......Page 373
16.3 Governance of ABS Software Development......Page 375
16.4 The ABS Software Development Process......Page 377
16.5 The ABS Software Requirements Phase......Page 379
16.6 Some Examples of ABS Software......Page 384
16.7 What can We Learn From the ABS?......Page 386
References......Page 388
Author Biography......Page 391
17.1 Introduction......Page 392
17.2 Background......Page 393
17.3 Practice......Page 394
17.4 Evaluation......Page 396
17.4.1 Achievable/Feasible/Attainable......Page 404
17.4.2 Clear/ Precise/Meaningful......Page 405
17.4.3 Complete......Page 406
17.4.4 Concise......Page 408
17.4.5 Correct......Page 409
17.4.7 Externally Consistent......Page 410
17.4.8 Forward Traceable......Page 411
17.4.9 Internally Consistent......Page 413
17.4.10 Modifiable......Page 414
17.4.11 Necessary......Page 415
17.4.13 Prioritized/Ranked/Annotated......Page 416
17.4.15 Unambiguous......Page 419
17.4.16 Understandable......Page 420
17.5 Conclusions......Page 421
References......Page 422
Author Biography......Page 423
18.1 Introduction......Page 424
18.2 Studied Companies......Page 425
18.3.1 Model-Based Process Assessment......Page 426
18.3.2 Inductive Process Assessment......Page 430
18.4 Assessment Findings......Page 432
18.4.1 Model-based Assessment Results......Page 433
18.4.2 Inductive Assessment Results......Page 434
18.5 Comparison with State of Practice Surveys......Page 437
18.6 Discussion......Page 440
18.6.1 Other Issues......Page 442
References......Page 443
Author Biography......Page 445
19.1 Introduction......Page 446
19.2 Empirical Research......Page 447
19.3 Classification of Existing Broad RE Studies......Page 448
19.3.1 Set up of the Study......Page 451
19.3.2 Information on the Context and the Background of the Sample......Page 452
19.3.4 Information on Specific Parts of the RE Process......Page 454
19.4.1 Set up and Context of the Studies......Page 455
19.4.1.1 General Information on the RE Process......Page 456
19.4.1.2 Specific Parts of the RE Process......Page 458
19.5 Requirements Engineering Practice: A New Study......Page 461
19.6 Remarks on Empirical RE Research......Page 464
19.7 Conclusion......Page 465
References......Page 467
Author Biography......Page 470
20.1 Introduction......Page 472
20.2 A Requirements Engineering Framework: Available Solutions......Page 473
20.3.1 Commercial Off-the-Shelf Components and Systems......Page 479
20.3.2 Product Life Cycle Management......Page 483
20.3.3 Introducing Requirements Engineering into an Organization......Page 489
20.3.4 The Requirements Engineer’s Skill Sets......Page 490
20.4 Conclusions and Outlook: Where is Requirements Engineering Heading?......Page 492
References......Page 493
Author Biography......Page 495
Index......Page 496