Problem solve Get help with specific problems with your technologies, process and projects.

Data architecture vs. information architecture

Learn about the differences between data architecture and information architecture, as well as the relationship between the two.

What is the difference between information architecture and data architecture? We have two environments: IT and IM division. In IT, we have data architecture and in IM we have information architecture -- but there seems to be a conflict in terms of responsibilities. Can you please clarify the differences between the two?

First let's define "data" and "information" -- from that, the delineation between "data architecture" and "information architecture" will become evident. Data are the raw facts about things in our business, e.g. on a sales transaction, what product was sold and how many. Information can be defined as: high quality data + meta data + data context.

More on data architecture

Learn how new BI demands are pushing data architecture limits

Read about how big data architecture adds integration options

See William McKnight discuss relational vs. NoSQL databases in this video

Data architecture is geared toward establishing the data environment for a particular application (e.g. ERP, CRM, Data Warehouse) and includes activities such as data modeling, database design, and data integration design.

Information architecture has more of an enterprise focus and encompasses aspects of data architecture, meta data management, and knowledge management to provide a holistic view of information assets to enable a cohesive platform for delivering information in the correct context to the right people. A key deliverable for an information architecture is the enterprise data model, comprised of a subject area model (SAM), enterprise conceptual data model (ECDM) and enterprise logical data model (ELDM). The enterprise data model is technology and application neutral, and defines how the business sees information.

Information architecture frequently requires development of enterprise taxonomies to organize data (e.g. products) in a hierarchical manner (made more difficult due to the variations between business units) as part of the master data management environment. Ontologies are becoming more common in information architecture to help to determine how to relate things (e.g. vocabulary words) so as to enable technologies such as enterprise search and the semantic Web.

Information is not just found in databases -- it is also found in our knowledge management systems (unstructured data) as well and so must be integrated with structured data to provide a complete picture of enterprise information.

Meta data is the glue that provides linkage between data resources, and provides context to our data in order to turn data into information. Business meta data is particularly crucial to providing understandability to our data, without which assumptions are often made leading to incorrect results ("bad information").

So you can see, there are significant differences between data architecture and information architecture, though there is overlap -- particularly in the realm of conceptual and logical data modeling. Having a good information architecture builds upon the data architecture.

More on data and information architecture


Dig Deeper on Enterprise data architecture best practices