Below is the 57 points/checks one should consider for developing webi report.These points can be best used at the time of unit testing of webintelligence report.These point can insure to deliver zero defect webi report.
No.
|
Particulars
|
Peer Review
|
Yes/No
|
||
Naming Convention and standards
are followed for
|
||
1
|
Report name
|
|
2
|
Web Intelligence Query provider
|
|
3
|
Report Tab name
|
|
4
|
Prompts text
|
|
5
|
Variable name
|
|
6
|
Title
|
|
7
|
Header
|
|
8
|
Body
|
|
9
|
Footer
|
|
10
|
Section
|
|
11
|
Charts and Legends
|
|
12
|
Block
|
|
Query
|
||
13
|
Use a
name for the query that describes the data.
|
|
14
|
Follow
correct naming conventions in case of multiple queries.
|
|
15
|
."Retrive
duplicate rows check box" is unchecked to retrieve distinct rows.
|
|
Prompt
|
||
16
|
Prompt order
box is used to organize the sequence in which the prompt appears.
|
|
17
|
Naming
convention is followed for prompt text
|
|
18
|
Local
variables are used to store prompt value to reduce maintaince overhead.
|
|
Report Body /Page
Headers/Footers
|
||
19
|
The
report block is aligned as per as business standards.
|
|
20
|
Minimum
margin set on all sides of the report.
|
|
21
|
The
columns of Text data are arranged in logical order (English speakers read
left to right).
|
|
22
|
The
data has been purged from the report.
|
|
23
|
Numerical
columns are right justified.
|
|
24
|
If a
legend or annotation is used, it is in understandable and in an appropriate
font.
|
|
25
|
For
data that spans multiple pages, section breaks are set to keep data and
titles together where possible.
|
|
26
|
The
header used describes the scope of the data.
|
|
27
|
The
header states the time period covered (for example, term, date range, as of date)
for date related information.
|
|
28
|
The
Font of the Report Title is as per as business standards.
|
|
29
|
The
Report Refresh Date font and style are as per as busines standards.
|
|
30
|
The Logo
of the Company is set properly and has tooltip and alternative text.
|
|
31
|
Header
is repeated on every page.
|
|
32
|
Report
last refreshed date is diplayed as per business standards .
|
|
33
|
Print date
is displayed as per the business standards.
|
|
34
|
Page
margins are as per as business standards.
|
|
35
|
Header
and footer font are set according to business standards
|
|
36
|
The footer
has included the page number and total number of pages.
|
|
37
|
The
page number is formatted as per as business standards
|
|
38
|
The
document name (=Document Name) is formatted as per as business standards
|
|
39
|
The title,
header, footer, and any labels have been checked for spelling errors.
|
|
40
|
Images
are stored on the shared location
where BOE has access
|
|
41
|
Break
and section header are formatted as per as business standards
|
|
42
|
For sections, the option to avoid page breaks in a
section is checked.
|
|
43
|
Remove
duplicates is
selected so that a break value will not repeat.
|
|
44
|
Hyperlinks
paths used are absolute path and not the relative path
|
|
Variables
|
||
44
|
Variables
are classfied as per as their datatypes
|
|
45
|
The
Variables are error free
|
|
46
|
Unused
Variables are deleted
|
|
Other Consideration
|
||
47
|
The
report is saved in result view so that it opens in results view, not structure
view.
|
|
48
|
The
appropriate dimension objects have been merged.
|
|
49
|
Detail
objects are associated with the appropriate dimension objects.
|
|
50
|
Report
Tabs are named properly and are in order
|
|
51
|
Report Filter
having proper width and placed in meaningful order
|
|
52
|
Images
have Tool tip and alternative text
|
|
53
|
Report
Linking/Repeating elements are on every page
|
|
54
|
Disclaimer
are there in proper format and place
|
|
55
|
If report
to be exported to other files formats like excel,pdf than formatting is set accordingly.
|
|
56
|
The
alterters properties are set as per as business standards
|
|
57
|
Followed
"Web Intelligence best practices".
|
No comments:
Post a Comment