Document the application's platform

An application platform describes the technical architecture in terms of the assembly of local components that a specific application runs on. This assembly is based on a platform template and ideally has standard components incorporated in it.

The local components added to the platform may be based on a standard component or created from scratch. Local components exist only in the context of the application and cannot be reused by other applications.

In the data table, click the navigate Navigate button of the application you want to define. Go to the Technology Context page and open and scroll to the Platform Architecture view and open it.

The application platform is displayed as a matrix. The X-axis shows the platform tiers used to classify components according to their role in a client / server architecture. The following platform tiers are defined:

The Y-axis shows the platform layers that classify components according to their technical abstraction level. The following platform layers are defined:

Define the application's platform. To assemble a platform for the application, add individual components to the platform matrix, structuring the selected platform component by component. Each component you add will be a local component that is used only in the context of this application.

Click in the cell in the platform matrix where you want to add the component and click the 3-dots ThreeDots menu > Create as Copy to create a new local component based on a copy of a standard component. Select a standard component to copy and give the new local component a name, version and start and end dates. Or click the 3-dots  ThreeDots menu > Add to add a local component that is already in the repository to the matrix.

The Components Lifecycle and Used Components views show the local components that are assigned to the appliciation. These local components may be included in the application's platform.