E-Book, Englisch, 635 Seiten
Käkölä / Käköla / Dueñas Software Product Lines
1. Auflage 2007
ISBN: 978-3-540-33253-4
Verlag: Springer Berlin Heidelberg
Format: PDF
Kopierschutz: 1 - PDF Watermark
Research Issues in Engineering and Management
E-Book, Englisch, 635 Seiten
ISBN: 978-3-540-33253-4
Verlag: Springer Berlin Heidelberg
Format: PDF
Kopierschutz: 1 - PDF Watermark
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.
Autoren/Hrsg.
Weitere Infos & Material
1;Foreword by John D. McGregor;5
2;Foreword by Frank van der Linden;9
2.1;Introduction;9
2.2;Quality Assurance;10
3;Preface;12
3.1;Introduction;12
3.2;Why This Book?;13
3.3;Which Questions are Answered by This Book?;14
3.4;Acknowledgments;16
4;Contents;17
5;List of Contributors;26
6;Part 1: Product Line Management;32
6.1;Introduction;32
6.2;1 A Scenario-Based Method for Software Product Line Architecting;34
6.2.1;1.1 Introduction;34
6.2.2;1.2 Research Method;37
6.2.3;1.3 Method Overview;39
6.2.4;1.4 Scenario-Based Architecting Applied;45
6.2.5;1.5 Conclusions and Future Research;80
6.2.6;Acknowledgments;81
6.2.7;References;81
6.3;2 Strategic Scenario-Based Valuation of Product Line Roadmaps;84
6.3.1;2.1 Introduction;84
6.3.2;2.2 Research Question;85
6.3.3;2.3 Research Method;86
6.3.4;2.4 Overview of Our Value Evaluation Approach;87
6.3.5;2.5 Existing (Product Line) Cost and Value Models;90
6.3.6;2.6 Product Line Pitfalls and Benefits;100
6.3.7;2.7 A Case Inspired By Reality ;107
6.3.8;2.8 Conclusions and Future Research;117
6.3.9;Acknowledgments;119
6.3.10;References;119
6.4;3 Experiences and Expectations Regarding the Introduction of Systematic Reuse in Small-and Medium- Sized Companies;122
6.4.1;3.1 Introduction;122
6.4.2;3.2 Method and Sample of the Study;124
6.4.3;3.3 State of Practice of Systematic Reuse in the Case Study;129
6.4.4;3.4 Reuse Invest Specific Results;131
6.4.5;3.5 Reuse Check Analysis Results;142
6.4.6;Future;152
6.4.7;References;155
6.4.8;Acknowledgments;155
7;Part 2: Product Line Requirements Engineering;156
7.1;Introduction;156
7.2;4 Capturing Product Line Information from Legacy User Documentation;158
7.2.1;4.1 Introduction;158
7.2.2;4.2 Problem;161
7.2.3;4.3 Related Work;164
7.2.4;4.4 Metamodel;169
7.2.5;4.5 Method;178
7.2.6;4.6 Validation of the Approach;182
7.2.7;4.7 Conclusions and Future Research;187
7.2.8;Acknowledgments;188
7.2.9;References;188
7.3;5 Scenario-Based Application Requirements Engineering;192
7.3.1;5.1 Introduction;192
7.3.2;5.2 Related Work;197
7.3.3;5.3 The Orthogonal Variability Modeling Approach;200
7.3.4;5.4 Use of the Orthogonal Variability Modeling Approach During Application Requirements Engineering;205
7.3.5;5.5 Discussion of the Proposed Approach;219
7.3.6;5.6 Conclusions and Future Research;223
7.3.7;Acknowledgments;223
7.3.8;References;224
7.4;6 Consolidated Product Line Variability Modeling;226
7.4.1;6.1 Introduction;226
7.4.2;6.2 Variability in Standard Languages Exemplified by UML 2.0;228
7.4.3;6.3 Variability by Enhancing Languages;233
7.4.4;6.4 Domain-Specific Languages;258
7.4.5;6.5 Evaluation;264
7.4.6;6.6 Conclusions and Future Research;270
7.4.7;References;271
7.4.8;Acknowledgments;271
8;Part 3: Product Line Architecture;274
8.1;Introduction;274
8.2;7 Dealing with Architectural Variation in Product Populations;276
8.2.1;7.1 Introduction;276
8.2.2;7.2 Architectural Variation;279
8.2.3;7.3 Textural Variation Points;283
8.2.4;7.4 Preliminary Validation;288
8.2.5;7.5 Related Work;300
8.2.6;7.6 Conclusions and Future Research;301
8.2.7;Acknowledgments;302
8.2.8;References;303
8.3;8 A Software Product Line Reference Architecture for Security;306
8.3.1;8.1 Introduction;306
8.3.2;8.2 Security Architecture Design;308
8.3.3;8.3 Conceptual Model of the Reference Architecture;311
8.3.4;8.4 Quality Model;318
8.3.5;8.5 Decision Model;320
8.3.6;8.7 Using the Reference Architecture;349
8.3.7;8.8 Validation;351
8.3.8;8.9 Related Work;354
8.3.9;8.10 Conclusions and Future Research;355
8.3.10;References;355
8.4;9 Architecture Reasoning for Supporting Product Line Evolution: An Example on Security;358
8.4.1;9.1 Introduction;358
8.4.2;9.2 Software Product Line Architecture;360
8.4.3;9.3 Architecture Recovery;363
8.4.4;9.4 Architectural Conformance;369
8.4.5;9.5 Conformance and Recovery with Respect to Security;372
8.4.6;9.6 The Case Study on Security for Distributed Systems;378
8.4.7;9.7 Security Model Validation;389
8.4.8;9.8 Conclusions and Future Research;397
8.4.9;Acknowledgments;399
8.4.10;References;399
8.5;10 A Method for Predicting Reliability and Availability at the Architecture Level;404
8.5.1;10.1 Introduction;404
8.5.2;10.2 A Literature Survey of Applicable Methods and Techniques for R& A Prediction;406
8.5.3;10.3 Overview of the RAP Method;410
8.5.4;10.4 Introduction of a Case Example;412
8.5.5;10.5 The First Phase: Defining Reliability and Availability Goals;415
8.5.6;10.6 The Second Phase: Representing Reliability and Availability in Architectural Models;426
8.5.7;10.7 The Third Phase: Evaluating Reliability and Availability;435
8.5.8;10.8 Discussion;448
8.5.9;10.9 Conclusions and Future Research;450
8.5.10;References;451
9;Part 4: Product Line Testing;454
9.1;Introduction;454
9.2;11 Product Line Use Cases: Scenario-Based Specification and Testing of Requirements;456
9.2.1;11.1 Introduction;456
9.2.2;11.2 PLUC Notation;458
9.2.3;11.3 PUC Derivation from PLUC;464
9.2.4;11.4 Using PLUCs for Derivation of Test Scenarios;465
9.2.5;11.5 Related Work;473
9.2.6;11.6 Conclusions and Future Research;474
9.2.7;References;475
9.2.8;Acknowledgments;475
9.3;12 System Testing of Product Lines: From Requirements to Test Cases;478
9.3.1;12.1 Introduction;478
9.3.2;12.2 Overview of the Approach;480
9.3.3;12.3 An Enhanced Use Case Model for Product;484
9.3.4;12.4 Simulating the Use Cases;487
9.3.5;12.5 Test Objectives;489
9.3.6;12.6 Test Case Generation;493
9.3.7;12.7 Results and Discussion;501
9.3.8;12.8 Conclusions and Future Research;506
9.3.9;References;507
9.3.10;Acknowledgments;507
9.4;13 The ScenTED Method for Testing Software Product Lines;510
9.4.1;13.1 Introduction;510
9.4.2;13.2 Basics of the ScenTED Method;513
9.4.3;13.3 ScenTED in Domain Engineering;515
9.4.4;13.4 ScenTED in Application Engineering;524
9.4.5;13.5 ScenTED at Siemens Medical Solutions - A Case Study;544
9.4.6;13.6 Conclusions and Future Research;548
10;Part 5: Specific Product Line Engineering Issues;552
10.1;Introduction;552
10.2;14 Incremental Systems Integration within Multidisciplinary Product Line Engineering Using Configuration Item Evolution Diagrams;554
10.2.1;14.1 Introduction;554
10.2.2;14.2 Configuration Management and Problems with Integration;557
10.2.3;14.3 Solving the Problems by Using the Configuration Item Evolution Diagram (CIED);559
10.2.4;14.4 A Preliminary Validation of the Proposed Solution;576
10.2.5;14.5 Conclusions and Future Research;583
10.2.6;Acknowledgments;585
10.2.7;References;585
10.3;15 Software Product Line Engineering with the UML: Deriving Products;588
10.3.1;15.1 Introduction;588
10.3.2;15.2 Deriving Static Aspects;589
10.3.3;15.3 Deriving Behavioral Aspects;598
10.3.4;15.4 Related Work;614
10.3.5;15.5 Conclusions and Future Research;616
10.3.6;References;617
10.3.7;Acknowledgments;617
10.4;16 Evaluation Framework for Model-Driven Product Line Engineering Tools;620
10.4.1;16.1 Introduction;621
10.4.2;16.2 Combining Model-Driven Development and Product Line Engineering;622
10.4.3;16.3 Tool Evaluation Framework;625
10.4.4;16.4 Examples of Tool Evaluations;631
10.4.5;16.5 Evaluation of the Framework;644
10.4.6;16.6. Conclusions and Future Research;647
10.4.7;Acknowledgments;648
10.4.8;References;648
11;Glossary;650
12;Index;656




