Saturday, May 24, 2014

OBIEE Gathering Business Requirements

Gathering requirements will be approached from several ways to ensure the requirements are full fill. And it differs with application environment. Here is what we follow to get the requirements for quick ad-hoc reports. 

Overview :

Brief description of project. Include expected business benefits to be accumulate out of this effort.

Functional Requirements :

Describe in detail with a focus on how you are going to use this report/dashboard data. Add screenshots, flow diagrams as needed. The more details you provide, the easier it would be for us to build
-        In case you have UI mock-ups please attach them
-        List any charts / graphs needed

Data :

List the data elements ("columns") in below format, and add rows as needed. If you are unaware of the data source leave this blank, but getting information on data sources would speed up the process

Data Elements (Columns)
"Data Element"  "Source"  "Description"    "If this is a calculated field please provide the calculations here"
 

How are you getting this data at present? (Leave blank if this is a new request)
How do you want to analyse the data?  (e.g. by date, by POD, by server, by tier, by customer etc. etc) Please list here
Data load job schedule time
Data retention period in days

Distribution :

Type of Report   :   Online / Periodic Mailer/Both
If periodic          :   Frequency of mailers
Any preferred data/time of mailing?
Would this have exec visibility?

Users:

User Name and emailid to give access.
Any user/group to be specifically excluded due to information protection requirements? 

GUI :

Any alerts needed based on data thresholds (e.g. storage usage > 80% for a week)? Please provide details here.

-Asifkhan



No comments:

Post a Comment