ROM: Rough Estimate of Magnitude

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!

ROM = Rough Order Of Magnitude

Hi Gregg,
I don't know of a "ROM Standard". Maybe your client only wants to get some rough idea of the costs for his project. Something like "between 5 and 6k USD".
Or he might want to get a really detailed version like in this ROM document.

A definiton:
"Estimated cost based on approximate cost models or expert analysis. It is usually based on top level requirements or specifications, and an overall prediction of work to be done to satisfy the requirements. The ROM is usually used for financial planning purposes only." [Source]

With respect to programming, you might also like to notice the use of ROM in Microsoft Terminology: "An estimate done without detailed costing, or based on initial or incomplete data. Typical categories are 1 - 3 days, 3 - 10 days, or greater than 10 days. A rough order of magnitude estimate establishes an approximate cost for a scenario or quality of service requirement." [Source]

Basically you should search the web for "Rough Order of Magnitude". This will give you better results than "Rough Estimate of Magnitude"

Hope that helps.

Kind regards,
Stefan Gentz

TRACOM OHG – Global Solutions for Global Documents