Why QuantiPhi?

Article Posted: 12-28-2006

If you are using the Mathworks tools (Simulink/Stateflow) to model features that will eventually be used to automatically generate code using Embedded Coder, then you should seriously consider using QuantiPhi for your lower layer software.

Your target dependent lower layer software could easily be completed within a day or two by a single engineer. Engineering resource is freed up to work on getting the functionality the customer wants.

Prototypes can be demonstrated to customers at the beginning of a project or to wow potential customers by responding to quotes with working prototype systems!

Consider the alternative more traditional approach:

• Specify the lower layer software components.
• Estimate effort for: requirements, design, code, peer review, test, integrate and retest, iteratively fix.
• Allocate engineering resource.
• Schedule the tasks.
• Perform the development.

Depending on the project complexity, there may be up to 3 man-years of work effort (management, development and test) with costs in the $100Ks.

Furthermore, hardware and software cannot be integrated and tested until the drivers have been developed and tested. It may be several months before a prototype could be demonstrated to a customer.

To further illustrate the savings associated with QuantiPhi, take a look at the figures shown below. These bar graphs show defect, effort and cost data resulting from the development of device drivers for a vehicle control system using hand coded software development. The system was not particularly complex and this data does not include scheduler or CAN development. This effort and cost would be almost entirely eliminated through the use of QuantiPhi.