Using software product line engineering to construct products with different certification levels - An Industrial Action Research Study

Examensarbete för masterexamen

Please use this identifier to cite or link to this item: https://hdl.handle.net/20.500.12380/300148
Download file(s):
File Description SizeFormat 
CSE 19-45 Reitmaier Evertsson.pdf1.95 MBAdobe PDFView/Open
Full metadata record
DC FieldValueLanguage
dc.contributor.authorEvertsson, Oscar-
dc.contributor.authorReitmaier, Rebecka-
dc.contributor.departmentChalmers tekniska högskola / Institutionen för data och informationsvetenskapsv
dc.date.accessioned2019-08-21T12:43:24Z-
dc.date.available2019-08-21T12:43:24Z-
dc.date.issued2019sv
dc.date.submitted2019
dc.identifier.urihttps://hdl.handle.net/20.500.12380/300148-
dc.description.abstractBackground: Software product line engineering (SPLE) is used to derive multiple products from a common platform and has many industry examples of its benefits such as reduced development cost and decreased time to market. However, there is no research to our knowledge on how well it functions with agile development when there is a need to create both safety-critical products and non safety-critical products. The regulatory difference between these two is that the safety-critical products require certification to be sold. Aim: This thesis investigates which SPLE variability approaches can be used to differentiate code associated to a safety-critical and a non safety-critical product. The research was done at the company 1928 Diagnostics, with the goal of finding the most suitable variability approach for the company and how this might affect their business, architecture, process and organization. Method: We investigate variability approaches by looking at current SPLE literature and by using an action research methodology. The data is collected through interviews, focus groups, a mockup of a chosen variability approach and discussions at the company. Results: We identify five variability approaches that can support differentiation: design patterns, components, preprocessor, parameter-based and version control. We found that the most suitable variability approach for 1928 Diagnostics was components. From the evaluation of the mockup we found that potential effects primarily would be related to the architecture and the assistance it could provide to the process later. Finally, we present a methodology for how to derive the most suitable variability approach.sv
dc.language.isoengsv
dc.setspec.uppsokTechnology
dc.subjectSoftware Product Linesv
dc.subjectAgile Developmentsv
dc.subjectSafety-critical systemsv
dc.subjectDevelopment Processsv
dc.subjectCE-marked productssv
dc.subjectCertificationsv
dc.subjectMedical Devicesv
dc.subjectSoftware Engineeringsv
dc.titleUsing software product line engineering to construct products with different certification levels - An Industrial Action Research Studysv
dc.type.degreeExamensarbete för masterexamensv
dc.type.uppsokH
dc.contributor.examinerFeldt, Robert-
dc.contributor.supervisorSteghöfer, Jan-Philipp-
dc.identifier.coursecodeDATX05sv
Collection:Examensarbeten för masterexamen // Master Theses



Items in DSpace are protected by copyright, with all rights reserved, unless otherwise indicated.