Dragon1 Open EA Method

1. A new view on EA

    2. Dragon1 Introduction

    3. EA in Practice

    4. Way of Thinking

    5. Way of Working

    6. Way of Representing

    7. Way of Supporting















    Dragon1 Open EA Method Official Specification

    Architecture Visualizations

    What is a visualization?

    A visualization is graphic representation of a model or a view of a model. A view is a representation of a model given a certain viewpoint. A viewpoint is a set of issues or concerns of a (type of) stakeholder. A model is a set of related entities.

    A business model for example is therefore actually not a visualization.

    Main Types of Visualization

    Dragon1 Defines different type of visualizations

    • Sketches
    • Diagrams
    • Blueprints
    • Landscapes
    • Artist Impressions
    • Heat maps
    • Roadmaps
    • Scenarios
    • Journeys
    • (Balanced) Score Cards
    • (Strategy) Maps

    In architecture, the architect creates formal and informal visualizations, sometimes of the same subject. This in order to increase the involvement of stakeholders. Looking at a formal BPMN process model or UML Use Case diagram does not trigger a business manager to take action. But an artist impression or design sketch or the problem caused by the current process configuration or systems use case, might just be the trigger for the business manager to take action.

    Objectives of Visualizations

    As an architect is a designer of total concepts and supervisor of the realization of enterprise-wide integral business IT systems, everything he draws are views of a design, requirements, vision, problems, plans. These visualizations are meant to inform, to support decision making, to structure thoughts or to startup thinking and creating common view and understanding. So if you create a visualization that does one of these, the visualization is a success.

    The Difference between a Visualization and an Architecture Visualization

    Not all visualizations you create as an architect are architecture visualizations. A visualization is only an architecture if it shows concepts and or their (concept) principles and the key elements (of the concepts). It could be that the theoretical concept is shown or the applied concepts as a solution is shown, or that a failing or working principle is shown. In all cases we call this an architecture visualization. It could be that the visualization is at conceptual, logical, physical or implementational level.

    Dragon1 Architecture Canvas (Architecture View Layout)

    Dragon1 promotes architecture visualizations to be created using a context containing strategy and transformation, and with that making a visualization more fit to use for decision support.

    The Dragon1 Architecture Canvas has a predefined layout, formerly known as the Architecture View Layout.

    Visualization Framework

    An overview of many common subject/topics where all the types of visualizations can be created for are:

    Industry Organizations Chain / Network Enterprise Organization Domain Area Program Project Market Clients / Customers Stakeholder Governance Business Function Issue Need Decision Requirement Rule Goal Objective Document Activity Identity Mission Vision Priority Initiative Product Process Service Capability Information Information System Application Data Interface IT-Infrastructure Network Storage Cloud Server Client Robot Security Finance Human Capital Service Delivery Concept Principle Pattern Component Standard Technology

    You can create a visualization for one item (like a process or an application) but you can also create a visualization for a subset of or all processes and all applications. This goes for all the subjects/topics above.

    And per subject/topic you can create or generate stakeholder specific views (that filter out any unnecessary data for that stakeholder, focusing the visualizaton on what the stakeholder understands and finds interestering.

    Visualization per Process

    Dragon1 has defined architecture working processes and per process what types of pictures should or could be created (MOSCOW). Below we have listed the most important ones.

    • Line of Sight picture
    • Strategy Map
    • Business Model
    • Business Case
    • Concept Design Sketch
    • Principles Details Diagram
    • Process Landscape
    • Application Landscape
    • Process-Application Dependency Landscape
    • IT Landscape
    • Architecture Vision Poster (Big Picture)
    • Structure Vision Poster
    • (Target) Operating Model Diagram
    • Enterprise (Architecture) Blueprint
    • Governance (Architecture) Blueprint
    • Business (Architecture) Blueprint
    • Process (Architecture) Blueprint
    • Service (Architecture) Blueprint
    • Information (Architecture) Blueprint
    • Application (Architecture) Blueprint
    • Data (Architecture) Blueprint
    • Security (Architecture) Blueprint
    • IT Infrastructure (Architecture) Blueprint / Technology blueprint
    • Architecture Working Processes Poster (maturity level)
    • Concept Design Sketch
    • Agile Projects Overview
    • Technology Roadmap
    • Transformation Roadmap

    Visualizations per Product

    Dragon1 defines architecture products, strategy products and transformation products.

    The Architecture Design Book, the Architecture Glossary Document, the Architecture Principles Document and the Solution Architecture Presentation (PXA) are the most import products in Dragon1. These documents contain various visualizations.

    Dragon1, SaaS platform for Enterprise Architecture.

    The #1 EA Tool

    Create Trial Account

    No credit card required

    Most Viewed

    What's New?

    Featured Content