English
Using model-based design to test auto embedded software
Jim Tung, The MathWorks
(09/24/2007 7:54 AM EDT) -- EE Times
Embedded software and electronics represent an increasing percentage of the engineering content of an automobile. By 2010, electronics are expected to comprise 40 percent of automotive material costs, up from 10 percent in 1970 [1]. Embedded software and electronics are used across the car's functional areas, replacing or simplifying mechanical and hydraulic systems in core functions, such as steering and braking, and implementing advanced features, such as active safety systems and driver information systems, that add significant customer value in terms of convenience, comfort, and safety.
However, the rapid growth in complexity of embedded software and electronics coupled with the difficulty of testing and verifying these systems has been associated with a rise in quality issues and recalls. According to IBM Corporation, automakers spend two to three billion dollars a year to fix software problems and 32 percent of auto warranty claims in the United States are for software- or electronics-related issues.
Model-Based Design has become the preferred approach for developing automotive embedded software because it improves the specification, design, and implementation phases. Now, new tools and capabilities are available for Model-Based Design that help address test and verification challenges, improving embedded software quality and shortening the test and verification cycle.
(09/24/2007 7:54 AM EDT) -- EE Times
Embedded software and electronics represent an increasing percentage of the engineering content of an automobile. By 2010, electronics are expected to comprise 40 percent of automotive material costs, up from 10 percent in 1970 [1]. Embedded software and electronics are used across the car's functional areas, replacing or simplifying mechanical and hydraulic systems in core functions, such as steering and braking, and implementing advanced features, such as active safety systems and driver information systems, that add significant customer value in terms of convenience, comfort, and safety.
However, the rapid growth in complexity of embedded software and electronics coupled with the difficulty of testing and verifying these systems has been associated with a rise in quality issues and recalls. According to IBM Corporation, automakers spend two to three billion dollars a year to fix software problems and 32 percent of auto warranty claims in the United States are for software- or electronics-related issues.
Model-Based Design has become the preferred approach for developing automotive embedded software because it improves the specification, design, and implementation phases. Now, new tools and capabilities are available for Model-Based Design that help address test and verification challenges, improving embedded software quality and shortening the test and verification cycle.
|
E-mail This Article | 
|
|
Printer-Friendly Page |
Related Articles
- Processor-In-Loop Simulation: Embedded Software Verification & Validation In Model Based Development
- Metric Driven Validation, Verification and Test of Embedded Software
- Model-based approach allows design for yield
- Optimizing embedded software for real-time multimedia processing
- Will Generative AI Help or Harm Embedded Software Developers?
New Articles
- Why RISC-V is a viable option for safety-critical applications
- Dimensioning in 3D space: Object Volumetric Measurement by Leveraging Depth Camera-based Reconstruction on NVIDIA Edge devices
- What is JESD204B? Quick summary of the standard
- Post-Quantum Cryptography - Securing Semiconductors in a Post-Quantum World
- Analysis and Summary on Clock Generator Circuits and PLL Design
Most Popular
- System Verilog Assertions Simplified
- Enhancing VLSI Design Efficiency: Tackling Congestion and Shorts with Practical Approaches and PnR Tool (ICC2)
- System Verilog Macro: A Powerful Feature for Design Verification Projects
- Method for Booting ARM Based Multi-Core SoCs
- An Outline of the Semiconductor Chip Design Flow