Environment details  | Server Name & Connection of all environments  | |
TNS entries for all environments  | ||
Universe Details:  | Name & Number of Universe  | |
Name & Number of star Schemas with confirmed Dimensions   | ||
Name & Number of tables   | ||
Name & Number of Aliases and Contexts   | ||
Name & Number of classes with some subclasses   | ||
Name & Number of objects   | ||
Name & Number of customized hierarchies   | ||
Name & Number of conditional objects with time conditions   | ||
Name & Number of default hierarchies  | ||
Name & Number of aggregate navigations   | ||
Name & Number of Linked universe  | ||
Security structure   | ||
Security groups  | ||
Manage access restriction mapping (groups and security levels) if any.   | ||
Universe connection name for each environment  | ||
Reporting details:  | Name & Number of Reports  | |
Number of Linked reports  | ||
Reports with multiple data provider  | ||
Number of report level objects  | ||
Customization of the reports(Means if there any standard template for the reports)  | ||
If there any specific alerter for all the reports  | ||
Number of Tabbed reports  | ||
Scheduling time and scheduling process. Multilingual Support information  | ||
Prompts used in reports  | ||
CMC details:  | Access levels of the system(Security analysis)  | |
Number of users/groups  | ||
Any customization of Info view is there..   | ||
Load Balancing system  | ||
Third party software used  | ||
Integration system with the Active Directory of BP with BO  | ||
Document needed  | Data Model   | |
Process flows  | ||
Functional specification   | ||
Operation manual  | ||
A single document which track all objects of all reports available  | ||
Wednesday, August 31, 2011
Questionair for unerstanding a BO project
Subscribe to:
Comments (Atom)