[webproducers] Re: tech spec help!

Good points. To help with #3, I generally write my specs first (in an=
 outline format, to make them easy to read and more intuitive), then follow=
 up with info-designs. Inevitably, something comes up when I'm mapping it=
 out that I hadn't addressed initially (oh yeah, what happens if the user=
 doesn't click that box before they hit submit? An error message? A default =
selection?).



=46or a complex project.=20

>yes, an internet search may help.
>
>however, there's no standard way of writing one. some orgs have formalized
>templates, which you are expected to use while others you roll your own.
>
>whatever you do, make sure it:
>
>1) contains illustrations where applicable (for example for sample output)
>
>2) is concise (wordiness tends to get ignored as well as confuses)
>
>3) is complete. make sure you cover all possible angles. for ex: if it's a
>web app, make sure you cover the process of entering data, expected
>output, mention business issues/rules, and address error conditions, etc.
>
>4) get it tech checked and signed-off by someone who knows their shit
>better than you.
>
>this not only helps minimize potential issues (and covers your ass) but
>the extra set of eyes will help you deliver a superior document.
>
>


__________________________________________________________________________
Check out www.webproducers.org to easily access list commands like subscribe, 
unsubscribe, digest mode, vacation, and to read the list archive.

Questions and comments are welcome just e-mail me,
webproducers-admins@xxxxxxxxxxxxx   -Morry

Other related posts: