|Environments and locations diagrams|
An environments and locations diagram depicts which locations host which applications, identifies what technologies and/or applications are used at which locations, and finally identifies the locations from which business users typically interact with the applications. This diagram should also show the existence and location of different deployment environments, including non-production environments, such as development and pre-production.
In this diagram, devices (servers, workstations) are embedded into (deployed) locations. Application components are in addition embedded within the devices.
Headquarter location: defines geographically where the elements of the enterprise are deployed (organization units, hardware devices, actors, etc.)
Site location: defines geographically where the elements of the enterprise are deployed (organization units, hardware devices, actors, etc.). Generally, an enterprise has one headquarter and several sites.
Server device: Represents a hardware platform, that can be connected to other devices, and on which are deployed application components.
Workstation: Workstation are connected via network links to the IS. Application components can be deployed there.
Application: This Application component corresponds to legacy applications, off the shelf products, or can be an assembly of application components.
Interaction application component: Represents the top level components that manage the interaction with the external of the IS. In most cases, it is a GUI component, such as here a web interface.
Association between two classes: An association has a name, and provide at each end the role name, and the cardinalities (possible number of occurrences) of related elements.
Sign in to use the forum and be informed of the latest news.