2010/3/12 Björn Helgason <[email protected]>: > When you decide to create a system you are supposed to write specs and > then create documentation and then write the code or is it the other > way around?
Yes, of course! > If you try to do it the other way around and write specs and > documentation first it is very often worse outcome. > > So what do we do? In my opinion: Initial specs should be task oriented, and should be regarded as incomplete drafts documenting critical requirements. Working code needs to pass a certain level of acceptance testing before it can be regarded as proper. When writing documentation, you will sometimes find cases which would be easier to document if the code were changed. In those cases the proper approach to writing documentation involves changing the code so that the documentation can be written simply. -- Raul ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
