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