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.

environments-and-locations-diagram
The main applications and devices are located in Dallas

In this diagram, devices (servers, workstations) are embedded into (deployed) locations. Application components are in addition embedded within the devices.

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

site-locationSite 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-deviceServer device: Represents a hardware platform, that can be connected to other devices, and on which are deployed application components.

workstationWorkstation: Workstation are connected via network links to the IS. Application components can be deployed there.

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

interaction-application-componentInteraction 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.

associationAssociation 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.

Network computing hardware diagrams

Starting with the transformation to client-server systems from mainframes and later with the advent of e-Business and J2EE, large enterprises moved predominantly into a highly network-based distributed network computing environment, with firewalls and demilitarized zones. Currently, most applications have a web front-end, and looking at the deployment architecture of these applications, it is very common to find three distinct layers in the network landscape: a web presentation layer, a business logic or application layer, and a back-end data store layer. It is a common practice for applications to be deployed and hosted in a shared and common infrastructure environment. Therefore, it becomes highly critical to document the mapping between logical applications and the technology components (for example, servers) that support the application both in the development and production environments. The purpose of the network computing hardware diagram is to show the deployed logical view of logical application components in a distributed network computing environment.

network-computing-hardware-diagramThis diagram shows where application components are deployed, how the computers are networked, and so on

This diagram presents the hardware (servers, workstations) that are interconnected by a network, as well as the technical and application components that are deployed on this hardware.

Technical, architectural components such as web servers are added to the logical components identified in the application architecture.

server-deviceServer device: Represents a hardware platform, that can be connected to other devices, and on which application components are deployed.

workstationWorkstation: Workstations are connected via network links to the IS. Application components can be deployed there.

process-componentProcess application component: A process application component is responsible for a business process execution. It orchestrates the tasks of the process.

entity-componentEntity application component: An entity component is frequently derived from business entities, and is responsible for managing the access to the entity, and its integrity.

utility-componentUtility component: Represents an application component that is frequently reused, and most of the cases bought off the shelf.

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.

DataBaseApplicationComponent32Database application component: This represents a repository. In pure SOA architecture, these elements should not appear. However, for legacy analysis or technology architecture, modeling repositories or repository deployment can be useful.

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

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.

Processing diagrams

The processing diagram focuses on deployable units of code/configuration and how these are deployed onto the technology platform. A deployment unit represents grouping of business function, service, or application components. The processing diagram addresses the following questions:
- Which set of application components needs to be grouped to form a deployment unit?
- How one deployment unit connects/interacts with another (LAN, WAN, and the applicable protocols)?
- How application configuration and usage patterns generate load or capacity requirements for different technology components?

See network computing hardware diagram. Processing diagrams will use deployment in a more generic way, in order to present deployment units. Deployment units can be presented as component instances where application components are deployed, or as physical utility components that will host the deployed application component (for example, an application server).

Associations between these deployment units will represent the connection (for example, a network), while information flows will indicate the nature of the information being exchanged.

In these diagrams, indications about capacity requirements are provided.

processing-diagram
This processing diagram shows how application components are deployed under the different kinds of application servers

The deployment configuration above is still independent of future deployment on physical servers.

entity-componentEntity application component: An entity component is frequently derived from business entities, and is responsible for managing the access to the entity, and its integrity.

process-componentProcess application component: A process application component is responsible for a business process execution. It orchestrates the tasks of the process.

utility-componentUtility component: Represents an application component that is frequently reused, and most of the cases bought off the shelf.

information-flowInformation flow: Defines the flow of any kind of information (business entity, event, product, informal, etc) between active entities of 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.

Login

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

Latest comments