Theme Issue on Automotive Software
Submission Deadline: 1 October 2016
Publication: May/June 2017
Software is today the number one decisive competitive factor in the automotive industry. Innovations such as driver assistance systems or energy efficient drives require complex solutions with complex software functionality. Big industry players such as BMW, Bosch, Daimler, Ford, GM, Hyundai, Magna, and ZF are today considered the market leaders in embedded software technologies as well as drivers in global software engineering methods and collaboration tools. Due to the fast growth of automotive software with a double-digit CAGR (compound average growth rate) in market penetration, many new players such as Apple, Google, and Huawei are getting into this market.
Developing automotive software is challenging for several reasons. Namely because it connects embedded software with big IT systems, it is developed in a global context in distributed teams, and it has one of the shortest cycle times of all industries. A modern car has 50-120 embedded microcontrollers on board and is connected over five external interfaces to a variety of cloud and infotainment technologies. Onboard software is in the hundred MLOC size, and still exponentially growing. Not only the growing complexity has to be managed, but safe behavior has to be ensured at all times. The global competition and thus cost pressure enforces continuous efficiency improvement and cost optimization. Therefore, software technology and the underlying engineering processes have to be constantly improved.
Automotive software makes the difference. Software engineering technology advances are today heavily driven by automotive OEMs and suppliers. Examples include systems modeling, testing and simulation with models in the loop, artificial intelligence in multisensor fusion and picture recognition for ADAS (advanced driver assistance systems), distributed end-to-end security for secure global OTA (over the air) software updates directly into the cars firmware, and the connection of global IT systems and cloud technologies for online diagnosis or emergency calls processing with millions of cars and their embedded devices.
We invite articles covering any aspect of automotive software. Survey articles and focused tutorials are especially welcome. Topics include but are not limited to:
- Contribution of automotive software engineering advances (e.g., in model-based development and simulation with models in the loop) to embedded systems development;
- Advanced automotive software architectures (partitioned, multicore) for managing mixed criticality, safety, and security;
- Component-based software reference architectures such as AUTOSAR and their benefits for other industries;
- Automotive software platforms and ecosystems;
- End-user customization/programming of automotive software applications;
- Cloud technologies for vehicle 2x communication;
- Testing of complex state space systems;
- Quality requirements engineering for safety, security, usability, and performance;
- Automotive software product line and variant management, including dynamic variability techniques for adaptive behavior during vehicle operation;
- Artificial intelligence in multisensor fusion and picture recognition for ADAS (advanced driver assistance systems);
- Software engineering challenges in the transition to autonomous driving;
- Distributed end-to-end security for secure global OTA (over the air) software updates directly into the cars firmware;
- Connection of global IT systems and cloud technologies for online diagnosis or emergency calls processing with millions of cars and their embedded devices;
- Green IT for embedded software and cloud systems;
- Automotive software engineering methodologies taking into account the challenges of distributed development among customers and suppliers;
- Automotive software engineering standards;
- Accelerated lean deployment, such as DevOps for automotive software;
- Integrated tool support and product life-cycle management (PLM) solutions;
- Education in automotive software engineering.
For more information about the focus, contact the guest editors:
Manuscripts must not exceed 4,700 words including figures and tables, which count for 250 words each. Submissions over these limits may be rejected without refereeing. Articles we deem within the theme and scope will be peer reviewed and subject to editing for magazine style, clarity, organization, and space. We reserve the right to edit the title of all submissions. Submissions should include the name of the theme or special issue you are submitting for.
Articles should be novel, have a practical orientation, and be written in a style accessible to practitioners. Overly complex, purely research-oriented, or theoretical treatments are not appropriate. IEEE Software does not republish material published previously in other venues, including other periodicals and formal conference/workshop proceedings, whether previous publication was in print or in electronic form.
To submit an article: https://mc.manuscriptcentral.com/sw-cs
For submission details: email@example.com
For general author guidelines: https://www.computer.org/web/peer-review/magazines