Abstract

Companies currently use product lines to enhance products qualities and to lower the development and marketing costs. Many approaches available to support product lines, but most of them fail to address safety critical requirements in their approaches. In this paper we present DOPLER+, an approach to handle safety critical system requirements and the addition of new safety critical requirements, and their influences on other features and requirement within the product line. To illustrate our approach, we apply DOPLER+ to mobile robot case study.

Highlights

  • The main goal of software Product line (SPL) is to decrease the efforts by increasing the degree of reuse in software engineering

  • In this paper we present DOPLER+, an approach to handle safety critical system requirements and the addition of new safety critical requirements, and their influences on other features and requirement within the product line

  • Software product lines is defined as “a set of software-intensive systems that share a common, managed set of features satisfying the specific needs of a particular market segment or mission and that are developed from a common set of core assets in a prescribed way” (Bergey et al, 2005)

Read more

Summary

Introduction

The main goal of software Product line (SPL) is to decrease the efforts by increasing the degree of reuse in software engineering. One of the major research issues in PLE is how to handle safety critical features in product lines; and how to add new safety critical features to the product line (Heider et al, 2012). In this paper we present DOPLER+, an expansion of DOPLER (Decision-Oriented Product Line Engineering for Effective Reuse) approach (Dhungana et al, 2011) and DOPLERUcon (Rabiser & Dhungana, 2007) to deal with the effects of adding a safety critical safety requirement to a PLE. Current version of DOPLER doesn’t handle safety requirements and rely on the engineers to do it manually. We use the work of (Dehlinger & Lutz, 2004), SFTA analysis for product lines to modify the current version DOPLERUcon.

Related Work
DOPLERUCON
Conclusion
Full Text
Paper version not known

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.