Quality assurance of a MicroStrategy project is a multi-faceted topic. Typically, it breaks down into the following 4 areas:
accuracy - did the report meet the requirement and subsequent specification ?;
performance - did the overall execution fall within the service level set by the business analyst;
efficiency - is the report SQL utilizing an optimum approach to arriving at the result - are indicies being used? are temporary table optimization options being leveraged?;
presentation - is the user interface manageable? do the prompts make since? do they follow a consistent order from report to report? is it possible to navigate to all of the required drills from the appropriate attributes?
One technical approach I've found useful is to generate a static (non-prompted) version of representative reports; generate the SQL for each of the reports and save it in either a spreadsheet or flat file of some kind. This is helpful when later determining the probable impact of an architectural change, and can provide some indication of how much quality assurance testing may be required to cover areas which may have been impacted by the architectural change.
Peace,
Don "Windy Won" McMunn
dmcmunn@ipcdesigns.com
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.