Home > Ask the Data management / BI Experts > Data architecture / Data modeling Questions & Answers > XML schema definition versus conceptual data model
Ask The Data Management Expert: Questions & Answers
EMAIL THIS

XML schema definition versus conceptual data model

Pete Stiglich EXPERT RESPONSE FROM: Pete Stiglich

Pose a Question
Other Data Management Categories
Meet all Data Management Experts
Become an Expert for this site


Tips, expert advice and sample chapters
Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us    Add to Google


>
QUESTION POSED ON: 20 May 2008
We write software for complex engineering systems. The engineering design needs to be complete at every level of maturity. The devices are naturally hierarchical, from parts to components to systems. Missing items lead to very poor and often the wrong designs. For this reason, I prefer using XML schema definition that expresses strict hierarchical relationships immediately, without a conceptual data model. We do draw diagrams, but they are drawn in Visio or by engineering simulation programs.

I am trying to explain the use of XML schema definition versus the use of a conceptual data model to our software person who has an enterprise software background. Could you help me articulate my view?



Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us    Add to Google



RELATED CONTENT
Data architecture / Data modeling
Data architect vs. application architect: Segregate the duties
Enterprise versus project level conceptual data modeling
Data model conversion: Conceptual design to logical design using an ER model
Four guidelines for enterprise conceptual data model (ECDM) entity selection
Data modeling for data warehouse projects
Data architecture vs. information architecture
What are the benefits of a conceptual data model?

Data modeling tools and techniques
Understanding five major enterprise information management benefits
Data modeling concepts: How settings can increase application success
Advantages and disadvantages of XML shredding
How to shred XML with the DB2 XMLTABLE function
Shredding XML docs into relational tables with annotated XML schemas
Examples of single and bulk XML shredding of XML documents
Improving ODBC application performance and coding
How to capture metadata information, ETL rules with CA Erwin Data Modeler
Data Warehouse Platforms Product Directory
Data models serve as blueprint for business intelligence, master data management projects

RELATED GLOSSARY TERMS
Terms from Whatis.com − the technology online dictionary
data modeling  (SearchDataManagement.com)
predictive modeling  (SearchDataManagement.com)

RELATED RESOURCES
2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems
Search Bitpipe.com for the latest white papers and business webcasts
Whatis.com, the online computer dictionary


Both XML Schema Definition (XSD) and a Conceptual Data Model (CDM) can express strict hierarchical relationships. However, XML Schema is meant to describe an XML document while a conceptual data model is meant to describe business objects and how these relate – it is a business model from a "data" point of view (for the CDM, actual data does not have to exist). It is technology and application neutral. A CDM usually takes the form of an Entity Relationship Diagram (ERD) but a Unified Modeling Language (UML) class diagram could be used as well for expressing constraints which an ERD might not be as capable of.

In addition, the CDM is not intended to be a design document (it's for understanding the business before a solution is designed) and so will not have all the gory details needed for implementing any data-related system.

One thing that an XML Schema Definition cannot express (easily) is a many-to-many relationship given its hierarchical nature. XSD itself is an XML document, not a model and so the relationships aren't as easy to identify due to the variable structure of the doc, e.g. lines may or may not be proporly indented. Even showing a well formed XSD to a business person or even to most technologists will be an invitation for glossy eyed incomprehension. Also, importantly, many-to-many relationships can be expressed easily in a CDM - this is important because parts may be used for many components, and a component has many parts, etc. Below is a sample CDM demonstrating parts explosions, which may or may not be applicable to your business.

Conceptual Data Model

The above CDM helps to visualize the parts explosion and has business rules (relationships) which are documented in business terms so that the business can immediately validate or point out the correct relationship easily. The Inclusive OR relationships indicates a Component (for example) may be comprised of both many (per crows feet notation) Parts and many sub Components (per recursive many to many relationship of Component to itself). As the saying goes "a picture is worth a thousand words".

The CDM should be developed before the XSD to ensure that your XSD is aligned with the business.

More about conceptual data models

More about XML




Search and Browse the Expert Answer Center
Search and browse more than 25,000 question and answer pairs from more than 250 TechTarget industry experts.
Browse our Expert Advice

About Us  |  Contact Us  |  For Advertisers  |  For Business Partners  |  Site Index  |  RSS
SEARCH 
TechTarget provides technology professionals with the information they need to perform their jobs - from developing strategy, to making cost-effective purchase decisions and managing their organizations' technology projects - with its network of technology-specific websites, events and online magazines.

TechTarget Corporate Web Site  |  Media Kits  |  Site Map




All Rights Reserved, Copyright 2005 - 2009, TechTarget | Read our Privacy Policy
  TechTarget - The IT Media ROI Experts