APR 10, 2012 5:40am ET

Related Links

Revolutionize Your Business Intelligence with Lean, High-Performance Solutions
August 21, 2014
Big Data Technologies Essential for Internet of Things
August 20, 2014
Mobile Apps Require New Development Methods
August 18, 2014

Web Seminars

Attract and Keep Shoppers with Product Information Management
August 21, 2014
Why Data Virtualization Can Save the Data Warehouse
September 17, 2014
Essential Guide to Using Data Virtualization for Big Data Analytics
September 24, 2014

Big Data and the Coming Conceptual Model Revolution


Conceptual modeling, or semantic modeling if you like, is a rather nebulous area in data management. There seems to be a lot of agreement that it is needed, some disagreement about what it is, and little understanding of how to do it. Yet I believe we are now at a point where we will be forced to deal with it in a far more serious way than we have in the past.

Definitional Problems

Get access to this article and thousands more...

All Information Management articles are archived after 7 days. REGISTER NOW for unlimited access to all recently archived articles, as well as thousands of searchable stories. Registered Members also gain access to:

  • Full access to information-management.com including all searchable archived content
  • Exclusive E-Newsletters delivering the latest headlines to your inbox
  • Access to White Papers, Web Seminars, and Blog Discussions
  • Discounts to upcoming conferences & events
  • Uninterrupted access to all sponsored content, and MORE!

Already Registered?


Comments (9)
Hi, Malcolm. Really interesting post. I have a few questions / comments:

1) While I understand your point that the conceptual model should be separate from the logical & physical models, mustn't you, at some level, reconcile these in order to get any value from the conceptual model?

2) How do you get management to pay for developing something (i.e. a conceptual model) that could be big and expensive yet is so far from the physical level?

3) Regarding your point, "Relationships between non-key attributes in an entity", isn't the relationship inherent in that these two items (total price & foreign key relationship to denomination) appear on the same record?

4) Regarding your point about code tables, aren't the business concepts they represent inherent just in the fact that they exist and are modeled?

5) Finally, can you provide some samples of the types of documentation you've used to support your conceptual models?


-- Ben

Posted by Benjamin T | Wednesday, April 11 2012 at 10:36AM ET
Interesting idea for discussing: Conceptual model is business metadata with taxonomy, categorization, business rules and relationship semantic, isn't it ?

Thanks, Simon

Posted by Semion I | Thursday, April 12 2012 at 5:29AM ET
Add Your Comments:
You must be registered to post a comment.
Not Registered?
You must be registered to post a comment. Click here to register.
Already registered? Log in here
Please note you must now log in with your email address and password.
Login  |  My Account  |  White Papers  |  Web Seminars  |  Events |  Newsletters |  eBooks
Please note you must now log in with your email address and password.