Step-by-Step Guide to Creating Enterprise Architecture Products with the Dragon1 Open EA Method
This article provides a comprehensive, step-by-step tutorial for designing and visualizing enterprise architecture products using the Dragon1 Open EA method, covering conceptual design, preliminary design, and archival documentation to help practitioners create effective, interactive architecture artifacts.
Enterprise architecture is a complete science and profession, yet it remains a young field that is new to most people; the following step‑by‑step tutorial lists the procedures for creating effective, visual, and interactive architecture products.
When you are busy, enterprise architecture still needs attention.
In your work you may wonder how to create certain enterprise‑architecture products or execute specific architecture processes; the resources on this site guide you through the steps that conform to the Dragon1 Open EA method for Visual Enterprise Architecture.
Your step‑by‑step tutorial
Each page presents a series of steps to design useful architecture products according to the ideal/normal order of the Dragon1 Open EA method.
A) Enterprise Architecture – Conceptual Architecture Design
The following products belong to the first stage of architecture design applications:
How to create stakeholder needs and requirements analysis diagrams (stakeholder enterprise vision)
How to create enterprise structure element and function diagrams (enterprise structure vision)
How to create enterprise architecture function, concept, and principle diagrams (enterprise architecture vision)
How to create ArchiMate business function diagrams
How to create design sketches of the overall enterprise concept
B) Enterprise Architecture – Preliminary Architecture Design
The following products belong to the second stage of architecture design applications:
How to create a detailed principle diagram of a concept
How to create meta‑model, user model, and instance model
How to create a horizontal process diagram (with business functions)
How to create an application landscape diagram (static and dynamic), including domains, information systems, suites, modules, components, objects, interfaces, connections, software, and services
How to create a technical (service) roadmap
How to create an AS‑IS enterprise architecture blueprint
How to set up AS‑IS architecture principle documentation/database
C) Enterprise Architecture Archive
The following products are part of the enterprise architecture archive:
How to set up EA baseline
How to create AS‑IS enterprise architecture framework diagram
How to set up a glossary for terminology documentation/database
How to create AS‑IS enterprise architecture documents
How to create AS‑IS governance architecture documents
How to create AS‑IS business architecture documents
How to create AS‑IS information architecture documents
How to create AS‑IS technical architecture documents
How to create AS‑IS security architecture documents
By following these tutorials you will cover the processes, products, checklists, document templates, and other practical content of the Dragon1 Open EA method.
Reading
The purpose of the step‑by‑step tutorial is to spark your interest in designing architecture products, after which you can decide to follow a training course or create a free Dragon1 account. If you are interested in architecture design, you may also want to read:
Terms > Architecture Framework Definition
Software > Enterprise Architecture Tool
Software > ArchiMate Tool
Software > BPM Tool
Examples > Application Landscape Diagram
Examples > Process Landscape Diagram
Examples > IT Landscape Diagram
Examples > IT Infrastructure Enterprise Blueprint
Getting Started
If you want to create your own architecture diagram, you can use Dragon1 PRO to create these architecture products.
Architects Research Society
A daily treasure trove for architects, expanding your view and depth. We share enterprise, business, application, data, technology, and security architecture, discuss frameworks, planning, governance, standards, and implementation, and explore emerging styles such as microservices, event‑driven, micro‑frontend, big data, data warehousing, IoT, and AI architecture.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.