Home > Articles > Software Development & Management

Putting the "I" Back in IT Planning

Jane Carbone looks at how to create the often-missing link between enterprise architecture and data modeling, through this list of nine "Dos and Don'ts."
Like this article? We recommend

Like this article? We recommend

Putting the "I" Back in IT Planning

In "How Did IT Get this Way?" DMReview (March, 2002) Rob Seiner says:

"If your company doesn't have any problems managing its information assets, this test is not for you. Okay. That should have eliminated...nobody."

Sadly, I agree with Rob. Nonetheless, perhaps twenty years ago, this situation (every company having problems managing information) would have been less disturbing. While many factors contribute to creating these problems, lack of planning or "dis-integrated" planning is a key factor. As a friend says, "we don't plan to fail, we fail to plan." Some examples of planning failures that we continue to see in our practice are:

  • A lack of formal, enterprise-wide IT planning (architecture) or unrelated pockets of planning

  • Data/information planning isolated from the "real" IT architecture (i.e., the technology architecture)

  • The terms "data architecture" and "data model" used inter-changeably;

  • The data model constructed before or without (reference to) the enterprise architecture

  • The data management organization viewed as a group of eccentrics who aren't nearly as vital to IT as the developers and data base administrators, or worse—viewed as a roadblock.

Like many, I began my IT career as a programmer, and moved "up" to design, then analysis, all at the project level. Then, listening to James Martin, I was "awakened." It took a few un-sought job "opportunities" before I fully understood the value and the business benefits of integrated IT planning at the enterprise level—not the least of which is planning for the business data. Even now, when the criticality of data to the business is almost universally understood, many organizations resist using IT resources to develop an architecture that goes beyond technology. In the past couple of years, I have seen an intensified interest in attendees of our architecture seminars in more broad-based architecture, especially when mergers and consolidations virtually require it. I believe we can leverage this interest to begin to make some profound changes in the process—or lack thereof—that we use to create plans for IT. Data and the data manager play a vital translation role in this process.

I have recently been reminded of how apt is the comparison of IT to building a house. I learned first-hand that what you plan formally is more likely to happen, that what you include in the plan is most likely to be executed and that what you omit—like an extra closet—will likely not see the light of day. I was reminded also that key to a successful outcome is the ability to translate intent from the client to the architect, through the builder and to the implementers who execute the plan (electrician, plumber, etc.). In the instance to which I refer, the builder's outstanding ability to translate the architect's plan into directions for the implementers resulted in tremendous success.

In our workplace organizations, the business client, the architect, the data manager and the developers often need to forge stronger relationships and call on their translation skills. To create better, integrated IT plans, we identify and implement process modifications. Working within better-defined processes, our

IT professionals can have a profound impact on the quality of IT implementations, and ultimately on the organization's success.

In our practice, we call the broad-based, enterprise-wide integrated IT plan the "Enterprise Information Architecture" (EIA)*. Presented here is one of the approaches we use to begin to close some of the gaps in the IT planning process. Specifically, we look at how to create the often-missing link between enterprise architecture and data modeling. Here's how the two views line up:

Enterprise Architecture Model

Data Model

Business View of IT

Strategic View

Planning Phase

Relationship of Data to Business Functions, External

Interfaces, Services,


Key Data Interactions, Capture and Storage


IT View of Business

Logical View

Analysis Phase

Relationship of data to other data

Data Structure


When the gaps between the two views are not bridged, the result may be technically excellent but useless outputs. For example, in one organization, when we developed the target architecture required to support a new business direction, it was an almost impossible task to persuade the data team to "reverse engineer" the enterprise data model. In another organization, we urged the decision-makers not to purchase an external data model before we defined the target architecture. Neither of these situations was likely to produce the sort of high-quality business data on which organizations today rely.

* "where "enterprise" means all parts of the company, business unit, agency or organization. "Information" means all the data required to run the enterprise and includes the functions, the technology and the people that create, access, use or transform that data into information and ultimately, knowledge. "Architecture" refers to the set of plans that describes how all parts of the IT infrastructure need to behave to support the enterprise needs and goals."

** "...the one-page entity-relationship model that describes the relationship of each set of subject data included in the architecture model to every other set."

Our experiences—the good, the painful and the almost terminally ugly—have led us to devise and use some very practical approaches for creating the necessary linkages and closing the gaps. In the nine "Dos and Don'ts" that follow, the architect and the data manager play key process roles in creating linkages through translation.

  1. Do include key information "subject areas" and business functions in your target IT architecture. If your "architecture" is simply a technology plan, throw it away and start over. The plan needs to include the data, function and technology components of the business and how they are related. Architecture modeling is one of the best ways to portray the relationships. The architecture model should include the data architecture—by identifying target operational data stores, data warehouses, data marts and reference data.

  2. Do use business language in the architecture models. The architect plays a critical role in the translation of business needs to IT architecture. If the business calls them "clients" don't refer to them as "customers" in the architecture. There is plenty of time to precisely name objects in the detailed logical data models.

  3. Do get business and IT concurrence on the architecture before you proceed any further. This tests the accuracy of your translation. Any lack of time spent here is sure to cost you greatly in later steps.

  4. Do use the architecture model as the basis for developing a conceptual data model.** The data analyst plays a critical role in the translation from architecture model to data model. This requires the data analyst to identify large, conceptual data subject areas referenced in the lowest level target state architecture models. These data areas are translated to provide an initial set of conceptual "mega-entities". The data analyst edits the mega-entities by adding or dividing where big, obvious gaps exist.

  5. Do include business policies in the conceptual data model—those very high-level written statements or guidelines that describe how the business wants to operate on the information. Don't try to get "atomic" or pin down "rules" yet.

  6. Do set a few, key standards—names and definitions for the mega-entities. Since a conceptual data model should fit on one page, there should only be a few, not many, entities that require standards, and these should be the basic information blocks of the organization, e.g., Customer, Product, Employee. These will be the basis for more detailed modeling and development.

  7. Do get concurrence from the architect and the business on the conceptual data model before you build anything new. If possible, do use the same participants who reviewed the architecture model. In a couple of cases, I found marketing and operations leaders who were eager to participate in both reviews. If this group doesn't understand the conceptual data model, then it is not conceptual or it is not an accurate translation.

  8. Do consider "just in time" logical modeling as you go forward—developing detailed logical data models only for new, large funded projects that comply with the target architecture.

  9. Do publish and update. Even the most excellent plans, if "secret" or static, are useless. Make sure the architecture models and the data models are available to the business and IT—architects, analysts, designers and developers—through the intranet, repositories and open forums.

This is a fairly simple, but not necessarily easy, process to execute. You are likely to meet resistance, which is why the concurrence steps are so important—and often, so time consuming. But having undertaken these steps, you will have put in place key linkages required to accurately translate the business requirements to architecture, to translate the architecture to data models, and to use the data models to provide direction and guidance for on-target code and business data implementations. By following this process, you will contribute heavily, not only to the elimination of problems managing information, but also to the delivery of IT components that actually meet the business goals—and that, hopefully, is why we are getting paid.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020