 |
Don't wait until the rest of the assembly is done
|
|
Don't wait until after the first debug run.
|
|
Try to avoid using it as the last resort (i.e. 'we tried everything
else, so now we figured we'd have a flow done on it!')
|
|
Don't restrict your applications to your toughest tool. There may be
something inherently flawed with your design that even flow analysis can't
help you with while some of you bread and butter tools nay be improved
dramatically
|
|
don't wait until they're cutting steel
|
|
avoid using flow analysis as an 'absolute' tool, accuracy of models
material data and other factors make this a risky approach. Use it to
compare various options and the relative differences.
|
|
Don't put the analysis into a black box and expect a magical one
sentence solution to come out. Share with the person performing the analysis
every piece of information available about a particular project. The more
background data, the better the results.
|
