| Foreword by John D. McGregor | 5 |
|---|
| Foreword by Frank van der Linden | 9 |
|---|
| Introduction | 9 |
| Quality Assurance | 10 |
| Preface | 12 |
|---|
| Introduction | 12 |
| Why This Book? | 13 |
| Which Questions are Answered by This Book? | 14 |
| Acknowledgments | 16 |
| Contents | 17 |
|---|
| List of Contributors | 26 |
|---|
| Part 1: Product Line Management | 32 |
|---|
| Introduction | 32 |
| 1 A Scenario-Based Method for Software Product Line Architecting | 34 |
| 1.1 Introduction | 34 |
| 1.2 Research Method | 37 |
| 1.3 Method Overview | 39 |
| 1.4 Scenario-Based Architecting Applied | 45 |
| 1.5 Conclusions and Future Research | 80 |
| Acknowledgments | 81 |
| References | 81 |
| 2 Strategic Scenario-Based Valuation of Product Line Roadmaps | 84 |
| 2.1 Introduction | 84 |
| 2.2 Research Question | 85 |
| 2.3 Research Method | 86 |
| 2.4 Overview of Our Value Evaluation Approach | 87 |
| 2.5 Existing (Product Line) Cost and Value Models | 90 |
| 2.6 Product Line Pitfalls and Benefits | 100 |
| 2.7 A Case Inspired By Reality | 107 |
| 2.8 Conclusions and Future Research | 117 |
| Acknowledgments | 119 |
| References | 119 |
| 3 Experiences and Expectations Regarding the Introduction of Systematic Reuse in Small-and Medium- Sized Companies | 122 |
| 3.1 Introduction | 122 |
| 3.2 Method and Sample of the Study | 124 |
| 3.3 State of Practice of Systematic Reuse in the Case Study | 129 |
| 3.4 Reuse Invest Specific Results | 131 |
| 3.5 Reuse Check Analysis Results | 142 |
| Future | 152 |
| References | 155 |
| Acknowledgments | 155 |
| Part 2: Product Line Requirements Engineering | 156 |
|---|
| Introduction | 156 |
| 4 Capturing Product Line Information from Legacy User Documentation | 158 |
| 4.1 Introduction | 158 |
| 4.2 Problem | 161 |
| 4.3 Related Work | 164 |
| 4.4 Metamodel | 169 |
| 4.5 Method | 178 |
| 4.6 Validation of the Approach | 182 |
| 4.7 Conclusions and Future Research | 187 |
| Acknowledgments | 188 |
| References | 188 |
| 5 Scenario-Based Application Requirements Engineering | 192 |
| 5.1 Introduction | 192 |
| 5.2 Related Work | 197 |
| 5.3 The Orthogonal Variability Modeling Approach | 200 |
| 5.4 Use of the Orthogonal Variability Modeling Approach During Application Requirements Engineering | 205 |
| 5.5 Discussion of the Proposed Approach | 219 |
| 5.6 Conclusions and Future Research | 223 |
| Acknowledgments | 223 |
| References | 224 |
| 6 Consolidated Product Line Variability Modeling | 226 |
| 6.1 Introduction | 226 |
| 6.2 Variability in Standard Languages Exemplified by UML 2.0 | 228 |
| 6.3 Variability by Enhancing Languages | 233 |
| 6.4 Domain-Specific Languages | 258 |
| 6.5 Evaluation | 264 |
| 6.6 Conclusions and Future Research | 270 |
| References | 271 |
| Acknowledgments | 271 |
| Part 3: Product Line Architecture | 274 |
|---|
| Introduction | 274 |
| 7 Dealing with Architectural Variation in Product Populations | 276 |
| 7.1 Introduction | 276 |
| 7.2 Architectural Variation | 279 |
| 7.3 Textural Variation Points | 283 |
| 7.4 Preliminary Validation | 288 |
| 7.5 Related Work | 300 |
| 7.6 Conclusions and Future Research | 301 |
| Acknowledgments | 302 |
| References | 303 |
| 8 A Software Product Line Reference Architecture for Security | 306 |
| 8.1 Introduction | 306 |
| 8.2 Security Architecture Design | 308 |
| 8.3 Conceptual Model of the Reference Architecture | 311 |
| 8.4 Quality Model | 318 |
| 8.5 Decision Model | 320 |
| 8.7 Using the Reference Architecture | 349 |
| 8.8 Validation | 351 |
| 8.9 Related Work | 354 |
| 8.10 Conclusions and Future Research | 355 |
| References | 355 |
| 9 Architecture Reasoning for Supporting Product Line Evolution: An Example on Security | 358 |
| 9.1 Introduction | 358 |
| 9.2 Software Product Line Architecture | 360 |
| 9.3 Architecture Recovery | 363 |
| 9.4 Architectural Conformance | 369 |
| 9.5 Conformance and Recovery with Respect to Security | 372 |
| 9.6 The Case Study on Security for Distributed Systems | 378 |
| 9.7 Security Model Validation | 389 |
| 9.8 Conclusions and Future Research | 397 |
| Acknowledgments | 399 |
| References | 399 |
| 10 A Method for Predicting Reliability and Availability at the Architecture Level | 404 |
| 10.1 Introduction | 404 |
| 10.2 A Literature Survey of Applicable Methods and Techniques for R | 404 |
| 406 | 404 |
|---|
| 10.3 Overview of the RAP Method | 410 |
| 10.4 Introduction of a Case Example | 412 |
| 10.5 The First Phase: Defining Reliability and Availability Goals | 415 |
| 10.6 The Second Phase: Representing Reliability and Availability in Architectural Models | 426 |
| 10.7 The Third Phase: Evaluating Reliability and Availability | 435 |
| 10.8 Discussion | 448 |
| 10.9 Conclusions and Future Research | 450 |
| References
|