I need to write specifications for enhancement/change requests to a web-
based medical application on a regular basis. The app is developed by a
company we are partners with and I have a good working relationship with
their development team. The problem is that they are not strong on
documentation, nor on usability fine points, and need requirements spelled
out in great detail in order to deliver accurate functionality that
maintains my standards of usability. It's also important that different
stakeholders on my end get to review and sign off on things to make sure
all operational compliance standards are met (no great surprise!)

I've been creating my own documentation but am looking for some more ideas
on formats and layouts from this distinguished community of professionals.
My requirements are that the document be able to accommodate line item
features, sign-offs for my QA team and their Dev team (per item), global
sign-offs for loftier stakeholders, deliverable dates (per item and global)
and some form of naming/numbering scheme for request and version tracking.
I'm pretty open to other data that I may not be including which perhaps I
should.

Can any of you point me in the direction of examples online or templates
that you've worked with? I know that everyone has their own formats, which
can change with project type, but I just need to see some examples to spur
my creativity.

Please send replies directly to me and I will post a summary. Thanks in 
advance to all compulsive documentation heads who reply!

David Newfeld
Technical Trainer
[log in to unmask]

    --------------------------------------------------------------
    Tip of the Day: Use the archives to research common questions
     CHI-WEB: www.sigchi.org/web POSTINGS: mailto:[log in to unmask]
              MODERATORS: mailto:[log in to unmask]
       SUBSCRIPTION CHANGES & FAQ:  www.sigchi.org/web/faq.html
    --------------------------------------------------------------