Defining business rules in the business' language

2015-09-23_12-40_520.gifOne of the biggest problems with any business intelligence project is for all involved to fully understand the data model and it's relationship to the business of the organization. Without an excellent business/data analyst, much will be lost in the translation. An article in DM Review addresses this very issue, however, largely from the technical person's point of view. Since this blog is primarily aimed at business leaders and decision makers (information consumers) that require business intelligence to make informed decisions, I won't go into gory detail summarizing the article.

The most useful tool mentioned in the article was this spreadsheet (pictured) to help put business language around a logical data model.

What's a logical data model?

[Silence fills the air.]

Exactly.

As a business decision maker you don't really need to worry about it so much, however, your analysts and technical staff developing the business intelligence architecture sure do.

Essentially it is the relationship between and amongst the tables that represent the business data.

Without a rock solid understanding of the "business rules" that describe the data, the business intelligence architecture will fail.

This tool is as good as any I've seen to help business decisions use their own language to precisely describe the relationships in the data model.

Think of this tool as the Rosetta Stone of BI. Okay. Never mind. I'm sure I'm overstating it. But it is useful nonetheless.