Rapid Prototyping

The advantages of rapid prototyping are hard to ignore.
With the change of ECU development trends and faster time to market cycles, rapid prototyping is necessary.
Expensive supplier coding, experts and hardware can be minimized based on the introduction of software-centric rapid prototyping. It offers quick changes, brings the ability for more areas of expertise to participate in idea generation and allows for creative experimentation.
It is important to understand the differences between the methodologies and select one that will help with a competitive advantage. Even with software-centric rapid prototyping, the tool choice may not be obvious. The defi nition of “hooks” may not be referred to in the same manner by all vendors. To help decipher some of the choices, consider the future needs:
 Can you defi ne all the necessary points of access needed for rapid prototyping?
 If you discover a new rapid prototyping need, will foundational work or steps be required to access it?
 Can the same tool be used with different ECUs or different microcontrollers?
 Do you need to purchase a compiler for use with that microcontroller?  Can the tool you are evaluating accommodate these unknowns?  Does your organization have the right expertise within its personnel?
 Does your program have the built-in time buffers for code iterations?
With the complexity of control systems increasing exponentially, anticipating all future development needs or situational variables is impossible. The investment in rapid prototyping tools must be judged throughout development, not only the product’s cost, but on its fl exibility to avoid delays and roadblocks. Additionally software-centric rapid prototyping must be evaluated on issues due to missed
“hooks” that inevitably result in expensive