Was Your Last Software Specification Really Appreciated?

If you're still trying to write system specifications in English then you're in toruble. For the same reason that engineers and architects use graphical tools to specify their products so too must program speciifers (the term program engineer may be used, but it does imply that we're using a disciplined approach).A system needs to be broken into small pieces in a structured way and we need to show various views of the system and how they fit together. Typically we may show a process view, a data view, perhaps a time-line view.Each piece, or module, can then be specified, using the following rules:1.
Strcuture the specification - use a numbering system. Number each separate business rule. User acceptance tetss can then be devised and cross-referenced accordingly.2. Cross-reference - your specificaiton must cross-reference to the basic processes of your process model.3.
Your headings should include Overview, Input Files, Ouptut Files, Files Referenced, Processing Rules.4. Write in the present tense, not the fuutre. It's easier to write, easier to read, and it makes more sense as it will be read and used more when the proudct exists.5. Write from the viewpoint of the processor, not the user.6.

Be crystal clear and unambiguous.
Use the active voice (subject, verb, object, sequence), not passive voice (object, verb or verb phrase, subject, sequence).7.

Test the specification - beofre it gets to the developer!