Professional Documents
Culture Documents
BO Dashboard Design and Development Standards
BO Dashboard Design and Development Standards
BO Dashboard Design and Development Standards
Page 2 of 6
Revision
Date
Revision Description
Page
No.
Page 2 of 6
Prev
Page
No.
Action
Taken
Addend
a/New
Page
Release
Notice
Reference
Table of Contents
1
Introduction......................................................................................................................................4
General
General
General
General
Standards
Standards
Standards
Standards
for
for
for
for
Dashboard Design........................................................................5
Metrics Design...............................................................................5
Metric Values and Analytics......................................................5
Metric Universes...........................................................................5
Page 3 of 6
1 Introduction
This document outlines the standards to be followed while designing the BO
Dashboards
Page 4 of 6
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.
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 6
2.4.3
2.4.4
Appropriate functional details should be mentioned for each class / subclass as class
description.
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.
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 6