Application and User Location Mapping: Purpose, Interaction Scenarios, and Architectural Profiles (UML/BPMN EAP & Archimate)

Application and user location maps show the geographic distribution of applications, indicating where end‑users operate the software, where host applications are delivered, and where applications are developed, tested, and released; the analysis can reveal rationalization opportunities, duplication, and gaps, aiming to clearly describe business locations of user interaction and hosting infrastructure.

Determine the number of package instances needed to fully support a geographically dispersed user base.

Estimate the quantity and type of software licenses required.

Assess the level of support users need and the locations of support centers.

Select system‑management tools, structures, and governance for local and remote enterprise users/customers/partners.

Plan technical components such as server capacity and network bandwidth appropriately.

Consider performance when implementing application and technical‑architecture solutions.

Users typically interact with applications in several ways: supporting daily business operations, participating in business processes, obtaining information (searching, reading), 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: geographically defines where enterprise elements are deployed; typically a headquarters plus several sites.

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

Application: may correspond 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: an association with a name, providing role names and cardinalities for each end point.

Archimate

The diagram shows who uses which application on which site.

"Application components" are deployed at locations together with roles or participants (thus representing the occurrence of roles, participants, and application components).

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

Source: http://jiagoushi.pro/node/1246

Discussion: Join the knowledge community "Chief Architect Circle" or the QQ group 11107777 for deeper conversation.