Why feature dependencies challenge the requirements engineering of automotive systems: An empirical study

@article{Vogelsang2013WhyFD,
  title={Why feature dependencies challenge the requirements engineering of automotive systems: An empirical study},
  author={Andreas Vogelsang and Steffen Fuhrmann},
  journal={2013 21st IEEE International Requirements Engineering Conference (RE)},
  year={2013},
  pages={267-272}
}
Functional dependencies and feature interactions in automotive software systems are a major source of erroneous and deficient behavior. To overcome these problems, many approaches exist that focus on modeling these functional dependencies in early stages of system design. However, there are only few empirical studies that report on the extent of such dependencies in industrial software systems and how they are considered in an industrial development context. In this paper, we analyze the… Expand
Feature dependencies in automotive software systems: Extent, awareness, and refactoring
TLDR
An empirical analysis of feature dependencies in three real-world automotive systems shows that features in modern vehicles are highly interdependent and that developers are not aware of these dependencies in most cases. Expand
Automotive Software Architecture Views and Why we need a new one – Safety view
TLDR
This paper advocates the need for this view – safety view – which is compliant with the ISO/IEC 26262 and links the design of software systems (both the functional and system views) with the safety goals. Expand
Temporal properties in automotive control software
TLDR
This paper provides a framework in which requirements for these abstract properties are documented as part of the interface specifications based on a lightweight extension of event models that also includes abstract properties used in control engineering such as aliasing. Expand
Traceability Analysis of a High-Level Automotive System Architecture Document
TLDR
It is concluded that manually maintaining such high-level architectures is highly error-prone and should thus be supported by automation and appropriate tooling. Expand
Characterizing Implicit Communal Components as Technical Debt in Automotive Software Systems
TLDR
This paper provides empirical evidence that implicit communal components exist in industrial automotive systems, and proposes a refactoring approach for implicit communal Components, which makes them explicit by moving them to a dedicated platform component layer. Expand
A feature-oriented approach: from usage scenarios to automated system of systems validation in the automotive domain
TLDR
This paper proposes an integrative requirements analysis and system validation approach, whereby new information is continuously provided via automated checks and short feedback loops that allows an early and iterative refinement of system objectives and requirements and reduces uncertainty during SoS development. Expand
Software Architectures: Views and Documentation
TLDR
This chapter introduces the definitions related to software architectures, and discusses the views used during the process of architectural design and discuss their practical implications. Expand
Minimalist Qualitative Models for Model Checking Cyber-Physical Feature Coordination
TLDR
This work created and used a qualitative model for formal verification against a property in time logic and formally verified the high-level logic of a composite feature to be used in automotive systems against a formalized accident property. Expand
Requirements Engineering for Automotive Embedded Systems
  • M. Staron
  • Computer Science
  • Automotive Systems and Software Engineering
  • 2019
TLDR
In automotive software engineering, requirements can have multiple forms—starting from the short textual descriptions of functionality to fully executable model-based specifications. Expand
A Standard Driven Software Architecture for Fully Autonomous Vehicles
TLDR
A prescriptive approach to design a functional software architecture for fully autonomous vehicles starting with requirements from an automotive standard and using a NIST reference architecture for real-time, intelligent, systems and well established architectural patterns to support the design principles. Expand
...
1
2
3
4
...

References

SHOWING 1-10 OF 20 REFERENCES
Extent and characteristics of dependencies between vehicle functions in automotive software systems
TLDR
Structural models of a modern realistic automotive vehicle system are analyzed with the aim to assess the extent and characteristics of interactions between system functions and show that at least 69% of the analyzed system functions depend on each other or influence each other. Expand
Challenges in automotive software engineering
TLDR
Major new challenges now are to tame all the complexity, get a system view on top of the individual functions, and to leverage executable system models to put more comprehensive testing into early phases of a development. Expand
Multifunctional software systems: Structured modeling and specification of functional requirements
  • M. Broy
  • Computer Science
  • Sci. Comput. Program.
  • 2010
TLDR
A theory and first concepts of a methodology for the identification, structured modeling, and formalization of functional requirements of multifunctional systems, based on the Focus theory for modeling interface behavior and services is introduced. Expand
Engineering Automotive Software
TLDR
The idiosyncrasies of the domain are pinpoints, the essentials of automotive software are characterized, and the challenges of the automotive software engineering are discussed. Expand
Feature-Oriented Domain Analysis (FODA) Feasibility Study
TLDR
This report will establish methods for performing a domain analysis and describe the products of the domain analysis process to illustrate the application of domain analysis to a representative class of software systems. Expand
Generating Tests for Feature Interaction
Modern vehicles integrate an increasing number of features. The interaction between these features is often error prone and requires extensive testing in order to ensure correctness and reliability.Expand
The SCR Method for Formally Specifying, Verifying, and Validating Requirements: Tool Support
TLDR
The SCR (Software Cost Reduction) requirements method, which is based on a tabular notation, is a formal method for specifying the requirements of real-time, embedded systems introduced more than a decade ago by the A-7 project. Expand
Using the SCR* toolset to specify software requirements
  • C. Heitmeyer
  • Computer Science
  • Proceedings. 2nd IEEE Workshop on Industrial Strength Formal Specification Techniques
  • 1998
TLDR
To provide powerful, robust tool support customized for theSCR method, the SCR* toolset is developed and a formal model which defines the semantics of SCR requirements specifications is developed. Expand
Feature Interactions in Telecommunications and Software Systems VI, May 17-19, 2000, Glasgow, Scotland, UK
TLDR
This sixth workshop maintains the contest started at the last workshop in Sweden, but the winner is kept secret and only announced during the workshop, which is entering an exciting new phase for feature interaction. Expand
Software Engineering for Automotive Systems: A Roadmap
TLDR
This paper presents research challenges in the domain of automotive software engineering and outlines the priorities for further research in this area. Expand
...
1
2
...