Search Results

In traditional automotive electronic design, software update has been a component oriented, manual process rather than a systematic designed in capability suitable for automation. In recent days as software content in vehicles grow, the need to update software in vehicles more frequently is becoming a necessity. Moreover, additional attributes for software updates, for example timely delivery of security related update for vehicles, desire to add features using software update, control cost of software updates, etc., requires a system engineered design rather than a component oriented approach. As the automobile domain utilizes various means of mobility (Combustion Engine, Hybrid, Battery, etc.) and various functional domains (Infotainment, Safety, Mobility, Telematics, ADAS (Advance Driving Assist service), Autonomous, etc.), to control the overall cost of future software update for such a diverse environment, it is beneficial to introduce automation in the software update process.

Consumer expectations for automated vehicle operations such as automatic locking, remote ignition control, navigation, and entertainment are primary drivers for the increasing complexity of embedded automotive electronics modules. The prevalent practice for procuring these modules is to develop a written behavioral specification that is then used by an outside supplier to build and test the module. Validation test plans are written separately based on an understanding of the requirements. The challenges posed by the current practice include the inability to completely specify the expected behavior in a timely manner, the need to balance the design between low cost and new features demanded by the customer, and ensuring that the product exactly implements the specified behavior. Moreover, vehicle manufacturers desire the ability to explore sensitivity of specifications by identifying constraints on the system and assessing the product for ease of implementation.