Modeling: Application vs. IT component

📘

Important Information

This page is a modeling guideline for Meta Model v3. Updated guidelines for Meta Model v4 is available in the documentation.

To model your architecture correctly in LeanIX, it is crucial to have a clear definition and understanding of the terms "Application" and "IT Component". First of all, please consider your software stack. The following picture shows examples of what we consider to be Applications and IT Components.

1900

For the first column you can see e.g. enterprise suites and ERP systems as examples. These are classic applications and, of course, also in LeanIX they are modelled as applications. In the row for the IT Component you find for example your system software, technology services or hardware (e.g. operating systems, databases, run-time environments, laptops, desktop computers and other devices). They are clearly IT Components in LeanIX. It becomes more difficult for application platforms or tools such as robotic process/test automation tools or BI software. They can be considered either applications or IT Components, depending on their usage.

The image below outlines the characteristics of an application within the context of LeanIX:

1954

An IT Component, on the other hand, would have the following characteristics:

1904

Try to use the above definitions to define whether your application platform/tool is an application or an IT Component. In the following graphic, you will find some more best practices on how to model applications and IT Components.

1989

The following example can also help illustrate whether a piece of software should be considered an Application in your landscape:
When quotes for customers are built using a macro within a spreadsheet called "Quoting Tool", then the quoting tool itself (the macro) is the Application rather than the spreadsheet software, which would be considered a Software Component.

In case you have further questions regarding modelling, please also take a look at this webinar presentation, which provides an overview of mapping your organization's infrastructure in the LeanIX Meta-Model, including many real-life examples (e.g. SAP, cloud environments and enterprise suites such as Microsoft Dynamics).