Search Results

Requirements development and analysis for automotive electronics products have been found to be tremendously challenging to both OEMs and suppliers. Besides ambiguity, incompleteness, conflicts and other pitfalls commonly seen in requirement specifications, in some cases, a requirements document for a new electronics product may even not exist and may need to be developed from scratch. Analysis reveals that generic model-based approaches and toolsets presently available lack support for requirements development while facilitating all other development activities across the entire product development cycle. In this work, we describe a model-based development methodology centering on requirements development, engineering, and management while supporting other development activities including requirements analysis and clarification, rapid prototyping, simulation, verification and validation, automatic code generation, and SIL/HIL testing.

The ever-increasing complexity and cost of automotive electrical systems are driving the change in automotive electronics development from traditional approaches to model-based methodology and processes. In this paper, we present an effective model-based development process particularly suitable for dealing with changes to existing designs, or “feature change” types of projects, in which the design and implementation procedures are often imposed by constraints due to the mandatory adoptions of legacy code and carryover designs. The new process herein involves creating “executable” requirements and functional models, generating test scenarios and/or cases, using the test cases for clarifying customer requirement specifications, using the clarified test cases for testing at various levels, and verifying the hardware-in-the-loop test results captured from the proprietary automatic test equipment.