How to Create an Enterprise Architecture Framework Diagram

What is an Enterprise Architecture Framework?

enterprise architecture framework management report

Using an Enterprise Architecture Framework as a Management Report.

Get insight and overview in your EA documentation

On the Dragon1 platform, you can generate or create manually 100% data-driven Enterprise Architecture Framework diagrams to get insights and overviews in the documentation of the architectures.

This page will inform you how to do that in about 19 steps.

The following questions are answered in this tutorial: 'Why should you start creating an Enterprise Architecture Framework?', 'What steps do you need to take to create an EA Framework, and 'What should the result of an EA Diagram look like'?

An EA Framework Definition

An Enterprise Architecture Framework, in its smallest form, is a classification scheme of types of architectures and their most important parts in a single schematic overview.

Dragon1 has defined an Enterprise Architecture Framework as follows:

An Enterprise Architecture Framework is a basic structure (like a method) grouping types of architectures that are filled with a set of key parts and tools, such as capabilities, concepts, principles, objects, reference models and view types, which can be used for documenting architectures efficiently and effectively and developing a broad range of different architectures and solutions as part of enterprise architecture.

An Enterprise Architecture Framework can often be visualized in a reasonably small but comprehensive diagram. Often, you will want to create separate diagrams or views for the various architecture plateaus (AS-IS, Plateau n, TO-BE, Envision).

Why create an EA Framework?

As an Enterprise Architect, one of your primary tasks is and should be creating AS-IS and TO-BE Architecture Framework diagrams for several types of architectures, starting with the one for Enterprise Architecture.

The diagram reveals to everyone which architectures are defined and recognized as part of the current state and future state architecture that is defined and present, but also which ones are not (yet) defined and recognized in the organization.

This is important to understand and know for the project and suppliers. For instance, if there is no definition or recognition for business architecture or data architecture in an organization, it is hard to coordinate suppliers and projects if they are implementing or changing parts of the business architecture and data architecture.

Architecture Framework States: AS-IS and TO-BE

The TO-BE version (often the ideal situation) of an Enterprise Architecture Framework is more complex and harder to create than the AS-IS version (often the realistic situation) since it requires new visions, missions, and strategic decisions. It (the TO-BE) also had a delayed effect.

The AS-IS impacts today, even if you have not created the enterprise architecture framework yet. The sooner you introduce definitions and a list of key parts and tools per architecture, the better you can manage projects and suppliers

Therefore, it is always useful to visualize the AS-IS framework and reuse the current (old) strategy aspects to create the diagram.

The available TO-BE and AS-IS architecture diagrams are extremely helpful in supporting high-level overview and decision support.

It is just sitting there, waiting for you to dust it off!

Enterprise Architecture Frameworks show the types of architectures used at a certain time, and it shows the concepts, principles, standards (norms), building blocks, metamodels, and user models that are part of the underlying architectures.

As an enterprise architect, you can decide which parts of the architecture should be part of the framework.

The below view of the framework diagram shows only the recognized architectures. This is a valuable diagram for the organization and is bound to facilitate many discussions.

Enterprise Architecture Framework Diagram.

Dragon1 Viewer

Excel Sheet

Data Manager

Quick Start: Download Excel Sheet

A quick start in creating your own EA Framework diagram would be to download the Excel sheet presented at the top of the page.
Next, you open it in Excel and start editing it, for example, the names of the architecture domains in the Tab Architectures.
Next, go to the Dragon1 Viewer, click the Data Upload button, and upload the Excel Sheet.
Dragon1 generates your version of the EA Framework Diagram.

Steps in creating an Enterprise Architecture Framework diagram

An overview of the steps to take in this enterprise architecture tutorial how to create an Enterprise Architecture Framework is here below.

We use mainly three applications on the Dragon1 platform: The Workplace, Viewer, and Data Manager.

We will use

The Viewer in 2 modes: the viewer mode and the edit mode.

19 Steps

Login
Go to the login application (www.dragon1.com/login) and login with a valid account.
Create Atlas
Go to the Data Manager application (www.dragon1.com/datamanager) and select the entity class Atlases. Next, click on the Add button. Provide an Atlas name and Click Save & Close.
Add Atlas Folder
Select the entity class AtlasFolders. Next, click on the Add button. Provide an Atlas Folder name and select the atlas of which this folder is part. Click Save & Close.
Add Atlas Page
Select the entity class AtlasPages. Next, click on the Add button. Provide an Atlas Page name, select the atlas this page is part of, and click Save & Close.
Create Visualization
Go to the Data Manager application. Select the entity class Visualizations. Click Add. Provide values for the following attributes:
- Provide a Name for the visualization
- Select the Template. Use Enterprise_Architecture_Framework
- Provide a Layout String. Use L04_C01_C01_C01_C01_F01_B01
- Provide a Layout Ext String. Use s00_s00_s00_s00_s02_s02_s00
- Provide a value for Action Script to generate a Legend: generateLegend();
- Provide Group value. A list of comma-separated architecture names: Enterprise Architecture, Business Architecture, etc...
You can also choose to draw areas instead of them generated in a layout. See later steps.
Link Atlas Page to Visualization
You need to link the visualization to the atlas page.

Edit the created Visualization. Select an Atlas page entity in the Atlas Pages Link field, and click Close & Save.
Enter Architectures as Data
Go to the Data Manager application. Select the entity class Architectures. Click Add. Provide a name for the architecture. Also, enter data for the owner and current status of the architecture and a user-defined field Deadline when the documentation should be completed.
Repeat this step for every architecture.

Optionally, you now place reference values in the visualization group names: ref=architecture,1,name. etc...
Enter Data Parts for the Architectures
Go to the Data Manager application. Select the entity class Concepts. Click Add. Provide per entity the following attributes:
- A name for the concept.
- Provide the name of the architecture it belongs to in the group field.
- Provide status and owner for the concept.
Place the value Reference in the type field. Add two user-defined fields, Total and Count, and provide in Count the number of items that can or should be documented. The total will hold the calculated number of items.

Repeat this step for all the parts of the architectures (capability, principle, standard, object, component, model, view, etc..)
Add Management Overview
Go to the Data Manager application. Select the entity class Views. Configure the action script to give colors to the architectures and parts based on how well they are documented.
Add Undocumented View
Do the same here. Configure the action script to show only the undocumented parts of the architectures.
Add Current State View
Go to the Data Manager application. Select the Views entity class. Click Add. Provide a name for the view. Configure the action script to show only the architectures and parts for the current state.
Add Future State View
Do the same here. Configure the action script to show only the architectures and parts for the future state.
Add Documented View
Do the same here. Configure the action script to show only the documented parts of the architectures.
Add Undocumented View
Do the same here. Configure the action script to show only the undocumented parts of the architectures.
Add Ownership View
Do the same here. Configure the action script to show a label on top of the architectures and parts with the names of the owners of the parts.
Add Areas
Go to the Viewer (www.dragon1.com/viewer). Open the correct atlas and click on the page for the correct visualization. Set the Viewer in edit mode. Drag 4, 5, or 6 areas from the icons panel onto the canvas. Please give them the names of the architectures. Do the same for creating sub-architectures in the architectures. Optionally, configure the architecture icon for the area.

Do not forget to save the diagram.
View the in-between result
Go to the Viewer (www.dragon1.com/viewer), select your atlas, and click on the page for your visualization.

You should see an empty diagram with your architectures and key parts inside the architecture. The diagram is not yet populated with the actual data.
Enter Documented Data
It is time to enter or provide the real documented data.

You can choose to define a JSON data source or enter or import all the data into the Dragon1 repository.

If you want to enter or import the documented data, you use the data manager or import application.
Enter Data Sources

To define a JSON data source for the EAF Diagram, do this in the visualization object.

Go to the data manager, open the visualization object, add a field called Data Source 1, and provide the JSON file or rest API link (that returns a JSON file). You can provide multiple Data Sources in this way.

Add a user-defined field called Data Source Classes 1 for every data source. Add a comma-separated field for the classes that are in the file or data stream.

If a data source holds multiple classes or multiple architectures, Dragon1 tries to find a class, type, or parts field/attribute (for the class) and a tag, architecture, or group field (for the architecture).

Add the following action script with the visualization: countFrameworkItems();. This function will look into the entered data or data sources and try to count the number of items per category. The count result will be stored in the Totals user-defined field with the reference items.

If you have done the above steps, you will have created your EAF diagram.

Extra Steps: Drill Down and Generate Sub Diagrams

Here, follow the extra steps to drill down into the diagram or to generate sub-diagrams.

Add Action Script with the Reference Items
Go to the Data Manager and open each entity or object you created with type value Reference.
Place the following action script with each entity: generateClassDiagram(domain);

Upon clicking on a reference entity in the diagram, a class diagram is automatically generated and shown. The items are grouped on the domain attribute. You can also use another attribute if you like.
Add Action Script: Show Class List
You can also add action script: showClassList(domains);

Upon clicking a reference entity, you will get a details list to the left.

List of common architectures

A list of common architectures to document for an organization are: enterprise, business, data, application, security, HR, information, service, process, interface, and technology (or IT infrastructure).

List of common key parts and tools

A list of common key parts and tools to document with an architecture are: capabilities, concepts, elements, principles, rules, standards, objects, components, design patterns, building blocks, reference models, documents, reports, actual models, diagram types and actual diagrams, view types, and actual views.

Management Project Steps

Creating an EAF diagram is more than creating or generating one. It also involves stakeholder engagement. The steps for this are described below.

Show an example EAF diagram to the owner/client (the CIO).
Get the assignment to create an EAF diagram and make sure it is clear who is going to approve the EAF diagram and who is going to use the EAF diagram for what purpose.
Make a list of candidate architectures and describe the enterprise architecture function: the common architectures people talk about in your organization. Look at your organization's structures, systems, domains, and functions. Are there already architectures defined for them?
Check if there is an architecture for a structure, system, or domain if concepts and principles are applied and if policies, rules, and standards are applied for that structure, system, or domain.
Try to find a reference model for the common framework for your industry.
Review your list with others to verify the actual status of the architectures.
Try to get a common definition for the architecture (to define its content, context, and scope); who is the owner, manager, and user?
List 7 issues for the architecture.
List 7 products of each architecture to create or have. With these products, the owner and enterprise architect of an architecture can direct developments and realizations.
Select the entities for your architecture framework model from your company's enterprise meta-model of an architecture modeling language.
Create the enterprise architecture framework model.
Create a management overview of the Enterprise Architecture Framework model.
Be sure you are not visualizing the perfect world (figure 1) but the current actual situation (figure 2). It could well be that your organization holds two different business architectures and technical architectures. That all depends, of course, on your definition of architecture.
Visualize in a diagram the management overview of the Enterprise Architecture Framework model.
Write down in a document why, when, and how you created the diagram and how it should be maintained.
Present it to the owner/client and have the EAF diagram approved and used.
Make the diagram part of the maintenance update cycle for architecture products.

The benefits of using an Enterprise Architecture Framework

Enterprise Architecture Framework Diagram Parts.

The benefit of modeling and visualizing the AS-IS Enterprise Architecture Framework is that you, as an architect:

to be able to analyze the impact of change on architectures and measure compliance to reference architectures better
to be able to communicate the current situation and implementation of architectures better to users and stakeholders
to be able to manage expectations better of what architectures are present and what is not to users and stakeholders
to be able to manage the workload to create and maintain the architectures and their products
to be able to focus discussions about the what, why, and where of architectures

Usage of this Enterprise Architecture Framework

Enterprise Architecture Framework Diagram Realistic.

On Dragon1, enterprise architects need to get the assignment to create a product, such as an AS-IS Enterprise Architecture Framework. To get that assignment from the owner/client (CIO preferably), you will need an example EAF diagram.

That example you could create without an assignment, and you can prepare a case or situation to depict so you can show the benefits of having such an EAF diagram available (when does it come in handy). What are questions people have, what are issues and problems regarding consisting architectures, and how does this diagram help to solve them?

An AS-IS Enterprise Architecture Framework is one of the first products to create as part of your Enterprise Architecture Baseline

Management Report Views

Enterprise Architecture Framework Diagram Management Report View.

With an Enterprise Architecture Framework, you can do a lot of reporting, such as using colors, how well the architectures are designed and implemented, or how well they comply with certain standards. If created correctly, it can act perfectly as an auditing framework.

Suppose you could use the color red to say a part of the architecture in the current situation is not implemented and not compliant with the company's strategy and policies. You can use the color orange for the partially compliant parts and the color green for those fully compliant. And black means you could not get the status, and white means getting the status has not been done or planned.

A typical management report view of the enterprise architecture framework like this will often cause an owner/client (CIO) to take immediate action.

About Architecture Diagrams

An Enterprise Architecture Framework diagram is a special type of Enterprise Architecture Diagram. A diagram is only an architecture diagram when it contains information about concepts that create or are part of an architecture together. An architecture diagram is a conceptual structure diagram.

If a diagram omits the conceptual layer and only shows elements of the logical layer, it is not considered anymore an architecture diagram but a logical structure diagram. If a diagram only shows the components and objects of the physical layer, the diagram is considered a physical structure diagram. The conceptual, logical, and physical layers in diagrams are often mixed up.

Dragon1 advises always to focus on a layer in an architecture diagram or at least to complete one layer in one diagram (the diagram shows the complete logical layer, etc..).

Get Started

We hope we have inspired you to Get Started creating enterprise architecture frameworks.

Do you want to use your company data? You can purchase your Dragon1 PRO here online via the Store.

If you do not have the time and you need an Enterprise Architecture Framework on short notice, we can Create a Framework for you.