Defining the Deployment Architecture of an Application
An application deployment architecture allows to represent Deployable Application Packages and Deployable Data Packages as well as the Technical Communication Lines necessary for their exchanges.

A deployable application package is a split of application code according to technical criteria for hosting purpose. For example, it may be N tiers, Front End/Back End/… or GUI/Business Logic/Database etc... Each deployable application package is associated to required technologies (for running) and can host code for several IT services. Architect can also prescribes a kind of hosting artefact (IaaS/PaaS cloud service or IT server model).

A deployable data package represents a data part of an application deployment that must be hosted and accessed by application services (code) to run. Each deployable data package is associated to required technologies (for data hosting and access) and can host several data structures. Architect can also prescribes a kind of hosting artefact (IaaS/PaaS cloud service or IT server model). Architect can also prescribes a kind of hosting artefact (IaaS/PaaS cloud service or IT server model).

A package connection represents a connection requirement between deployable packages. A client (package) requires a connection to a server (package). The connection is defined by a Connection Type and can be characterized with technical flow measures.
Several viewpoints are proposed in HOPEX IT Architecture:
Application Deployment Architecture Diagram
To facilitate the creation of your application deployment architecture, HOPEX IT Architecture provides standard deployment architecture diagrams.