The engineers dream machine

The engineers dream machine

[SAHARBAUGH]

Gary Funck writes, in part:
Tell me it wouldn't be better
   to implement a traceability/CASE tool that keeps the unit hierachy
   and dependency numbering scheme in parallel with the program components.
---
Let me tell you about my dream machine. You look at
software as written.  You punch a button and the comments
disappear.  You punch a different button and the code 
disappears.  You punch a different button and the code
is pretty printed in my favorite format. You punch another
button and the long variables get replaced by short ones,
maybe even icons. e.g., a small picture of an antenna
replaces the identifier ANTENNA.  You get the idea.
  Many years ago a Tri-Ada vendor showed an editor that
"allowed you to format anyway you wanted to". I said that
I wanted to replace "package" with a smiley face.  He
looked ta me as if I was from another planet.
  Also Gary, I am one of those bad systems enginers that
specify that system level names be used in the code.  About
12 years ago I was assigned to the systems engineering
group of a large communications project and was responsible for
the CPDP (Computer Program Development Plan) among other things.
I assured the communications systems engineers that if they
attended a code walkthru in 2 or 3 years they would probably
be able to understand the code because they would see
identifiers that they had been using for 5 years.  We had a
systems level dictionary and that was GIVEN to the software
engineers.  I understand your complaint but please realize
that it is VERY IMPORTANT that the system engineer can read
the software.  It is very importatnt that the system enginer
can spot something like Link_Power_Margin := Transponder_Power_Rating
+Link_Power_Setting (where the plus should have been a minus).
Suppose he had read L001:=T004-L002; and had to look in a dictionary.
sam harbaugh saharbaugh@ROO.FIT.EDU        
-----------
Florida Bumper Sticker: "If its tourist season can we shoot them?"
---