Try to imagine next situation, and think further on that part of your implementation test.

Suppose your company does write firmware for an ABS-carsystem. How do you test your firmware without a car, cause your company is not building cars!

If your company is able to get a test-vehicle to do all kind of test on it. How do you intent to build a test without using to many new cars (due to bug-crash).

Is there a possibility to use a system to test your firmware non-destructivly? If not, how do you intend to test for bugs.

Everymen, and I mean EVERY man and woman, do make mistakes. If you can capture the fault before final release, you may be happy.


These items should be included in your technical proposal.

BTW there is no software that scans your firmware for BUGS. You might want to use a simulator, that solves your hardware isue!

Best Regards,

Bert