Buggy Software
Buggy Software
(OP)
Is it just me or is the quality of engineering software going downhill? We received an update to a popular(?) FEA program last week. With hopes high I installed the update and promptly imported a solid model that came from a CAD package.
I started to sketch something on the part but something looked out of whack. I measured an edge on the part and it was way bigger than it should be. I double checked my work and became convinced it was the software, so I called technical support. Sure enough, they have a bug in the import routine. It seems that an inch in the solid model comes in as a meter in the FEA package. (Is anyone thinking Mars probe?)
Here's my question about overcoming obstacles in the workplace. Is there nothing we engineers can do to stop this crap or at least slow it down?? I don't know about y'all be we run into crappy bugs like this all of the time. All we ever get is how complicated these programs are and you've got to expect some mistakes. I would keep prattling on but I've got to go.
I started to sketch something on the part but something looked out of whack. I measured an edge on the part and it was way bigger than it should be. I double checked my work and became convinced it was the software, so I called technical support. Sure enough, they have a bug in the import routine. It seems that an inch in the solid model comes in as a meter in the FEA package. (Is anyone thinking Mars probe?)
Here's my question about overcoming obstacles in the workplace. Is there nothing we engineers can do to stop this crap or at least slow it down?? I don't know about y'all be we run into crappy bugs like this all of the time. All we ever get is how complicated these programs are and you've got to expect some mistakes. I would keep prattling on but I've got to go.





RE: Buggy Software
Either high management gave the customer impossible deadlines that the software designers couldn't keep and something missed checking.
Or maybe the software designer didn't have all the information to begin with...
Another common mistake is that in the middle of software development, high management changes one little thing that wrecks everything done to that point.
Or it could be poor software writing and debugging skills.
I would bet on the first three as most likely to occur ;)
RE: Buggy Software
corus
RE: Buggy Software
RE: Buggy Software
But the caring, knowledge, testing, and more testing that cars are submited to makes a difference.
Software on the other hand is made and tested only once or twice... And not all conditions are verified, or if verified, they are by people that don't know the purpose of the software.
Software writers can build programs for chemical or other engineering branch, but they don't have the knowledge to tell if all the possibilities came as expected.
Another thing might be the fact that, a car is intended to last, ideally, through a lifetime. Software isn't. :(
RE: Buggy Software
There is no mechanism in software that behaves in a nondeterministic fashion.
There is no reason on God's Green Earth why computers should have, or need, a Reset button.
Well, except for Billy, who always sells stuff before it exists, then hires people to produce it, rushes it out the door, and induces every computer user in the world to work for him, and pay him for the privilege, for at least a few minutes a day, cleaning up the mess he made.
Nineteenth Century Robber Barons were putzes.
Mike Halloran
NOT speaking for
DeAngelo Marine Exhaust Inc.
Ft. Lauderdale, FL, USA
RE: Buggy Software
But the guy had difficulty modelling the load interface. When the deflections were magnified in the graphics, the interface appeared to be a point load instead of a line or narrow rectangle. What a waste.
FEA was prescribed by QC types in the QS9000 system.
RE: Buggy Software
Far from being a waste the analysis confirmed the hand calculation approach and also assured engineers that there were no other secondary effects to be worried about. FEA gives confidence in the results and design, engineers using F/A doesn't inspire confidence at all.
corus
RE: Buggy Software
Giving a powerful tool to someone who doesn't understand the tool or the problem the tool is intended to solve will produce unfortunate consequences. Lawyers at the defense table would call them unforeseen consequences, but engineers know better.
Introduce a toddler to a running chainsaw, and you should expect blood, not stump sculpture.
Mike Halloran
NOT speaking for
DeAngelo Marine Exhaust Inc.
Ft. Lauderdale, FL, USA