Ron, you definitely should be telling everyone in the company who will listen to you that specification and planning is actually far more important for Software than for Plumbing and/or Electrical ... and that Software, in fact, is not one whit more “malleable.”
If you describe the thing that you are building in terms of it being nothing less than a self-directing machine, composed of millions of mutually-interdependent and interacting parts, and that nothing ever happens except as the consequence of a binary yes/no decision with no possibility of direct human influence ... then you will accomplish the mental gear-shifting that, it seems, someone at your company at one time tried to do when they specified the same formal planning and design process for Software as for Plumbing and Electrical.
It’s easy to see the need for discipline in these other trades, because you can see them with your eyes. You’d instantly reject the “stand-up comedy routine” if you saw that even a stationary thing, like an electrical layout or a plumbing grid, were being constructed, because you’d see and intuit the folly of such an undisciplined approach. (Not to mention it would not be legal, and you would lose your license to do the work ... a concept of which the Software industry still has no parallels, yet.) Not a soul goes to a workplace without a sheaf of blueprints, all bearing that vital license-stamp, and no one does anything but follow it. The projects happen, routinely and safely, because of that.
Ron, someone at your company was definitely on to something very important when s/he created that original idea of formally planning Software as with everything else. That way of thinking should be frankly encouraged. Computer software is very much like Laws and Sausages: people encounter it every day without really understanding how it gets made and what strictures apply to it. And so, they treat it “differently,” and more casually. Fact is, since software is a machine, and one that runs autonomously, it requires more planning and more discipline than almost anything else . . . yet, rarely receives it. “Aye, there’s the rub.”
Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
Want more info? How to link or
or How to display code and escape characters
are good places to start.