Business Objects Reports Design and Development Standards

Page 2 of 7

Business Objects ReportsDesign and Development Standards

V 1.0

Business Objects Reports Design and Development Standards

DOCUMENT REVISION LIST

Document Name: Business Objects Reports Design and Development Standards

Release Notice Reference (for release):

Rev. No.

Revision Date

Revision Description Page No.

Prev Page No.

Action Taken

Addenda/New Page

Release Notice Reference

Page 2 of 7

Business Objects Reports Design and Development Standards

Table of Contents

1 Introduction......................................................................................................................................4

2 Performance Management Standards for Dashboard, Metrics & Universe5

2.1 General Standards for Dashboard Design........................................................................52.2 General Standards for Metrics Design...............................................................................52.3 General Standards for Metric Values and Analytics.....................................................52.4 General Standards for Metric Universes...........................................................................5

Page 3 of 7

Business Objects Reports Design and Development Standards

1 Introduction

This document outlines the standards to be followed while designing the BO Dashboards

Page 4 of 7

Business Objects Reports Design and Development Standards

2 Performance Management Standards for Dashboard, Metrics & Universe

These standards are meant for all Dashboards and Metrics generated by the system.

2.1 General Standards for Dashboard Design

Analytical Frames should be properly top and left aligned. Frame borders should be removed by customizing the dashboard. As far as possible, make sure the frames should not have any scrollbars.

2.2 General Standards for Metrics Design

If more than 1 or 2 metric measures are present in one fact table then go for self join on table otherwise apply where condition on measure objects.

Use the proper syntax in self join (given in manual) to avoid any error while creating metrics.

Choose the same aggregate function for the metric that is used for universe measure.

Select the number format of the measure as per the client standards or see the standards mentioned in the next section.

2.3 General Standards for Metric Values and Analytics

All numbers should be right aligned. Measures like Total Purchase, Discount Taken etc should be expressed in

thousands with 0 decimal precision (may be some limited exceptions as required)

Percentages like LD% should be expressed with 1 decimal precision (e.g. 94.6%)

Negative numbers should be in parenthesis and red (Set the format of negative numbers as (#, ##0) [Red])

Use commas to separate 000 points (Set the Format of positive numbers as #, ##0)

2.4 General Standards for Metric Universes

2.4.1 Names Universe name should start with or end with “pm_” to identify them separately. Name should define the subject area covered in that universe.

2.4.2 Classes Name of the class should be meaningful, as these become the subject areas in PM. All class names should be in Init-cap format. Example: Client, Summarized Fact. Two words in the name of a class should be separated by space. Subclasses should be created if required. If names of subclasses are same in two

different classes, then the subclass names should be prefixed by the class name.

Page 5 of 7

Business Objects Reports Design and Development Standards

Appropriate functional details should be mentioned for each class / subclass as class description.

2.4.3 Objects All object names should be in Init-cap format. Example: Time, Client Id etc. Two words in the name of an object should be separated by space. The qualification for each object should be correctly mentioned. All measure objects in the universe may be included in only one class. (This is entirely

dependent upon the requirements.) Detail objects should be created if required. If the detail objects of two different parent

objects have same names, then the detail object names should be prefixed by the parent object name.

Appropriate functional details should be mentioned for every object as object description. If the object is a calculated object then the detailed calculation should be mentioned.

2.4.4 Structure All tables in the structure should be logically positioned. All tables should have 3D border. The alias tables should show the original table name along with the new alias. All columns in all tables should be left aligned.

Page 6 of 7