|
Re: Specifications
all the real work in engineering happens when you write the requirements spec (what the system shall do), the design spec (how the system is going to do each 'what'), and the test spec (how you are going to test the system to prove it does all the 'whats').
If the specs are not written, or only half written, or you use parts (like interface specs) that are not up to date, or if you have no spec at all, then you are writing code by the seat of your pants.
Engineering has gone through this before - there's always some group of hotshots who think they can figure out what a systems going to do, how its going to do it, come up with the algorythms and data structures on the fly, and make up or fill in the interfaces as you go along.
Thats not engineering, thats hacking.
If your specs are worthless its because the person who wrote them doesnt know what they are doing.
|