Dragon1 EA Method















    Architecture Diagram Definition

    Dragon1 Icon for Architecture Diagram
    Dragon1 Icon for Architecture Diagram
    CREATED BY ANONYMOUS, CREATIVE COMMONS LICENSE

    Dragon1 Definition for Architecture Diagram:
    An architecture diagram is a graphical representation of a set of concepts, that are part of an architecture, including their principles, elements and components.

    Architecture Diagram Definition Summary

    What is a diagram? The Dragon1 open EA Method makes it very clear: if a diagram does not show a concept, principle or part of a principle, it is NOT an architecture diagram, because it does not show (a part of) architecture.

    dragon1 architecture diagram Example Architecture Diagram of an Enterprise Architecture to create a Modern Smart and Green Company, using various concepts and principles.

    Watch the interactive Architecture Diagram

    Levels of Abstractions

    Architecture is a coherent set of concepts for a structure. These concepts are often visualized at four levels of abstraction. These are:

    • Conceptual Level - showing an overview of concepts
    • Logical Level - showing a logical design of one or more concepts, containing at least the key elements of concepts and showing the principles of the concepts (i.e. how the concepts work).
    • Physcial Level - showing a component design depicting the elements
    • Implementational Level - showing the vendors and products with which the components will be implemented.

    The first picture on this page is a logical level architecture diagram. Most often architecture diagram contains a combination of logical and physical aspects, meaning that logical elements and physical components are used randomly by each other. The Dragon1 open EA method suggests to either separate these levels of abstraction in various diagrams or to be very clear which shapes show an element and which show a component.

    The next picture on this page is a logical level architecture diagram of an application landscape.

    Visualizing a Principle: Separation of Concerns

    Using a logical level architecture diagram of an application landscape
    dragon1 logical level architecture diagram Example Logical Level Architecture Diagram of an Application Landscape, showing the concept of Front-, Mid and Back Office.

    The above diagram is, in this case, a logical architecture diagram, because it shows the offices concept used in the organization:

    • Front Office
    • Mid Office
    • Back Office

    The principle of the Office concept is: By separating concerns with regards to software applications in front office, mid office and back office, the applications for these three domains can be integrated and focused much better on their task.

    Front office applications are applications that deal with client data and often need to be updated much more frequently than back-office applications. So placing all these applications together makes it easier to integrate and deduplicate them.

    This is also the case with Mid Office and Back Office applications. Back office application is often transaction processing applications that are hardly updated every month with new functionality. Also, the application platforms and the sizing of their infrastructure are significantly different from front office applications.

    Grouping application logically and or physically in front, mid and back office will cause you as an organization to make better use of the applications.

    This specific architecture diagram helps CxOs, managers and architects to make decisions like deduplication of application modules, replacing, merging, integrating and phasing out applications. The result of this work is that the organizations' application landscape will comply better with the enterprise strategy and the return on IT investments (how well you make you use of the IT-equipment you bought), will be higher.

    So every organization benefits from creating these kinds of architecture diagrams and maintaining them on Dragon1.

    Chatbot Architecture Diagram

    The next picture is a physical level architecture diagram, as it show some components part of the Chatbot concept and the coherence between these components (the chatbot concept) is made very clear.

    dragon1 physical level architecture diagram Example Physical Level Architecture Diagram of a Chatbot.

    This diagram does not show all components of the Chatbot concept, but it focuses on the feature of image moderation. It shows how always every image is scanned for explicit content and deleted accordingly.

    Also Read

    You might also want to read:

    Subscribe for Trial Account

    If you are curious of how you can create easily architecture diagrams by yourself, you can create a Free Trial Account here for working with Dragon1.

    Dragon1 December Deal


    If you have comments or remarks about this Dragon1 term or definition, please mail to specs@dragon1.com.