Report Development Checklist

Hi Guys

I’m working on creating a report development checklist for one of my staff members. The purpose of this checklist is to help point him in the right direction for things to check on a report before sending it of for user acceptance testing. Things that need checking are spelling mistakes, columns are aligned appropriately, reality checking on the data back to the server and etc.

Does anyone have a document like this or can point me in the direction of a good resource?


pidgeon001 :australia: (BOB member since 2012-03-06)

Here is what I have created so far to give you guys an idea on what I’m after. Mine has some workplace specific requirements
Crystal Reports Design Usability Checklist.zip (13.0 KB)


pidgeon001 :australia: (BOB member since 2012-03-06)

As far as the formatting. It totally up to our customers (some want Arial, some want Times New Roman, some just want pretty).

We try to use commands in most cases (we have seen a big performance boost on larger reports in most cases).

When we were converting Webi reports over from a older version of BI to a newer version. We had to create a ‘cover page’ that had the title, run date/time, all the parameter values.

One of the big thing for us it verifying the data (sometimes very difficult since we may not have access to the application that our clients do).

Another thing which be very helpful. Commenting any formulas that are at the least bit complex or just doing something out of the ordinary.

Also our supervisor wants us to put our name in the Author in the Summary Info. She also wants us to put in the report title, but that overrides what you see on the tab when open the report (can be confusing).


kevlray :us: (BOB member since 2010-06-23)

In most of the cases you need to set the default values to set your customer requirements… like my customer informer only Arial 12 Bold for detail and Courier New bold 11 for headings etc., you can set all these types of conditions in default settings of crystal reports… so that you don’t need to check each and every point again and again… also you can set number and date formats as customers requirement… like amount should always 0.000 and date always should be 11-Jan-2016 format… etcetera… Hope this helps you additional time in testing… for remaining data related topics you need good analytics to test or compare data… spellings is very common but one should have minimum communication to type correct spellings in report… more than 99% accuracy is acceptable… but remaining 1% is human error which will always happen unless multiple rounds of testings…


surya.g :india: (BOB member since 2009-11-24)