Search Results

Today's vehicles are typically outfitted with passenger convenience features that require Human Machine Interfaces (HMIs). HMIs can be relatively simple - such as a remote key fob - or more sophisticated - such as a radio face plate. Traditional development of HMIs involves two typically independent processes - (1) Physical Component Design and (2) Functional Logic Design. The physical component design is developed by a team that usually includes both graphics and ergonomics designers to ensure that the HMI is intuitive and fits well with the interior styling of the vehicle. The functional logic design follows a more typical software development process. This process is based on functional requirements commonly written in terms of user requests and system responses as represented by the HMI. As the complexity of the system increases, it is essential for the intuitiveness and ease of use of the HMI to advance as well.

Model-Based Design is no longer limited to R&D and pilot programs; it is frequently used for production programs at automotive companies around the world. The demands of production programs drive an even greater need for tools and practices that enable automation and rigor in the area of verification, validation, and test. Without these tools and practices, achieving the quality demanded by the automotive market is not possible. This paper presents best practices in verification, validation, and test that are applicable to any program, but are critical when applying Model-Based Design in production programs.