Managed Evolution of Automotive Software Product Line Architectures: A Systematic Literature Study

The rapidly growing number of software-based features in the automotive domain as well as the special requirements in this domain ask for dedicated engineering approaches, models, and processes. Nowadays, software development in the automotive sector is generally developed as product line development, in which major parts of the software are kept adaptable in order to enable reusability of the software in different vehicle variants. In addition, reuse also plays an important role in the development of new vehicle generations in order to reduce development costs. Today, a high number of methods and techniques exist to support the product line driven development of software in the automotive sector. However, these approaches generally consider only partial aspects of development. In this paper, we present an in-depth literature study based on a conceptual model of artifacts and activities for the managed evolution of automotive software product line architectures. We are interested in the coverage of the particular aspects of the conceptual model and, thus, the fields covered in current research and research gaps, respectively. Furthermore, we aim to identify the methods and techniques used to implement automotive software product lines in general, and their usage scope in particular. As a result, this in-depth review reveals that none of the studies represent a holistic approach for the managed evolution of automotive software product lines. In addition, approaches from agile software development are of growing interest in this field

Model Quality Assessment in Practice: How to Measure and Assess the Quality of Software Models During the Embedded Software Development Process

International audienceIn this paper we present an approach for assessing the quality of model-based software projects. We demonstrate this approach in embedded software projects in the automotive domain. Our methodology can however be extended to other fields of software development. In general, the quality assessment of software projects is often based on quality criteria such as maintainability, testability, readability of the software or the software model. Our approach expands this basic assessment in that we assess the quality of a project on the basis of the success or degree of realization of quality operations (testing, reviews, etc.) respectively. Furthermore, we do not focus on single artifacts of the development process (e.g. model or code); rather we take all relevant development artifacts into account and use their interrelations to obtain metrics and key figures. We demonstrate our approach using our tool, Model Quality Assessment Center (MQAC), which was expressly developed for this purpose

An investigation of model-based techniques for automotive electronic system development

Over the past decades, the adoption of electronic systems for the manufacturing of automotive vehicles has been exponentially popularized. This growth has been driven by the premium automobile sector where, presently, diverse electronic systems are used. These electronic systems include systems that control the engine, transmission, suspension and handling of a vehicle; air bag and other advanced restraint systems; comfort systems; security systems; entertainment and information (infotainment) systems. In systems terms, automotive embedded electronic systems can now be classified as a System of Systems (SoS). Automotive systems engineering requires a sustainable integration of new methods, development processes, and tools that are specifically adapted to the automotive domain. Model-based design is one potential methodology to carry out design, implement and manage such complex distributed systems, and their integration into one cohesive and reliable SoS to meet the challenges for the automotive industry. This research was conducted to investigate the model-based design of a 4×4 Information System, within an automotive electronic SoS. Two distinct model-based approaches to the development of an automotive electronic system are discussed in this study. The first approach involves the use of the Systems Modelling Language (SysML) based tool ARTiSAN Studio for structural modelling, functional modelling and code generation. The second approach involves the use of the MATLAB based tools Simulink and Stateflow for functional modelling, and code generation. The results show that building the model in SysML by using ARTiSAN Studio provides a clearly structured visualization of the 4×4 Information System from both structural and behavioural viewpoints of the system with relevant objects. SysML model facilitates a more comprehensive understanding of the system than the model built in Simulink/Stateflow. The Simulink/Stateflow model demonstrates its superior performance in producing high quality and better efficiency of C code for the automotive software delivery compared with the model built in ARTiSAN Studio. Furthermore, this Thesis also gets insight into an advanced function development approach based on the real-time simulation and animation for the 4×4 Information System. Finally, the Thesis draws conclusions about how to make use of model-based design for the development of an automotive electronic SoS

Applying Model Based Techniques for Early Safety Evaluation of an Automotive Architecture in Compliance with the ISO 26262 Standard

International audienceIn 2011, the automotive industry introduced the application of a standardized process for functional safety-related development of automotive electronic products. The related international standard, ISO 26262 functional safety for road vehicles, has high demands on process documentation and analysis. Within an engineering context this challenges the tremendous increase of complexity for modern automotive systems and high productivity demands for industrial competiveness purpose. Model based development techniques based on an Architecture Description Language (ADL) has been identified as the best candidate to manage the system complexity and the related safety analysis with the benefit of formal description and capabilities for test automation. The proposed concept relies on the definition of a compositional error modeling approach tightly coupled with the system architecture model, capable to analyze the software and hardware architectures and implementations. This paper explains the results of the language extension based on the EAST-ADL and AUTOSAR domain model in terms of early safety evaluation of an automotive architecture, automating the qualitative and quantitative assessment of road vehicle products as claimed by the application of the ISO 26262

A Model-based Approach towards Human-Machine-Interfaces

International audienceSpecification and development of Human-Machine-Interfaces (HMI) for infotainment systems pose a difficult challenge for those automotive OEMs who claim this topic as one of their core competences. Experience shows that a major problem arises from the non optimal communication of all involved parties during the HMI development. This article describes a model-based approach towards HMI-development which combines conceptual design, specification and implementation based on a single complete HMI-model which serves as an improved means of communication between designers, ergonomists and software developers

Systematic Testing of Embedded Automotive Software - The Classification-Tree Method for Embedded Systems (CTM/ES)

The software embedded in automotive control systems increasingly determines the functionality and properties of present-day motor vehicles. The development and test process of the systems and the software embedded becomes the limiting factor. While these challenges, on the development side, are met by employing model-based specification, design, and implementation techniques [KCF+04], satisfactory solutions on the testing side are slow in arriving. With regard to the systematic selection (test design) and the description of test scenarios especially, there is a lot of room for improvement. Thus, a main goal is to effectively minimize these deficits by creating an efficient procedure for the selection and description of test scenarios for embedded automotive software and its integration in the model-based development process. The realization of this idea involves the combination of a classical software testing procedure with a technology, prevalent in the automotive industry, which is used for the description of time-dependent stimuli signals. The result of this combination is the classification-tree method for embedded systems, CTM/ES [Con04]. The classification-tree method for embedded systems complements model-based development by employing a novel approach to the systematic selection and description of the test scenarios for the software embedded in the control systems. CTM/ES allows for the graphic representation of time-variable test scenarios on different levels of abstraction: A problem-oriented, compact representation, adequate for a human tester and containing a high potential for reusability, is gradually being transformed into a solution-oriented technical representation which is suited for the test objects\u27 stimulation. The CTM/ES notation facilitates a consistent representation of test scenarios which may result from different test design techniques. The test design technique which this method is primarily based on, is a data-oriented partitioning of the input domain in equivalence classes. Secondary test design techniques are, for instance, the testing of specific values (or value courses) or requirement-based testing. A domain-specific application pragmatics in the form of agendas supports the methodical execution of individual test activities and the interaction of different test design techniques. The methodology description leads up to an effective test strategy for model-based testing, combining the classification-tree method for embedded systems with structural testing on the model level, and accommodating the different forms of representation of the test object during model-based development. Systems which have been developed in a model-based way can be tested systematically and efficiently by means of the CTM/ES and the tools based thereon, such as the classification-tree editor for embedded systems CTE/ES [CTE/ES], as well as the model-based test environment MTest [LBE+04, MTest]

Automatic Safety mechanisms implementation in Software Model-Based Development

International audienceModel Based Development (MBD) is now a common approach for the automotive industry. Using modeling tools to simulate the behavior of a system before developing the corresponding product(s) through automatic code generation has proven its efficiency. The Road vehicles — Functional safety — ISO 26262 standard (Part6 ) [2] identifies MBD as a recommended approach especially for software architecture design with semi-formal notation and software verification with back-to-back testing through Model in the Loop (MIL) , Software in the Loop (SIL) and Processor in the Loop (PIL). Regarding error detection the standard recommends a certain number of monitoring methods such as “Range checks of input and output data”, “Plausibility check”, “Control flow monitoring”, but does not give any concrete recommendation for software implementation of those methods and therefore how to test through fault injection. In the MBD approach, since code is generated automatically, safety mechanisms must be introduced at model level

A Comprehensive Safety Engineering Approach for Software-Intensive Systems Based on STPA

Formal verification and testing are complementary approaches which are used in the development process to verify the functional correctness of software. However, the correctness of software cannot ensure the safe operation of safety-critical software systems. The software must be verified against its safety requirements which are identified by safety analysis, to ensure that potential hazardous causes cannot occur. The complexity of software makes defining appropriate software safety requirements with traditional safety analysis techniques difficult. STPA (Systems-Theoretic Processes Analysis) is a unique safety analysis approach that has been developed to identify system hazards, including the software-related hazards. This paper presents a comprehensive safety engineering approach based on STPA, including software testing and model checking approaches for the purpose of developing safe software. The proposed approach can be embedded within a defined software engineering process or applied to existing software systems, allow software and safety engineers integrate the analysis of software risks with their verification. The application of the proposed approach is illustrated with an automotive software controller