Skip to main content

Modeling a Business Application

In Txture, a Business Application is a key part of the platform's default data model. It is used to represent how an application and its infrastructure connect to the business view. By using Business Applications in Txture, you can streamline the management of applications that are strongly related to each other such as different environments or instances of a Business Application.

Example​

The tree report below shows an example of how a Business Application can be used to group several application assets. In this example, each of the two application instance assets represent a deployment environment of the Business Application "Inventory Control" - a production and a development environment. The transition to the business level takes place via the Business Application.

The report shows the following layers:

  1. Business Application
  2. Application Instance
  3. Business layer with asset types Organizational Unit and Business Capability
  4. Middleware layer including asset types Database and Technical Component
  5. Infrastructure layer

Use cases​

There are several use cases for Business Applications in Txture. In all use cases, the central aspect is the grouping of different application instance assets into a Business Application and, as a result, the simplified management of these application instance assets.

  • Business Applications group related application instance assets.
  • They allow you to set Target Architecture Preferences for all linked application instances.
  • Business Applications link technical infrastructure with business objectives.
  • Properties can be inherited from the Business Application to all linked assets, ensuring consistency.

Grouping Applications with a Business Application​

A Business Application is used to group several assets of the type "Application Instance". This allows you to manage multiple application instances that are connected or work together under one umbrella. For example, if you have several deployment environments each modelled as an individual application instance asset, you can group them in a single Business Application.

Defining Target Architecture Preferences for the Business Application​

One of the key benefits of using a Business Application is that you can set Target Architecture Preferences in the Transformation Cockpit for all the application instances linked to it. These preferences allow you to define how you want your application instances to evolve or migrate in the future, ensuring that all related application instances follow the same architectural strategy.

Linking Infrastructure to Business View​

A Business Application represents the connection between the technical infrastructure and the business perspective. By grouping application instances within a Business Application, you can align infrastructure decisions with business priorities, making it easier to understand how technical changes impact the business and vice versa.

Inheriting Properties Automatically​

Another useful feature of Business Applications is the ability to automatically inherit properties using Propagation Rules from the Business Application to the linked application instance assets. This is especially helpful for properties that have the same value across all related application instances. For example, if all application instances under a Business Application share the same Technology or Programming Languages, these properties can be inherited automatically, reducing the need for manual updates.