Portals eNewsletters Web Seminars dataWarehouse.com DM Review Magazine
DM Review | Covering Business Intelligence, Integration & Analytics
   Covering Business Intelligence, Integration & Analytics Advanced Search
advertisement

RESOURCE PORTALS
View all Portals

WEB SEMINARS
Scheduled Events

RESEARCH VAULT
White Paper Library
Research Papers

CAREERZONE
View Job Listings
Post a job

Advertisement

INFORMATION CENTER
DM Review Home
Newsletters
Current Magazine Issue
Magazine Archives
Online Columnists
Ask the Experts
Industry News
Search DM Review

GENERAL RESOURCES
Bookstore
Buyer's Guide
Glossary
Industry Events Calendar
Monthly Product Guides
Software Demo Lab
Vendor Listings

DM REVIEW
About Us
Press Releases
Awards
Advertising/Media Kit
Reprints
Magazine Subscriptions
Editorial Calendar
Contact Us
Customer Service

Data Management Association (DAMA):
Hitchhiking to a Semantic Model

online columnist Data Management Association International - DAMAI     Column published in DMReview.com
April 27, 2006
 
  By Data Management Association International - DAMAI

This month's column is contributed by John Schley, president, DAMA International.

A few years ago, I had the good fortune to develop an enterprise-wide semantic model - except I didn't know that's what we were doing.

Coming from a data management background, I called it a conceptual data model. A large project to reinvent our mortgage company's loan servicing system was kicking off, and I was new to the business. As a way to compensate for my lack of business knowledge, I asked the project team to develop a conceptual data model of the major entities in that space. This turned out to be more complicated than it may seem, because the different parts of the company used the same terms differently. Was it a loan when it was applied for ("application"), signed ("closed") or when we had completed our final review of all the loan documentation ("post-closing")? The answers varied, depending upon who was doing the answering. As we developed our conceptual data model, we came together to concisely define each entity. We kept the process moving, and in a few weeks, we had identified and defined approximately 50 business concepts in our "concept model." I use the term concept model, because term "conceptual data model" didn't make sense to the business partners. They didn't see this as focusing on data but on their business terms. Using their term increased their sense of ownership in the effort.

A year or two after that, the organization adopted an object oriented (OO) approach to systems development. The OO developers wanted a high-level class diagram that showed the major objects in the enterprise so they could begin building components around them. Rather than start a new effort to search these objects out, they recast the concept model developed earlier as a class diagram and drove discovery and documentation of another hundred or so classes/entities.

Not long after that, the company was sold to another mortgage company. In preparation for the conversion to the new company's systems, a large-scale effort was made to document all our data structures. The data management staff and I used this opportunity to not only document our physical data models but leverage it into a way to create a home-grown enterprise logical data model by "logicalizing" the physical data elements into a single logical view. This "bottom-up" effort resulted in a logical model that encompassed approximately 75 percent of the company's structured data.

Over this time, we had developed a set of semantic models that integrated data across the enterprise. Along the way, we had filled in the cells in the data column of John Zachman's Framework for Enterprise Architecture and built links between the different levels to associate different perspectives of the same data. It had morphed from a concept model to a class diagram to an attributed logical data model, hitchhiking on different projects with different goals. The final product was driven by different efforts but remained intact to aid the organization's future development.

High-level semantic work is valued by the business, although it must be given a name that is meaningful to the business and it must meet a business need. This kind of work cannot be prescribed by information technology, project management or by anyone's "best practices," but must relate directly to an existing business problem and be substantial enough to help solve that problem. When those pieces are aligned, it's time to stick out your thumb and hitch a ride to a semantic model.

Check out a DAMA International chapter meeting near you to hear experiences like this and learn about data management from other practitioners and thought-leaders in the field. Visit our Web site at www.dama.org to learn more on how to get involved with DAMA.

...............................................................................

For more information on related topics visit the following related portals...
Data Management, Enterprise Information Management and Semantic Web.

The Data Management Association International (DAMA International) is a global not-for-profit, vendor-independent association of data and information resource management professionals with chapters and members around the world. DAMA International is dedicated to advancing the concepts and practices of data and information resource management. Its primary purpose is to promote the understanding, development and practice of managing data and information as key enterprise resources. DAMA International produces premier Symposiums for data and information management professionals in the U.S., the UK and Australia. For more information visit www.dama.org.

Solutions Marketplace
Provided by IndustryBrains

Design Databases with ER/Studio: Free Trial
ER/Studio delivers next-generation data modeling. Multiple, distinct physical models based on a single logical model give you the tools you need to manage complex database environments and critical metadata in an intuitive user interface.

Validate Data at Entry. Free Trial of Web Tools
Protect against fraud, waste and excess marketing costs by cleaning your customer database of inaccurate, incomplete or undeliverable addresses. Add on phone check, name parsing and geo-coding as needed. FREE trial of Data Quality dev tools here.

Speed Databases 2500% - World's Fastest Storage
Faster databases support more concurrent users and handle more simultaneous transactions. Register for FREE whitepaper, Increase Application Performance With Solid State Disk. Texas Memory Systems - makers of the World's Fastest Storage

DeZign for Databases - Database Design Made Easy
Create, design & reverse engineer databases with DeZign for Databases, a database design tool for developers and DBA's with support for Oracle, MySQL, MS SQL, MS Access, DB2, PostgreSQL, InterBase, Firebird, NexusDB, dBase and Pervasive.

Supermicro SuperServers
Custom build your next generation server for a fraction of the cost. SuperServers runs the latest technologies from Intel and AMD.

Click here to advertise in this space


E-mail This Column E-Mail This Column
Printer Friendly Version Printer-Friendly Version
Related Content Related Content
Request Reprints Request Reprints
Advertisement
advertisement
Site Map Terms of Use Privacy Policy
SourceMedia (c) 2006 DM Review and SourceMedia, Inc. All rights reserved.
SourceMedia is an Investcorp company.
Use, duplication, or sale of this service, or data contained herein, is strictly prohibited.