RE: Top ten myths of technical communication
Software Engineering methodology usually says that things go in this order:
1. Discovering user requirements
2. Developing specs
3. Writing code
I consider anyone developing software and documenting it who experience the process in the order shown above are very lucky.
My experience has shown that software is usually done in a more hapaazard manner:
1. Develop the barest of specifications in the vaguest terms.
2. Write the code.
3. Test the program/document the program.
4. Add features.
5. Fix bugs.
6. Repeat steps 3 through 5 until Marketing demands that it be released.
7. Discover user requriements through complaints to Customer Support group.
Engineering Services, Senior Technical Writer
scott_turner -at- csicontrols -dot- com
Previous by Author:
Re: Number of steps per procedure
Next by Author: RE: accuracy in packaging
Previous by Thread: RE: Top ten myths of technical communication
Next by Thread: Re: Top ten myths of technical communication
Search our Technical Writing Archives & Magazine