Current requirements engineering (RE) practice in industry lacks the availability of an integrated guide that defines and supports the requirements engineering part of embedded system development. Therefore, the RE part of a development project is not as structured and defined as desired. This paper presents results of an experiment validating a RE guide developed by a joint research project between industry and academia. In the experiment carried out for 14 weeks, embedded development projects using the guide were compared to projects following a state-of-the-practice process. The results suggest the guide to be suitable for mastering the RE part of an embedded system development.

No abstract

This paper analyzes concepts to measure benefits of quality assurance measures applied in the electric / electronics (E/E) development in the automotive domain. Therefore selected models are examined and their suitability in the given context is evaluated. Since typical models in literature do not fulfil the practical requirements, the goal is to develop an extensive cost-benefit model based on organization specific cause-andeffect chains embracing software but also hardware development aspects. In a first example, based on the experiences in a software engineering experiment with 20 students, the applicability of the defined cause-and-effect chains with their according metrics is shown. Further research aims on process simulation to ensure plausibility and case studies for the validation of the presented approach. The development of electric / electronics (E/E) for OEMs (Original Equipment Manufacturer) in the automotive domain is characterized by developing not only software but also hardware. Additionally the V-Model is usually not run entirely by the OEM: In most of the projects, component specifications are written on the OEM´s side while the supplier develops the actual Electronic Control Unit (ECU) with the according hard-and software. The OEM himself performs the subsequent integration tests and monitors the development of the supplier [7][9].There are many different projects in an OEM´s development concerning the complexity of the functions, the number of developers involved, the safety-criticality of the component, the inhouse-depth of development and so forth. While one variant of a quality measure (e.g. walkthroughs and inspections as variants of reviews) works fine for a project it may not be efficient in another one with changed characteristics.As stated by Barry Boehm, much of current software engineering still happens in a value neutral setting putting in danger the project outcomes [1]. In practice relevant factors are taking into account but not always in a proper systematic way. Facing the described scenario, value must be considered when deciding about which quality assurance (QA) measure fits best to specific projects. To ensure the efficient deployment of QA measures (e.g. reviews and integration tests), models are needed that are able to prioritize QA measures and suggest certain variants of QA measures considering the defined processes and the needs of very different projects in the automotive E/E development context. Hence the presented research aims on the development of such an extensive model which allows prognoses for project managers to decide which variants of QA measure fit best to a specific project.Whereas costs can usually be measured quite well in practice, the measurement of benefit is difficult. Thus the following research questions are addressed to develop the model:•What are the qualitative impacts of QA measures? Which are the causal chains? • How can the impacts be measured? What are the right metrics to measure these impacts? •How can the benefit of these impacts be meas...