Search Results

Software products in the automotive industry are by nature widely distributed and costly to update (recall), so high reliability is clearly of utmost importance. Just as clearly, the increasing reliance on remote access to such systems, for diagnostic and other purposes, has made security an essential requirement, and traditional techniques for software development are proving to be inadequate in dealing with these issues. Correctness by Construction is a software design and development methodology that builds reliability and security into the system from the start. It can be used to demonstrate, with mathematical rigor, a program's correctness properties while reducing the time spent during testing and debugging. This paper will discuss the use of Correctness by Construction, and its accompanying SPARK language technology, to improve automotive systems' security and reliability. (The approach can also account for safely issues, although that is not the focus of this paper.)

The first commercially available plug-in hybrid electric vehicle (PHEV), the General Motors (GM) Volt, was introduced into the market in mid-December 2010. The Volt uses a series-split powertrain architecture, which provides benefits over the series architecture that typically has been considered for use in electric-range extended vehicles (EREVs). A specialized EREV powertrain, called the Voltec, drives the Volt through its entire range of speed and acceleration with battery power alone and within the limit of battery energy, thereby displacing more fuel with electricity than a PHEV, which characteristically blends electric and engine power together during driving. This paper assesses the benefits and drawbacks of these two different plug-in hybrid electric architectures (series versus series-split) by comparing component sizes, system efficiency, and fuel consumption over urban and highway drive cycles.