Thinking a bit outside the box here, but what about using something like SurveyMonkey? They have a free plan if you just want simple.

I believe this situation is quite familiar to many (most?) of us :) The only good process I know is exactly what you mentioned, do it proactively when everything is clear in mind. Doing the documentation later is always somewhat gathering the pieces. About the tools, I think RedGate makes good products, but also this: http://www.dbdesc.com/[^] could be worth to look at. There are few areas these tools don't cover so if you use a tool to generate the documentation, I would still try to manually include for example: - E/R diagrams per subsystem (especially in larger dtabases) - if a table/view has enumerated values etc. in a column, what do they mean - same for procedures - privilege/role maps and so on Hope this helps, Mika The need to optimize rises from a bad design.My articles[^]

I prefer use cases that are follwed through by acting them out (involve client for this). Any fuzzy points can be sorted out with the client at an early stage. The problem I have experienced with SRSpecs is that you often assume something means A and the client assumes that the same text means B and nobody questions it until the software is delivered. Often the client will sign off the spec (my clients at least) without reading it and then act surprised when 'it don't work' At least if you go through each scenario with the client most of these problems are picked up early. Another advantage of running through the use cases is that you can get your software team involved in the process, so they can understand how the system is going to work and can add their input. It does take a lot of organisation and it also requires some effort from the client. It also means that you have to ensure that someone with business knowledge is available from the clients. This is only a quick list of what I can think off the top of my head. Paresh Solanki "Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep." Scott Adams (Dilbert cartoonist)