business requirements gathering for bi

32
Business Requirements Gathering Webinar Connecting Content | Driving Performance 1

Upload: corey-dayhuff

Post on 17-Aug-2015

118 views

Category:

Data & Analytics


5 download

TRANSCRIPT

Page 1: Business requirements gathering for bi

Business Requirements Gathering Webinar

Connecting Content | Driving Performance

1

Page 2: Business requirements gathering for bi

Webinar Presenter

Joe HoganPractice DirectorBusiness [email protected]: 614-774-2296

2

Page 3: Business requirements gathering for bi

Smarter Business Requirements

1. Ask good Business Use Questions and document the answers

2. Complete a Source System Inventory

3. Prioritize the Source System Inventory

4. Complete the Data Element Inventory

5. Prioritize the Data Element Inventory

6. Write Data Behavior Statements

7. Identify Data Element Thresholds

8. Conduct a Data Element ‘Sweep’

9. Determine the Authoritative Source for data element

10. Document the Data Provisioning

11. Determine Data Granularity and Aggregation

12. Present the Business Information Model to business users and present the physical data model to technologists 3

Page 4: Business requirements gathering for bi

Need: A Common Statement

Your Company…• Desires comprehensive, company-wide analytics to support decisions

that:o Are proactive and focused at multiple management levelso Improve company performance and accountabilityo Establish repeatable compliance reports with easeo Enhance access and service for employeeso Leverage technology assets for expanded access and serviceo Unify the digital company

• Seeks advice on business intelligence tools• Wants to explore available BI offerings from software vendors like

Microsoft, IBM, MicroStrategy and Oracle.• Establish a business intelligence center of excellence with company-

wide governance4

Page 5: Business requirements gathering for bi

Example: Acme TechWare DistributorVision and Business Need Statement

• The Data Warehouse (BI solution) mission is to drive sales, increase profit and enhance distributor satisfaction with Acme TechWare Distributor by :o Creating visibility to product and customer informationo Providing analyses of information from multiple viewpointso Leveraging a consistent, standard, and timely single repository of

information from our operational systems

• Resulting in:o Visibility of key performance indicators that measure our business

successo Analysis of issues and trends that affect our business performanceo Guidance on where to target resources and actions for improvemento Measurements to evaluate the success of our actions 5

Page 6: Business requirements gathering for bi

Example: Interview Prep Questions

1. What opportunities exist to dramatically improve your management at your company, based on improved access to information? What is the financial impact? What is the efficiency impact? Given that Company is partially funded by a county levy, the Business Intelligence tool can connect student enrollment to voter registration information. This connection would allow Company to target specific geographies with pertinent messages about the need for a levy. Are there other examples of how information can dramatically improve my company’s goal achievement?

2. Is there a task, however large or small, that is difficult to complete due to inadequate data, inadequate organization of data or lack of reports? By automating much of the routine reporting tasks, the Business Intelligence tool can free executives and their teams to analyze larger more complex problems. One example might be automation of the required tracking of international customer registration.

3. On a daily basis, how do you identify problems and exceptions or know when the Company’s objectives are not being met? Daily is significant as it allows our Company to leverage the Business Intelligence tool to move from an after-the-fact reactive mode to an intervention proactive mode.

6

Page 7: Business requirements gathering for bi

7

Business Use Questions

Ask questions that seek ‘dimensionalized’ answers! Document!• What are your key business objectives, drivers and metrics and how do you

currently measure your success?• What opportunities exist to dramatically improve your business

management based on improved access to information? What’s the financial impact?

• What information is requested from your customers and suppliers?• What key information is required to make or support the decisions you make

in the process of achieving your goals and overcoming obstacles? How do you get this information today?

• How do you identify problems and exceptions or know you’re headed for trouble?

Page 8: Business requirements gathering for bi

Business Use QuestionsAn Example

Question: Is there information, which is not available to you today, that would have significant impact on your goal achievement?

Answer:• Complete and fully integrated Canadian sales revenue for all 42 product categories across

8 sales districts for the past 3 years – updated daily.

• Customer hierarchy/rollups from customer viewpoint and the sales organization viewpoint for all active customers over past 10 years.

• Need customer segmentation information on 7 market spaces, 12 demand segments and 20 value segments.

• Customer trends and growth rates in sales revenue, gross margins, order frequency and order lot size by month for past 10 years.

8

Page 9: Business requirements gathering for bi

Business Use QuestionsDeveloping Dimensions from Notes

Question Response

1. What prevents you from meeting the needs of supporting the business?

2. What are the key issues you face today? The current process has many manual compnents which limits the group of Acme ability to meet SLAs and scale efficiently.

3. What’s the benefit for Acme that is derived from the use of the reporting system?

Helps to grow business and revenue.

4. How do you identify problems or know you’re headed for trouble? The current process is manual and time consuming.

5. Where do you stand compared to your competition in the use of information technology?

The current version of BO is 5.1.8 and Oracle DB is 8.1.7. Both of these versions are not supported by the vendors.

6. Are you able to respond quickly to market conditions?

7. Which reports do you currently use? Management reports, Other reports.

8. What data on the report is important?

9. How do you use the information? 9

Page 10: Business requirements gathering for bi

Business Use QuestionsQualifier Matrix

• Declare dimensions (report filters)• Declare facts (measures)• Determine which facts can be measured

against what dimensions

10

Page 11: Business requirements gathering for bi

Declare Dimensions

Dimension Name Dimension Description

Date Contains all of the attributes associated with the date that activityoccurred.

Time Contains attributes about the time when an activity occurred.

Billing Date Contains all of the attributes associated with the date that products and/or services were billed to the customer.

End Date Contains all of the attributes associated with an end pr resolutions date (contract end, service call resolved).

Customer Represents both commercial and consumer customers and all ofthe associated attributes.

Product Contains information about products and services that we sell.

Pricing Package Describes the pricing used for customer billings.

11

Page 12: Business requirements gathering for bi

Declare Facts

Dimension Name Dimension Description

Revenue Revenue collected from retail POS and wholesale ordersdefined as units times actual sales price.

Units Sold The actual number of units sold at the order line detail.

Product Count The count of unique products (SKU numbers) on a given order.

Contribution Margin The sales price less the fixed costs associated with the product(SKU)

12

Page 13: Business requirements gathering for bi

Qualifier Matrix

13

Page 14: Business requirements gathering for bi

Data: MeasuresCumulative and Non-Cumulative

• Non-cumulative measures cannot be stored in the physical database; they must be calculated at the OLAP presentation point.

• Non-cumulative measures typically have division, % or are ratios like:

• – Sales Win Rate % – GPA – Top 10%

14

Page 15: Business requirements gathering for bi

15

Source System Inventory

Page 16: Business requirements gathering for bi

Source System InventoryAn Example

16

Page 17: Business requirements gathering for bi

Prioritize Source System InventoryAn Example

17

Page 18: Business requirements gathering for bi

Business Use QuestionsQualifier Matrix

Make an inventory of all the data elements that users require for business decisions. The list should be from the business user perspective.• Business name for data element (the names on the screens)• Application(s) were used• Screen(s) were used• Examples of data element values• Desired display format like $#,###.## or ’01-Product Code’• Measure or ‘Report Filter’ (Dimension)• Is the ‘Report Filter’ flat or hierarchical?• Update frequency• Create user data groups from the data elements

Don’t worry about the data source mappings now! 18

Page 19: Business requirements gathering for bi

Data Element InventoryAn Example

Ref Data Group Report Filter (Dimension or Measure)

List of Values or Measure Format

Hierarchical or Flat Filter or Measure

Source (Database or Business Rule)

Siebel Screen Tab(s)

Update Frequency

1 Opportunity Sales Stage and Sales Phase

External Appointment Set Opportunity Management Ass’tInternal Proceed Stop Approved

H Siebel Opportunities Daily

2 Opportunity Opportunity Revenue Type ActualShippedBilledBookedProjectedQuota

F Siebel Opportunities Daily

3 Opportunity Opportunity Priority YesNo

F Siebel Opportunities Daily

4 Opportunity System Generated YesNo

F Siebel ContactsOpportunities

Daily

5 Opportunity Opportunity Created Date MM/DD/YYYY F Siebel Opportunities Daily

6 Opportunity Opportunity Count ###,# M Calculated N/A On demand

19

Page 20: Business requirements gathering for bi

Data Element InventoryExercise Screenshot #1

20

Page 21: Business requirements gathering for bi

Data Element InventoryExercise Screenshot #2

21

Page 22: Business requirements gathering for bi

Prioritize Data Element InventoryAn Example

Ref Data Group Report Filter (Dimension or Measure)

List of Values or Measure Format

Hierarchical or Flat Filter or Measure

Source (Database or Business Rule)

Siebel Screen Tab(s)

Update Frequency

1 Opportunity Sales Stage and Sales Phase

External Appointment Set Opportunity Management Ass’tInternal Proceed Stop Approved

H Siebel Opportunities

Daily

2 Opportunity Opportunity Revenue Type

ActualShippedBilledBookedProjectedQuota

F Siebel Opportunities

Daily

3 Opportunity Opportunity Priority

YesNo

F Siebel Opportunities

Daily

4 Opportunity System Generated

YesNo

F Siebel ContactsOpportunities

Daily

5 Opportunity Opportunity Created Date

MM/DD/YYYY F Siebel Opportunities

Daily

6 Opportunity Opportunity Count

###,# M Calculated

N/A On demand

Prioritize on Data Group because:1. Translate nicely to

dimensions in the physical model

2. Determines any battle ground early

3. Reveals any hidden data elements

22

Page 23: Business requirements gathering for bi

Data Behavior Statements

Write statements that describe how the data relate.• Ask business about how one Data Group relates to another.• Drill from top down on one Data Group.• Think in genealogy terms! Grandparents, parents, children and twins.• ‘Report Filters’ and measures both have behaviors.• Ask business questions about extreme cases.• Determine if the data element is nominal, ordinal, interval or ratio type.• Determine if a data element is slow changing.• Don’t forget to ask about history of data behaviors. Has the data element always behaved this

way?

Data behavior statements help determine the date model dimensions! 23

Page 24: Business requirements gathering for bi

Data: ClassificationData Type Determination

NOIR• Nominal – Red, Yellow and Blue

Just a name with no order or magnitude

• Ordinal – 1st, 2nd and 3rd

An order, but no magnitude

• Interval – 1”, 2” and 3”An order, a magnitude but absolute zero

• Ratio - -2, -1, 0, +1, +2 CAn order, a magnitude and below zero possibilities

Nominal and Ordinal data type elements are dimensions and Interval and Ratio data type elements are facts in the data model. 24

Page 25: Business requirements gathering for bi

Revenue change month-over-monthCategorize each data element as Nominal, Ordinal, Interval or Ratio

• Revenue change month-over month• Sales districts North, South, East and West• Product rank by gross revenue for first quarter 2006• Total units of product sold• Shipping weight per product• Order type and order sub-type• Gross Profit Year-To-Date• Birth date of client

25

Page 26: Business requirements gathering for bi

Data: Behavior StatementsSlowly Changing Dimensions

• Slowly Changing Dimension:o (Type One), doesn’t preserve historyo (Type Two), preserve a version of historyo (Type Three), Hybrid of Type One and Two

• Users typically want a “Type Two” methodology of SCD• A Type Two change writes a record with the new attribute information and

preserves a record of the old dimensional data.• Type Two changes let you preserve historical data.• Implementing Type Two changes, after the fact, will require significant analysis and

development.• Type Two changes accurately partition history across time more effectively than

other types.• Because Type Two changes add records, they can significantly increase the

database’s size. 26

Page 27: Business requirements gathering for bi

Data: Star SchemaA Quiz

Q. If a star schema has 3 dimensions and one fact:- Class with 1000 rows- Time with 365 rows- Faculty with 2000 rows- Registration transactions fact table of 50 rows,

How many rows are returned in a query of select * with all dimensions joined?

R. 50What else can you tell about the institution? 27

Page 28: Business requirements gathering for bi

Data: Behavior StatementsOrganizational Hierarchy Types

Balanced Hierarchies

• All branches of the hierarchy descend to the same level, and each member’s logical parent is the level immediately above the member.

Unbalanced Hierarchies

• Branches of the hierarchy descend to different levels. For example, an Organization dimension contains a member for each employee in a company.

Ragged Hierarchies

• The logical parent member of at least one member is not in the level immediately above the member. This can cause branches of the hierarchy to descend to different levels. 28

Page 29: Business requirements gathering for bi

Data Behavior StatementsHierarchy Types, OLAP Interface

A table can translate three ways to the semantic layer of the OLAP tool:

• One to One – The table column translates to one object in the semantic layer.• Temporal Hierarchies – A hierarchy is generated from the rows within a

column; this only happens in a reporting time dimension.• Traditional Hierarchies – Multiple table columns like, Sales Organization and

Department and Unit, translate into ‘Sales Org Hierarchy.’

Cloistered Data?The Primary and Foreign Keys of the physical tables are never seen within the semantic layer, and are never seen by the report consumers. Only the business keys like Customer Name are viewable to the report consumers. 29

Page 30: Business requirements gathering for bi

Data Behavior StatementsAn Example

Orders• Order number is unique within System A and within System B but not

across System A and System B.• Order number format changed in 1985 to 12 numbers from 9 numbers

and letters.• Orders have 1 to 999 maximum order lines in System A and 1 to 99 in

System B.• An order line contains only 1 product in System A. An order line in

System B can have 1 to 9 products.• Order line status in both systems is: ‘Placed,’ ‘Credit Check,’ ‘Packing,’

‘Ship Hold,’ ‘Shipped,’ ‘ Backordered’ and ‘Received.’• ‘Backordered’ order lines have a status that is updated daily. 30

Page 31: Business requirements gathering for bi

Smarter Business Requirements

1. Ask good Business Use Questions and document the answers2. Complete a Source System Inventory3. Prioritize the Source System Inventory4. Complete the Data Element Inventory5. Prioritize the Data Element Inventory6. Write Data Behavior Statements7. Identify Data Element Thresholds8. Conduct a Data Element ‘Sweep’9. Determine the Authoritative Source for data element10. Document the Data Provisioning11. Determine Data Granularity and Aggregation12. Present the Business Information Model to business users and present the physical data

model to technologists 31

Page 32: Business requirements gathering for bi

Webinar Presenter

Joe HoganPractice DirectorBusiness [email protected]: 614-774-2296

32