I am looking for MRD/ERD (Marketing/engg. Research documents) kind of documents, which describe the user requirements with out too much of technical contents. Itís more of feature requirement with description and usage intended.
What would be too much "technical contents"? Without detail, it is most difficult to be helpful.
Use Google to find companies that make and sell this type of product and look at the features that they have - this would be a starting point.
I have not failed. I've just found 10,000 ways that won't work" --Thomas Edison
From what I understand, you are trying to look more at the business angle of things rather than the tech spec, as it were.
In such cases, I've found it most useful to have a meeting or workshop with the Product Manager or Business Analyst and find out how the requirement ties in with business expectations.
The exercise is basically to map out how a business need translates over time into a technical requirement.
I'm not sure whether we might have missed what Pooja is asking for.
Pooja, do you want a real EXAMPLE of such a document?