[Kevin Sevcik]

I'm a MechE, so I'll throw in my 2 cents as well. As mentioned above, software is an enabling tool that lets Mechs do more with less. So it's important in that regard. However, mechanical engineering isn't completely computer modelling of parts. That's really one of the last steps in the process. A lot is about creative thinking and solving problems. A lot of new tech is going to depend on miniturization, and that's highly dependent on mechanical engineering and creativity. Look into microelectromechanical systems (MEMS) and you'll see an awful lot of exciting stuff there. Things like microscopic motors and pumps and all sorts of stuff. When you get that small, the equations lots of things change and that takes a sharp MechE to rework things before software can do anything with it.

Software packages have their limitations. FEA packages aren't 100% accurate and can be blatantly wrong if you're not careful. You need enough engineering knowledge to make sure your result is in the ballpark.

Both of your examples are controls systems, which do depend on software to process feedback and control the system. No amount of software engineering will help you understand the dynamics of the system and what it actually has to do to control the system, however. Tweaking the constants and functions that generate the control signals is pure mechanical. The software is there simply to translate the MechE's work into reality.

In the end, I don't think you can say any technical discipline is better or more important than another in an absolute sense. They're all highly interrelated and interdependent and you can't advance in one without advances in others.