Requirement Validation for Embedded Systems in Automotive Industry Through Modeling

Abstract

Requirement validation contributes significantly toward the success of software projects. Validating requirements is also essential to ensure the correctness of embedded systems in the auto industry. The auto industry emphasizes a lot on the verification of car designs and shapes. Invalid or erroneous requirements lead to inappropriate designs and degraded product quality. Considering the required expertise and time for requirement validation, significant attention is not devoted to verification and validation of requirements in the industry. Currently, the failure ratio of software projects is significantly higher and the key reason for that appears to be the inappropriate and invalidated requirements at the early stages in the projects. To that end, we propose a model-based approach that uses the existing V&V model. Through virtual prototyping, the proposed approach eliminates the need to validate the requirements after each stage of the project. Consequently, the model is validated after the design phase and the errors in requirements are detected at the earliest stage. In this research, we performed two different case studies for requirement validation in the auto industry by using a modeling-based approach and formal technique using Petri nets. A benefit of the proposed modeling-based approach is that the projects in the auto industry domain can be completed in less time due to effective requirements validation. Moreover, the modeling-based approach minimizes the development time, cost and increases productivity because the majority of the code is automatically generated using the approach.

Verification and validation of embedded software in an automotive context: a systematic literature review

“…V&V activities are divided into two main categories: static tests do not necessarily need working software and they can be based on a functional model or even specifications, while dynamic tests run the actual software and not just a reference model. Multiple other authors have also described software testing in the same manner (SZALAY et al, 2021;IQBAL, 2020;JORDAN et al, 2019;NEUROHR, 2021;DURISIC, 2013;DELAMARO, 2007;JINO, 2007;MALDONADO, 2007). Szalay et al (2021) unit testing aims to evaluate the interaction of the smallest part of a software or internal flow limit component.…”

“…that involving key stakeholders in the creation/adjustment of a RIM for a specific project will bring the benefit of a common language and compliance with standards. Other authors also mentioned benefits such as a high degree of integration between teams, increased quality of deliverables, precise definition of tasks, and detailed specifications of the developed functions that will be useful in the testing phase (SZALAY et al, 2021;IQBAL, 2020;JORDAN et al, 2019;NEUROHR, 2021;DURISIC, 2013;LOCHAU, 2014). (KASOJU, 2013;PETERSERN, 2013;MÄNTYLÄ, 2013) stated that there is no evidence on how the automotive industry tests software nowadays.…”

“…RQ4 was aimed at elaborating the main standards available for guiding the development and testing of embedded automotive software. Many of the selected articles cited ISO 26262 as a reference standard (CHOI, 2018;SZALAY et al, 2021;IQBAL, 2020;JORDAN et al, 2019;NEUROHR et al, 2021;DURISIC, 2013;LOCHAU, 2014;ANTINYAN, 2017;STARON, 2017;WIECHER, 2019;GREENYER, 2019;KORTE, 2019;VÖST et al, 2016;FERNANDEZ et al, 2015;BERNARDI et al, 2016). Szalay et al (2021) argued that the safety goals of the V&V process should be defined according to ISO 26262.…”

Software requirements modeling from the selected set of requirements using fuzzy based approach

“…The proposed method has been validated using various public software projects. Iqbal et al [35] proposed a model-based approach using a verification and validation model. The authors have validated the proposed approach using two different case studies from the auto industry.…”