An Assessment Model to Foster the Adoption of Agile Software Product Lines in the Automotive Domain
Philipp Hohl
Diese Publikation zitieren
Philipp Hohl, An Assessment Model to Foster the Adoption of Agile Software Product Lines in the Automotive Domain (2019), Logos Verlag, Berlin, ISBN: 9783832588892
147
Accesses
Accesses
4
Quotes
Quotes
Beschreibung / Abstract
The automotive industry is changing rapidly. E-Mobility, self-driving and other trends revolutionize the automotive industry. These trends have to be addressed when developing new car generations and future mobility solutions. This is challenging for the automotive domain with its special peculiarities such as rigid quality and safety requirements, deep integration between hardware and software, strong focus on development processes, and strong supplier involvement. Traditionally, software product lines have been used to cope with the large amount of software in cars by means of software reuse. Anyhow, there is a lack of knowledge about how to react flexibly on rapid changes with software product line development. The use of agile software development methods promises a flexible development with the possibility to react fast to changes.
Interviews, workshops and literature reviews revealed the necessity to combine agile practices with software product lines for automotive software development. The thesis identifies the factors that hinder or support the adoption of agile practices in the automotive domain. In addition, another essential goal of this thesis was to develop an approach for supporting organizations with the establishment of agile software product lines. In order to fulfill this goal, an assessment and improvement model, the so-called Agile Software Product Lines in Automotive Model (ASPLA Model), was developed to foster the adoption of agile software product lines in the automotive domain. The ASPLA Model identifies improvement potential for a change towards agile software product lines and provides a prioritized list of recommendations on how to combine agile software development with software product lines within the assessed development process. Main characteristics of the ASPLA Model are the compatibility with the widely-used ASPICE model, the integration of a new product-focused category and empirically-based recommendations.
The evaluation of the ASPLA Model indicated that the assessment can help to foster the combination of agile software development with software product lines in the automotive domain. A case study compared the results from the ASPLA Model with the assessment results from experts. In comparison with experts' assessments and recommendations, the model produced similar or even better results.
Interviews, workshops and literature reviews revealed the necessity to combine agile practices with software product lines for automotive software development. The thesis identifies the factors that hinder or support the adoption of agile practices in the automotive domain. In addition, another essential goal of this thesis was to develop an approach for supporting organizations with the establishment of agile software product lines. In order to fulfill this goal, an assessment and improvement model, the so-called Agile Software Product Lines in Automotive Model (ASPLA Model), was developed to foster the adoption of agile software product lines in the automotive domain. The ASPLA Model identifies improvement potential for a change towards agile software product lines and provides a prioritized list of recommendations on how to combine agile software development with software product lines within the assessed development process. Main characteristics of the ASPLA Model are the compatibility with the widely-used ASPICE model, the integration of a new product-focused category and empirically-based recommendations.
The evaluation of the ASPLA Model indicated that the assessment can help to foster the combination of agile software development with software product lines in the automotive domain. A case study compared the results from the ASPLA Model with the assessment results from experts. In comparison with experts' assessments and recommendations, the model produced similar or even better results.
Inhaltsverzeichnis
- BEGINN
- Acknowledgments
- Abstract
- Zusammenfassung
- List of Figures
- List of Tables
- Acronyms
- 1 Introduction
- 1.1 Background and Motivation
- 1.2 Research Scope
- 1.3 Research Approach
- 1.4 Goals
- 1.5 Research Questions
- 1.6 Hypotheses
- 1.7 Contributions of Thesis
- 1.8 Structure of Thesis
- 1.9 Chapter Summary
- 2 Theoretical Foundation
- 2.1 Automotive Assessment/Reference Models
- 2.2 Systematic Software Reuse Strategies
- 2.3 Agile Software Development
- 2.4 Agile Software Product Lines
- 2.5 Chapter Summary
- 3 State of the Practice
- 3.1 Automotive Software Engineering
- 3.2 Interview Study
- 3.3 Bene ts of Agile Software Product Lines
- 3.4 The Agile Adoption Forces Model
- 3.5 Automotive Challenges on Agile Software Product Lines
- 3.6 The Agile Software Product Line Portfolio
- 3.7 Lack of Structured Combination Approach
- 3.8 Chapter Summary
- 4 State of the Art
- 4.1 Automotive Agile Software Product Lines
- 4.2 Existing Maturity Models in Literature
- 4.3 Chapter Summary
- 5 The ASPLA Model
- 5.1 The Type of Research Artifact
- 5.2 Setting up the ASPLA Model
- 5.3 The ASPLA Model
- 5.4 Addressed Aspects of Norms and Standards
- 5.5 Conduct an ASPLA Assessment
- 5.6 Chapter Summary
- 6 Validation of the ASPLA Model
- 6.1 Hypotheses
- 6.2 Two-Step Validation Strategy
- 6.3 Phase 1: Iterative Learning
- 6.4 Phase 2: Case Study
- 6.5 Chapter Summary
- 7 Results
- 7.1 Methods to Establish an Agile Software Product Line
- 7.2 Transformation Tasks towards Agile Software Product Lines
- 7.3 Challenges of Agile Assessment Models
- 7.4 Automotive Speci c Aspects in Agile Software Product Line Assessments
- 7.5 The Modi cation of Existing Assessment Models
- 8 Related Work
- 9 Discussion
- 9.1 Critical Appraisal
- 9.2 Adherence to Design-Science Research Guidelines
- 9.3 Ful llment of Assessment Criteria
- 10 Conclusion and Future Work
- 10.1 Conclusion
- 10.2 Future Work
- Bibliography
- A ASPLA Model Assessment Results
- A.1 Recommendation List for Developer 1
- A.2 Recommendation List for Developer 2
- B Data Collection in Workshops
- B.1 Workshop 1: Agile Transformation with Arie van Bennekum
- B.2 Workshop 2: Daimler AG - Agile Development In-house
- B.3 Workshop 3: Daimler AG - Agile Open Space
- B.4 Workshop 4: Automated Testing of Software Variants
- B.5 Workshop 5: Agile Practices and Software Product Lines
- C Identi ed Challenges
- C.1 Organizational Challenges
- C.2 Software Product Line Challenges
- C.3 Agile Software Development Challenges
- C.4 Automotive Speci c Challenges
- D Identi ed Recommendations
- E The ASPLA Model
- E.1 Honeycomb 1: Product Line Architecture
- E.2 Honeycomb 2: Domain Requirements Engineering
- E.3 Honeycomb 3: Agile Software Development
- E.4 Honeycomb 4: Continuous X
- E.5 Honeycomb 5: Continuous Model Improvement
- E.6 Honeycomb 6: Test Strategy
- E.7 Honeycomb 7: Communication
- E.8 ASPLA Work Products
- E.9 Assessment Questions
- E.10 The Relationship between the ASPLA Model and Standards
- F Literature Reviews
- F.1 Agile Software Product Lines
- F.2 Automotive Agile Software Product Line Assessments
- G Publications
- CV