Application and user location diagrams

The application and user location diagram shows the geographical distribution of applications. It can be used to show where applications are used by the end users; the distribution of where the host application is executed and/or delivered in client scenarios; the distribution of where applications are developed, tested, and released, and so on. Analysis can reveal opportunities for rationalization, as well as duplication and/or gaps. The purpose of this diagram is to clearly depict the business locations from which business users typically interact with applications, but also the hosting location of the application infrastructure.


The diagram enables:

  • Identification of the number of package instances needed to sufficiently support the user population, which may be spread out geographically.
  • Estimation of the number and type of user licenses for the package or other software.
  • Estimation of the level of support needed for the users and location of support center.
  • Selection of the system management tools, structure and management system required to support enterprise users/customers/partners, both locally and remotely.
  • Appropriate planning for the technological components of the business, namely server sizing and network bandwidth, and so on.
  • Performance considerations when implementing application and technology architecture solutions.

Users typically interact with applications in a variety of ways, for example:

  • To support the operations of the day-to-day business.
  • To participate in the execution of a business process.
  • To access information (look-up, read).
  • To develop the application.
  • To administer and maintain the application.

 

application-and-user-location-diagram
This diagram shows who is using which application on which site

The "application components" are deployed in locations, as well as roles or actors (these are, therefore, occurrences of roles, actors and application components).
In the example above, "Customer" is not localized. It is, therefore, the role (and not an occurrence) which is used.

headquartersHeadquarter location: Geographically defines where the elements of the enterprise are deployed (organization units, hardware devices, actors, etc.)

site-locationSite location: Geographically defines where the elements of the enterprise are deployed (organization units, hardware devices, actors, etc.). Generally, an enterprise has one headquarter and several sites.

interaction-application-componentInteraction application component: Represents the top level components that manage the interaction with elements outside the IS. In most cases, it is a GUI component, such as here a web interface.

ApplicationApplication: This application component corresponds to legacy applications, off the shelf products, or can be an assembly of application components.

external-actor-32External actor: An actor that is external to the enterprise.

internal-actor-32Internal actor: An actor that belongs to the enterprise.

associationAssociation between two classes: An association has a name, and for each extremity provides the role name and cardinalities (possible number of occurrences) of related elements.

Comments   

Hendra Wijaya
0 # Hendra Wijaya 2017-12-06 04:57
Want to confirm, the diagram is showing the location of the actor and not showing the location of the server. Is that correct?

Thank you,
Hendra Wijaya
Reply | Reply with quote | Quote

Add comment

Leave this empty:


Security code
Refresh

Login

Sign in to use the forum and be informed of the latest news.

Latest comments