Are there any criteria available for finding out the health of the product ?
I am testing a Software having 6-7 modules . Client wants to get the release certified from us before rolling it out . We are yet to find any model which helps in certifying the health of the product .
An addition to what Jake wrote above, and in case you don't have an answer to Joe's question about what he means by certified...
One thing I like to do with customers that don't specify their Acceptance Tests Scenarios is to ask them for their top 10 - 20 (it can be even 50, depending on your application) End-to-End Business Processes they run as part of their day-to-day operation, and their most important 3 Processes that they don't run every day but are very important (e.g. end of month reports to higher management).
I take this information and build a set of Acceptance Tests that I run in-house and I then I build a report and send it to the customer.
Better yet, ask them to have a domain expert use a beta version of the software. That is, of course, unless this isn't possible without upgrading the whole company.
In that case, is there a way you can give remote access to one of their people to review it? Of course, I'm assuming that you don't know exactly what the client wants. In many cases, though, we don't know exactly what the client wants. We have an idea of how the client would use the software, generally, but what do they actually do in it and why?
Having an expert from their org look over it is always a nice option when it's available.
9 out of 10 people I prove wrong agree that I'm right. The other person is my wife.