Six Basic Interrogatives “6BI” Design Framework

1

Six Basic Interrogatives “6BI” Design FrameworkAn approach for aligning the design of desicion support and business intelligence systems with the Business Architecture.

Wayne Kurtz

Six Basic Interrogatives “6BI” Design FrameworkAn approach for aligning the design of desicion support and business intelligence systems with the Business Architecture.

Wayne Kurtz

2

Agenda

• Background• The Technique• Traceability• Q and A

3

Background

• Based on Client Engagements, Best Practices, Research & Literature

• Uses Industry Standards - OO and ER Synthesis

• Repeatable Process• Scalable – upward or downward

• Open Methodology – can be applied outside BI

• Flexible – not carved in stone

4

Business Object Categories

5

The Value Statement

A Party (“Who”) produces and/or consumes Products (“What”) by performing Activities (“How”) in response to Events (“When”) at Locations (“Where”) guided by Motivators (“Why”)

6

6BI, Zachman and DoDAF – Validation

Row 2

Row 3

7

Party-Product Association Model

<Associated only indirectly >

8

The Technique

• Step 1- ID & Sort the Business Entity Types - Place them within the context of the Business Object Categories (BOC):

Ask yourself: Does the entity type address a basic interrogative? (who? what? where? when? why? or how?)

• Step 2 - Categorize Source Tables & Data Elements - Create a Logical Data Model (LDM) with data structures placed into BOC Subject Areas (Sas), not Functional SAs:

You have the physical data structures (from the Technical Architecture) organized into the logical BOCs (from the Business Architecture)

9

Mapping

• Step 3 – Map the Physical thru the Logical to the Dimensional: Each attribute of each Dimension is mapped thru the BOCs to business entity types back to its originating source data element

Dimensions

Business Entity Types

Business Object Categories

Data Elements

Dimension

10

Traceability

• Data Lineage

• Business Architecture and Technical Architecture Alignment

• “Middle-Out” Data Mapping

11

Bridging the Barrier

Semantic Barrier

Technical Architecture- Data, Applications, etc.- System Specs

Business Architecture- Mission, Vision, Stretegy, etc.- Business Object Categories

Ladd

er o

f Abs

trac

tion

“6BI”

12

References

• Data Model Patterns, Conventions of Thought by David C. Hay

• Database Design for Smarties, Using UML for Data Modeling by Robert L. Muller

• The Data Model Resource Book, A Library of Logical Data Models and Data Warehouse Designs by Len Silverston, W.H. Inmon, Kent Graziano

• An Activity-Based Methodology for Development and Analysis of Integrated DoD Architectures by S. Ring, D. Nicholson, J. Thilenius, S. Harris

• The Problem Space by Dan Tasker • A framework for information systems architecture by John

Zachman

13

Questions?

14

Extra slides

15

Zachman

16

DODAF