Just wanted to share how High Level OBIEE Design Template looks like
Introduction
< Give a brief background about the project and the objectives of the design document.>
Purpose
<Provide the purpose of this document here.>
Scope
< Provide the scope of this document >
Design Overview
<This section defines the overview of the Design document, including the key points in the design>
Environment Setup
<This section contains details about the environment setup.>
Description<This section shall contain the details of the proposed architecture for the OBIEE application. Include a brief description about the components of the OBIEE application here.>
<This section shall contain the information about the server configurations done for OBIEE in the development, testing and the production environment. Also include the diagrams here.>
<This section shall contain details about how the development is done – How the repository is configured (whether multi-user development environment is set up for repository configuration or each developer is working on the repository asynchronously).
Specify how the reports and dashboards will be created (whether on the developers local machine and the catalog objects copied to the servers’ catalog later or is the development done on the server directly).>
Repository
This section contains a brief description of
the OBIEE repository, including the 3 layers of the repository. Also specify
the following details:
·
How the
business models and presentation catalogs will be created in the repository
·
List the
presentation catalogs to be created
Presentation Catalog
|
Description
|
Intended Users
|
Business Model Source
|
< Name of the presentation catalog.>
|
<Description of the presentation catalog>
|
<Intended user groups of
the presentation catalog>
|
<Source of the Presentation Catalog>
|
·
How the
OBIEE application users would be authenticated
·
Data level
security to be implemented
Repository Group
|
Data level security
|
<Name of the repository group>
|
Data level security to be implemented on
the repository group
|
·
How the cache
management would be done.
Presentation
Catalog
This section shall contain the following
details:
-
A brief description about the components of the presentation catalog that will be used to create the reports, dashboards and iBots
-
Dashboard and reports to be created.
-
List the iBots to be created and their purpose.
-
How the dashboard and report level security is implemented.
- A brief description about the components of the presentation catalog that will be used to create the reports, dashboards and iBots
- Dashboard and reports to be created.
- List the iBots to be created and their purpose.
- How the dashboard and report level security is implemented.
Dashboard
|
Dashboard Page
|
Report Name
|
<Name of the Dashboard>
|
<Name of the
dashboard page>
|
<Name of the Report>
|
<Name of the Report>
|
||
<Name of the
dashboard page>
|
<Name of the Report>
|
|
<Name of the Report>
|
iBot
|
Purpose
|
<iBot Name>
|
<Purpose of the
iBot>
|
Dashboard Name
|
Intended Users
|
<Name of the Dashboard>
|
<Intended users of the dashboard>
|
Consider the following:
- How do you plan to back up the repository and the presentation catalog?
- How often do you plan to back up?
- What are the necessary requirements for recovery?
--Asif Pathan
No comments:
Post a Comment