Application and User Location Mapping in Enterprise Architecture

Application and user location maps show the geographic distribution of where applications are used, deployed, developed, tested, and released, helping identify opportunities for rationalization, duplication, and gaps.

Purpose:

Determine the number of package instances needed to fully support geographically distributed user groups.

Estimate the quantity and type of software licenses required.

Assess the level of support needed and the location of support centers.

Select appropriate system management tools and structures for local and remote enterprise users, customers, and partners.

Plan technical components such as server sizing and network bandwidth.

Consider performance when implementing application and technical architecture solutions.

Typical ways users interact with applications include supporting daily business operations, participating in business processes, retrieving information, developing applications, and managing/maintaining applications.

UML/BPMN EAP Profile

Headquarters location: geographically defines where enterprise elements (organizational units, hardware, participants, etc.) are deployed.

Site location: defines the geographic deployment of enterprise elements; typically one headquarters and multiple sites.

Interaction application component: top‑level component managing interaction with external elements, often a GUI such as a web interface.

Application: may refer to legacy applications, off‑the‑shelf products, or assembled application components.

External participant: participants outside the enterprise.

Internal participant: participants belonging to the enterprise.

Association between two classes: includes a name, role names, and cardinalities for each endpoint.

Archimate

This diagram shows who uses which application on which site.

"Application components" are deployed at locations along with roles or participants, indicating the appearance of roles, participants, and application components.

In the example, "Customer" is not localized; a role is used instead of a concrete entity.