: Timo Käköla, Juan Carlos Duenas
: Timo Käkölä, Juan Carlos Dueñas
: Software Product Lines Research Issues in Engineering and Management
: Springer-Verlag
: 9783540332534
: 1
: CHF 85.70
:
: Informatik
: English
: 635
: Wasserzeichen/DRM
: PC/MAC/eReader/Tablet
: PDF

This book covers research into the most important practices in product line organization. Contributors offer experience-based knowledge on the domain and application engineering, the modeling and management of variability, and the design and use of tools to support the management of product line-related knowledge.

Foreword by John D. McGregor5
Foreword by Frank van der Linden9
Introduction9
Quality Assurance10
Preface12
Introduction12
Why This Book?13
Which Questions are Answered by This Book?14
Acknowledgments16
Contents17
List of Contributors26
Part 1: Product Line Management32
Introduction32
1 A Scenario-Based Method for Software Product Line Architecting34
1.1 Introduction34
1.2 Research Method37
1.3 Method Overview39
1.4 Scenario-Based Architecting Applied45
1.5 Conclusions and Future Research80
Acknowledgments81
References81
2 Strategic Scenario-Based Valuation of Product Line Roadmaps84
2.1 Introduction84
2.2 Research Question85
2.3 Research Method86
2.4 Overview of Our Value Evaluation Approach87
2.5 Existing (Product Line) Cost and Value Models90
2.6 Product Line Pitfalls and Benefits100
2.7 A Case Inspired By Reality 107
2.8 Conclusions and Future Research117
Acknowledgments119
References119
3 Experiences and Expectations Regarding the Introduction of Systematic Reuse in Small-and Medium- Sized Companies122
3.1 Introduction122
3.2 Method and Sample of the Study124
3.3 State of Practice of Systematic Reuse in the Case Study129
3.4 Reuse Invest Specific Results131
3.5 Reuse Check Analysis Results142
Future152
References155
Acknowledgments155
Part 2: Product Line Requirements Engineering156
Introduction156
4 Capturing Product Line Information from Legacy User Documentation158
4.1 Introduction158
4.2 Problem161
4.3 Related Work164
4.4 Metamodel169
4.5 Method178
4.6 Validation of the Approach182
4.7 Conclusions and Future Research187
Acknowledgments188
References188
5 Scenario-Based Application Requirements Engineering192
5.1 Introduction192
5.2 Related Work197
5.3 The Orthogonal Variability Modeling Approach200
5.4 Use of the Orthogonal Variability Modeling Approach During Application Requirements Engineering205
5.5 Discussion of the Proposed Approach219
5.6 Conclusions and Future Research223
Acknowledgments223
References224
6 Consolidated Product Line Variability Modeling226
6.1 Introduction226
6.2 Variability in Standard Languages Exemplified by UML 2.0228
6.3 Variability by Enhancing Languages233
6.4 Domain-Specific Languages258
6.5 Evaluation264
6.6 Conclusions and Future Research270
References271
Acknowledgments271
Part 3: Product Line Architecture274
Introduction274
7 Dealing with Architectural Variation in Product Populations276
7.1 Introduction276
7.2 Architectural Variation279
7.3 Textural Variation Points283
7.4 Preliminary Validation288
7.5 Related Work300
7.6 Conclusions and Future Research301
Acknowledgments302
References303
8 A Software Product Line Reference Architecture for Security306
8.1 Introduction306
8.2 Security Architecture Design308
8.3 Conceptual Model of the Reference Architecture311
8.4 Quality Model318
8.5 Decision Model320
8.7 Using the Reference Architecture349
8.8 Validation351
8.9 Related Work354
8.10 Conclusions and Future Research355
References355
9 Architecture Reasoning for Supporting Product Line Evolution: An Example on Security358
9.1 Introduction358
9.2 Software Product Line Architecture360
9.3 Architecture Recovery363
9.4 Architectural Conformance369
9.5 Conformance and Recovery with Respect to Security372
9.6 The Case Study on Security for Distributed Systems378
9.7 Security Model Validation389
9.8 Conclusions and Future Research397
Acknowledgments399
References399
10 A Method for Predicting Reliability and Availability at the Architecture Level404
10.1 Introduction404
10.2 A Literature Survey of Applicable Methods and Techniques for R404
406404
10.3 Overview of the RAP Method410
10.4 Introduction of a Case Example412
10.5 The First Phase: Defining Reliability and Availability Goals415
10.6 The Second Phase: Representing Reliability and Availability in Architectural Models426
10.7 The Third Phase: Evaluating Reliability and Availability435
10.8 Discussion448
10.9 Conclusions and Future Research450
References