How to start an enterprise architecture program?

Who uses an Enterprise Architecture?


Where to begin? 

The most important part of starting an enterprise architecture is establishing the right sponsorship to insure its successful development and deployment. All potential users (see an example of personas to the right) of the applications and systems derived from the architecture must be involved in the process. Without both management sponsorship and near-universal involvement, enterprise architecture projects usually fail.

 Here is a short checklist of what you need to look for:

  • Every enterprise has an architecture, however, it is usually undocumented and the
    elements are inconsistent.

  • Most likely some of the architectural elements are in strategic and performance plans.

  • Look at published and unpublished policies and procedures, and system documentation.

  • There are also a lot of enterprise architecture elements, particularly business rules, that are embedded in software application code.

  •  Still, more exist only as employee "tribal knowledge.
Zachman Framework Image


Screen Shot 2021-12-06 at 7-31-56 PM-png

Transition to an Enterprise operating model.

How is this supported?

Your Enterprise Architecture serves as a map of all the linkages among business initiatives, data required to support those initiatives, business processes that use the data, and physical information systems that support data requirements and processes.

By signing up for a free 30-day trial, not only will you be able to construct the architecture, you will also be able to instantiate its operational model. Using the trial, you are able to:

  • Create an Enterprise Operational model.
  • Link to an Enterprise Strategy
  • Link Strategy to Value-based Outcomes
  • Create Workflows based on Capabilities
  • Build linkages to Implementations

Hands-On Tutorial 

Includes important step-by-step information on how to set up your Enterprise Architecture (EA).

 The tutorial contains step-by-step instructions on how to map different types of artifacts, assets, statements and lists to specific cells of the EA framework. Each cell of the framework is described as follows:

  • Cell location, label, perspective, and descriptive type.
  • An explanation of the cell definition
  • The artifact created in the project to implement.
  • The name and location of the cell included in the artifact 
  • A detailed explanation of the project artifact
  • Alternative artifacts that could be created in the project to implement the cell.