: Allen H. Dutoit, Raymond McCall, Ivan Mistrík, Barbara Paech
: Allen H. Dutoit, Raymond McCall, Ivan Mistrik, Barbara Paech
: Rationale Management in Software Engineering
: Springer-Verlag
: 9783540309987
: 1
: CHF 85.50
:
: Informatik
: English
: 434
: Wasserzeichen/DRM
: PC/MAC/eReader/Tablet
: PDF

This is a detailed summary of research on design rationale providing researchers in software engineering with an excellent overview of the subject. Professional software engineers will find many examples, resources and incentives to enhance their ability to make decisions during all phases of the software lifecycle. Software engineering is still primarily a human-based activity and rationale management is concerned with making design and development decisions explicit to all stakeholders involved.

Foreword6
Preface8
Introduction8
Book Overview9
Contents12
Contributors18
Rationale Management in Software Engineering: Concepts and Techniques22
1.1 Introduction22
1.2 Design Rationale Fundamentals24
1.3 Approaches to Design Rationale28
1.4 Uses of DR and DR Methods37
1.5 Limitations of Current DR Approaches and Software41
1.6 Rationale Management in Software Engineering45
1.7 Tool Support for Rationale Management57
1.8 Conclusion64
Part 1 Fundamentals – Rationale Representation, Capture, and Use70
Three Studies of Design Rationale as Explanation74
2.1 Introduction74
2.2 Explanations of Complex Systems76
2.3 Design Rationale as Explanation Content77
2.4 Three Cases of Design Rationale as Explanation79
2.5 Challenges and Opportunities for Design Rationale as Explanation88
2.6 Conclusion89
Effective Design Rationale: Understanding the Barriers93
3.1 Introduction93
3.2 Design Perspectives and Rationale94
3.3 The Fundamental Barriers98
3.4 Transcending the Barriers105
3.5 Conclusions108
Rationale as a By-Product111
4.1 Introduction111
4.2 Origins of Rationale in Software Projects112
4.3 Rationale as a By-Product114
4.4 Case 1: Capturing Rationale in Software Prototypes121
4.5 Case 2: Risk Analysis124
4.6 Discussion126
4.7 Conclusions127
Hypermedia Support for Argumentation- Based Rationale: 15 Years on from gIBIS and QOC130
5.1 Introduction and Overview130
5.2 The Vision131
5.3 The Design Rationale Capture Problem132
5.4 Understanding Cognitive Overhead133
5.5 Compendium134
5.6 Reasoning Services and Verification141
5.7 Revisiting ‘Intrusiveness’142
5.8 Examples of Compendium in Use143
5.9 Lessons Learnt and Conclusions148
Part 2 Rationale Management for Requirements Engineering152
A Hybrid Approach to Upstream Requirements: IBIS and Cognitive Mapping156
6.1 Introduction156
6.2 The Process157
6.3 The Tool163
6.4 Example165
6.5 Experience167
6.6 Discussion169
From DREAM to Reality: Specificities of Interactive Systems Development With Respect To Rationale Management174
7.1 Introduction174
7.2 State of Art in Rationale Management for Interactive Systems175
7.3 TEAM Notation176
7.4 DREAM Tool179
7.5 Case Study184
7.6 Conclusion189
The WinWin Approach: Using a Requirements Negotiation Tool for Rationale Capture and Use192
8.1 Introduction192
8.2 The Theory W and WinWin Spiral Model in Software Development Process194
8.3 Fundamental WinWin Concepts197
8.4 Tool Support for WinWin Requirements Negotiation201
8.5 An Example – Using WinWin in Software Development 203
8.6 Using the Captured Rationale to Improve Later Decisions 207
8.8 Future Directions208
8.7 Related Work208
Design Rationale in Exemplary Business Process Modeling210
9.1 Overview of Exemplary Business Process Modeling210
9.2 The EBPM Paradigm211
9.3 EBPM Models214
9.4 Capturing Design Rationale218
9.5 Relations to Other Approaches224
9.6 Conclusion225
Promoting and Supporting Requirements Engineering Creativity228
10.1 Introduction228
10.2 Overview of Design Rationale229
10.3 Understanding the RE Process 232
10.4 RE Creativity in Relation to Psychology of Problem Solving237
10.5 Using DR to Support Creative RE Process240
10.6 Summary and Conclusion245
Part 3 Design Rationale and Software Architecting250
A Framework for Supporting Architecture Knowledge and Rationale Management256
11.1 Introduction256
11.2 Background and Motivation257
11.3 Managing Architecture Design Knowledge 260
11.4 Conclusions and Open Issues270
Capturing and Using Rationale for a Software Architecture274
12.1 Introduction274
12.2 Structuring Rationale275
12.3 How will Architectural Design Rationale be Used? 281
12.4 Capturing Rationale284
12.5 An Example of Capturing and Using Rationale 288
12.6 Summary