My current customer has requested a "ROM" or "Rough Estimate of Magnitude" document for a software project. I have done some searching on Google and found little that addresses this topic.

What kind of information should a good ROM document contain? Are there any published standards, templates or outlines for a ROM?

Thanks for any help you may be able to provide!

How does everyone handle what I call the "Rodney Dangerfield" syndrome (the "I don't get no respect") issues of being a tech writer?

Has anyone used Requisite Pro to set up a software documentation system and templates? I have a new position with a government contractor and we are trying ReqPro out on one set of software documents to see how it works out. I have used it for about two weeks and am finally getting less dangerous with it. ;-) The learning curve is pretty high at first, as they use their own language in their templates.

I'm also brand new to the software development world, having been an aviation technical writer for the airlines for the last 3 years. Any advice is appreciated.

Gregg