Universe Designer Checklist :- Unit Testing of Universe

Below is the 54 points/checks one should consider for developing universe .These points can be best used at the time of unit testing of Universe.These point may insure to deliver zero defect Universe design.

No.	Particulars	Peer-review
		Yes/No/NA
Connection
1	Connection to the Database is according to the requirement
2	Parameters - SQL Tab - Multiple SQL statements for each measure  is unchecked
3	Parameters - SQL Tab - Cartesian Products - Prevent is checked
4	Database Connection named or define in such a way that it refers to actual database
Tables
5	Alias Tables are named with proper functional use.
6	For Aliasing tables, the original one noted with ‘Aliased Table – Do Not Remove’
7	Tables are arragned in the Structure as per Business/Functional logic
8	Tables are connected or joined.
9	Isolated tables are placed in separate universe.
10	Context are named with proper functional use.
11	All joins falls under some meaningful named context
12	Cardinalities are set.
Class
13	Universe Classes / Subclasses Defined as per the business logic & Naming Convention
14	Description for the use of each Class/Subclass is given
15	Maximum number of the objects in the classes are restricted to 30
Objects
16	Objects used in calculation are of type Measure.
17	Objects used in Analysis are of type Dimension.
18	Object Description is given properly.
19	LOV Option for each Dimension is set only for required Objects
20	LOV option for each measure objects is unchecked.
21	"Automatic Refresh before Use" option is checked for LOV Objects.
22	Significant name is given to the list name under Object properties for editible LOV.
23	Duplicate Object names are there in different classes.
24	Objects and classes naming convention is as per business terms
25	Timestamp is not present in the LOV's of properly defined Date prompt.
26	Object formatting  specified at universe level, especially with measures. (Formatting like dates, currency  etc.)
27	Multiple SQL statements for each measure should be turned off, to generate optimum SQL. (This option should be checked if the measures being retrieved in the same query involve different tables)
28	All the Objects are arranged in alphabetical order within calss and classes are arranged ina hiearachial order from highest to lowest grain.
29	WHERE' Clause is not used in any objects at the time of creation in universe.
30	HTML Objects like hyperlink are created at Universe level.
31	Only required fields of a Table are included as  Objects instead of the entire fields of the Table.
Predefined Conditions and Hierarchies
32	Condition Objects are created mostly at Universe level.
33	Description is given for each pre-defined condition.
34	LOV is provided for a associated dimention when condition is resulting in a prompt.
35	Time dimension related predefined conditions are expressed as Current year, Current month, previous year, last (x) weeks etc making it easy for scheduling daily/weekly/period based reports.
36	Custom hierarchies are defined and done according to the end-user’s requirements
37	Regularly used conditions e.g. current year / latest date do not have prompts.
Import/Export
38	The path for Import, is in the Business Objects' Universe folder.
39	Universe is locked when Administrator\ Designer does not want any user to Import/Export.
40	Before Exporting Universe 'Integrity check' is performed
41	Folders are structured in such way that secured environment is maintained.
42	While deleting any object from an exported Universe ,impact analysis is performed.
Use Aggregates for measures
43	Aggregation is used in all measure objects
44	In measures SQL aggregation functions are present.
Use Partitions for high volume fact tables
46	To boost query performance partition of high volume fact tables is used.
47	To improve query performance aggreate tables,materialised views with aggregate awareness are included.
48	Arrey fetch size parameter optimal value is set up.
Other Considerations
49	Short cut Joins are used where ever possible to improve performance.
50	Integrity check and database straucture refresh is performed.
51	Unnecessary Objects are removed from universe before moving it to production.
52	Universe is created from the end-user perspective, and not from a developer’s perspective.
53	Length of query time and Number of rows retrived is set as per the database.
54	Universe is tested based on the functional requirement

WebIntelligence Report Checklist :- Unit Testing of WebI Report

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".

CheckOut-:- WebIntelligence Interview Question