Fabian Pascal

Down to the Basics of Business Modeling Concepts

NO RATINGS
View Comments: Oldest First | Newest First | Threaded View
BethSchultz
User Rank
Blogger
Best practice?
BethSchultz   1/16/2013 5:36:47 PM
NO RATINGS
Hi Fabian, I like the idea of laying out the definitions in this way. What's your advice on how to make sure people within a company are all working from the same dictionary, so to speak, as they work on their business modeling? Should they have a document with all of their terms spelled out, for example?

dbdebunker
User Rank
Data Doctor
Re: Best practice?
dbdebunker   1/17/2013 12:02:13 PM
NO RATINGS
Hi, Beth,

Of course, how businesses do that  makes the difference between success or failure.

The large and complex databases require (1) a formal process (2) management support (3) modeler-user-manager-dba team (4) thorough knowledge of the business (5) data foundation knowledge (6) proper documentation and design tools.

I believe that except for cases of relatively simple databases used by only a few application/users, the current practice of assigning a programmer/developer to do everything from business modeling to database design to database administration to application development will usually end up with serious problems.

The notion that eschewing this saves money and time is an illusion due to scarcity of foundation knowledge: the opposite is true. The argument that modeling and design is difficult, takes a long time, is expensive and so on is certainly true, but there is no free lunch: if you want the benefits of a true db system, that's the price for it, and thinking that you can eschew it and still get the benefits is delusional. You can do it, but then you must do it consciously and aware of the benefits you give up. The ndustry caters to this delusion by promoting magic wands.

Simplicity and parsimony are critical. Given the complex nature of business reality and the above process, it is crucial that we don't pile complexity of methodology and tools on top of it. Everything should be as simple as possible, but not simpler. That's the issue that the relational model addresses and the failure to comprehend that is one of the core problems in IT.

kq4ym
User Rank
Data Doctor
Re: Best practice?
kq4ym   1/28/2013 9:02:07 AM
NO RATINGS
Good points, more than just a programmer/developer is needed to make sense and hopefully some company profits out of the data massage.

Lots of data, means lots of brainpower is needed to figure the best ways to use it, and the persistence to keep trying new ways of looking at what's going on. It's not the first result that will define the answers.

dbdebunker
User Rank
Data Doctor
Re: Best practice?
dbdebunker   1/28/2013 1:10:29 PM
NO RATINGS
All that data were generated for different purposes and, therefore, do not have a common structure to which common sound operations can be applied for analytical purposes. There is this common delusion that such data can be taken as is and, without any effort, can be mined for information.

Another aspect is a disregard for the cruacial importance the ratio of method and tool complexity to usefulness. The purpose of models is to simplify the reality of interest to the most essential and to structure it optimally for multiple analytical purposes. Complexity and lack of generality defeats their purpose. This is largely missed by both business and IT and the industry encourages the opposite.

Codd's genius was not only to apply theory to data management, but also that the theory provides an optimal ratio of simplicity to generality: the relational approach is the simplest way to deal with data that is general enough to handle a vast majority of informational needs. In my paper "Businss modeling for database design" I specify the criteria that an alternative approach must satisfy to be superior. Unless it does, we trade down. The trite statement "the right tool for the right job" more often than not reflects a lack of foundation knowledge.

Best regards,
Fabian Pascal
www.dbdebunk.com
http://en.wikipedia.org/wiki/Fabian_Pascal
http://www.linkedin.com/profile/edit?trk=tab_pro
http://dbdebunk.blogspot.com/p/about_4.html
http://dbdebunk.blogspot.com/p/papers_3.html
http://dbdebunk.blogspot.com/p/seminars.html


 

Information Resources
More Blogs from Fabian Pascal
Something's too often missing from job requirements for data scientists: relational theory.
Fabian offers his guidelines for understanding business rules and table constraints.
Analysts must know database tablesí interpretation -- the business rules underlying them -- which is rarely documented.
Before you dive into analytics, you need to understand what the properties in a database really represent.
Guessing the meaning by visual table inspection is a risky proposition, likely to lead astray. It helps if the analyst knows the types of rules to expect.
Radio Show
Radio Shows
ARCHIVE
James M. Connolly
Analytics: Your Defense Against Cyber Threats


5/27/2015  LISTEN   60
ARCHIVE
James M. Connolly
Big Data & Big Pharma: How Analytics Might Save Your Life


5/19/2015  LISTEN   37
ARCHIVE
James M. Connolly
Live Interviews From SAS Global Forum


4/28/2015  LISTEN   11
ARCHIVE
James M. Connolly
How to Hire Great Analytics Talent


4/23/2015  LISTEN   51
ARCHIVE
James M. Connolly
Sports Analytics Mean Fun and Business


3/24/2015  LISTEN   4
ARCHIVE
James M. Connolly
Secure Your Big Data in the Cloud


2/26/2015  LISTEN   114
ARCHIVE
James M. Connolly
Make It Big As a Data Scientist in 2015


2/11/2015  LISTEN   106
ARCHIVE
James M. Connolly
Big Data, Decisions & the Simulated Experience


2/3/2015  LISTEN   87
ARCHIVE
James M. Connolly
A Chat About Big Data, Machine Learning & Value


1/15/2015  LISTEN   125
ARCHIVE
Curtis Franklin Jr.
An Infrastructure for Analytics


12/18/2014  LISTEN   63
Information Resources
Quick Poll
Quick Poll
Infographic
Infographic
It Pays to Keep Insurance Fraud in Check
While 97% of insurers say that insurance fraud has increased or remained the same in the past two years, most of those companies report benefits from anti-fraud technology in limiting the impact of fraud, including higher quality referrals, the ability to uncover organized fraud, and improve efficiency for investigators.
Follow us on Twitter
Follow us on Twitter
Cartoon
CARTERTOONS
Like us on Facebook
Like us on Facebook
About Us  |  Contact Us  |  Help  |  Register  |  Twitter  |  Facebook  |  RSS