Resources / Dragon1 Glossary of Terms

Architecture Diagram Definition

Dragon1 Icon for Architecture Diagram

Dragon1 Icon for Architecture Diagram

Dragon1 Definition for Architecture Diagram:

Architecture Diagram Definition Summary

What is a Diagram or Architecture Diagram?

What exactly is diagram meaning? A Dragon1 Term Definition.


On Dragon1 the definition of Architecture Diagram and / or Architectural Diagram is: A graphical representation of the concepts, their principles, elements and components that are part of an architecture.

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

Principle: Separation of Concerns

The above diagram is in this case an architecture diagram, because it show 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 are 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 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 kind of architecture diagrams and maintaining them on Dragon1.

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.

If you have comments or remarks about this Dragon1 term or definition, please mail to