Application Architecture

Dragon1 defines Application Architecture as 1) the total concept of an application landscape and 2) the total application concept of an organization or chain or network of organizations.

Go to the tutorial to design an Applications Architecture landscape.

Types of Application Architecture

As with building architecture, an application architecture consists of a specific type or style when there is a certain concept, principle, or element dominant.

Suppose a hospital has many Windows applications, and all these applications are monolithic (meaning they do not consist of replaceable modules). These two aspects dominate everything and every change. One would say that the hospital's type of application architecture is a Monolithic Win32 enterprise application architecture.

Dragon1 suggests that every organization should be familiar with the reference architectures in its industry or branch, as well as the types of application architecture that best fit its size and ambitions.

Read more about Applications Architecture on Wikipedia.

Overview of Common Application Concepts and Principles

Of course, any organization is unique. That said, every organization uses various application concepts, such as 32-bit Windows and monolithic applications.

Below is a summarization of common application concepts.

Many organizations have these concepts as part of their current and future state application architectures because the IT solution they bought had them embedded.

Common Application Concepts:

Windows 32-bit Application (Win32 App)
Monolithic Application
Three-tier Application

Applications Architecture Example

Below is an example of an applications architecture with domains, concepts, and principles. You can, of course, add other elements to it, like building blocks, standards, etc...

Applications Architecture diagram: Who is providing the applications?

Applications Landscape with AA Principles Projects

The proof of the pudding is in the eating.

With Application Architecture principles, we want to support decision-making and guide innovation projects. Therefore, everything that is not compliant with the principles (required by the strategy) blocks the realization of business goals.

Visualizations of application architectures that show this issue and propose a solution will guide architects working on architecture projects.

Benefits of having a predefined list of application attributes

Having a predefined list of attributes when creating an application landscape on Dragon1 offers several important functions and benefits:

Standardization: Ensures consistent data entry across the organization, making it easier to compare, analyze, and report on applications.
Completeness: Guides users to capture all relevant information about each application, reducing the risk of missing critical details.
Efficiency: Speeds up the data collection process by providing clear fields and options, reducing ambiguity and errors.
Data Quality: Improves accuracy and reliability of the application data, supporting better decision-making.
Integration & Automation: Facilitates integration with other systems, tools, or processes (e.g., compliance checks, lifecycle management) by ensuring data conforms to expected formats and categories.
Better Analysis & Decision-Making: Enables consistent reporting, trend analysis, and impact assessments across the application portfolio.
Governance & Compliance: Supports governance by maintaining a controlled and auditable record of application attributes, ensuring adherence to policies and standards.
Scalability: Provides a scalable framework that can be reused and adapted as the application landscape evolves.

In essence: A predefined attribute list acts as a structured blueprint that makes managing, understanding, and optimizing the application landscape more effective and reliable.

Would you like guidance on selecting specific attributes for your organization or how to structure them?