HOPEX Aquila EN

EA - IT Architecture V2 > Introduction TO HOPEX IT Architecture > Before starting with HOPEX IT Architecture > Using IT architecture diagrams

Using IT architecture diagrams

For more details on the use of diagrams, see Diagrams.

With HOPEX IT Architecture, an application object may be described by different diagrams. Each diagram type corresponds to a specific view of the object: internal architecture, deployment architecture, flows exchanged inside the object and flows exchanged outside depending on the context of use of the object. Depending on the described object, each representation is associated to a diagram type.

• External data flows are represented in an Environment Diagram. This diagram type contains the described application object and the application flows exchanged with partners (other application systems, applications, data stores, org-units or
position type).

• The internal architecture is described by a structure diagram representing the object components their exchanges. A structure diagram can be designed for an application, an application environment, an application system, an application system environment, a logical application system, a logical application, an application service or a microservice.

• The deployment architecture is described by a diagram representing the deployable application packages, the microservices and the deployable data package used as well as the required communication techniques.

• The Internal Data Flows are represented in a scenario of flow diagram describing the messages exchanged between the object components. With HOPEX IT Architecture, you can design two types of scenario of flow diagram:

• The Scenario of flows diagrams that describe the flows exchanged in different use scenarios of the object described.

• Scenario of sequence diagrams that describe the chronology of the flows exchanged in different use scenarios of the object described.

To use Scenario of Application Flows Diagrams, open the Options window and check that IT Architecture > Activate Flow Scenario Sequence Diagrams option is activated.

• The external interactions are represented in a Scenario of Flow Diagram describing the external service interactions of an application object in a specific environment. This diagram contains the described object and the service interactions with partners (other systems).

Representation	List of involved diagrams
Internal Architecture	• Application structure diagram • Architecture • Application System Structure Diagram • IT Service Structure Diagram • Microservice structure diagram • Application System Structure Diagram • Logical application structure diagram • Structure diagram of the logical application system • Deployable Application Package Diagram • Resource Architecture Assembly Diagram • Hardware Assembly Diagram • IoT Device Assembly Diagram
Internal Data Flows	• Scenario of Application Flow Diagram • Scenario of Application System Flows Diagram • Scenario of IT Service Flow Diagram • Scenario of Microsystem Flows Diagram • Scenario of Logical Application System Flows Diagram • Scenario of Application Flows Sequence Diagram (UML) • Scenario of Application System Flows Sequence Diagram (UML)
External Data Flows	• Scenario of Application Environment Flows Diagram • Scenario of Application System Environment Flows Diagram • Scenario of Logical Application System Environment Flows Diagram • Scenario of Application Environment Flows Sequence Diagram (UML) • Scenario of Application System Flows Sequence Diagram (UML)
External Interactions	• Application Environment Diagram • Application system environment diagram • Logical application system environment diagram • Resource Architecture Environment Diagram
Deployment Architecture	• Application Deployment Architecture Diagram • Application System Deployment Architecture Diagram • Microservice Deployment Architecture Diagram

Creating a structure diagram

To create a, Application system structure diagram, for example:

1. Open the Diagrams property page of the application system and click Create a diagram.

2. In the choice window, select Structured diagram > Internal Architecture.

The diagram opens in the edit area. You are now in the HOPEX graphic editor. The frame of the described object appears in the diagram.

Example of an application system structured diagram

By default, the diagram is initialized with the described object, represented by a frame; the components of the described object are positioned at the top of the diagram.

If the described object is represented in a higher level diagram, the new diagram is initialized taking into account participants and flows that are represented in the higher level diagram.

Diagram commands with HOPEX IT Architecture

Depending on their type, HOPEX IT Architecture diagrams propose specific commands.

Icon	Description
	Refresh channels Allows to update the content of the channels described in a scenario of flows. See Creating an application flow channel.
	Reinitialize components Add, in the diagram, the components of the first level of the described object.
	Auto Layout Enables to organize automatically the described object components in the diagram. See Auto Layout in architecture diagrams.
	Add Items Enables to complete the current diagram with the elements defined in other diagrams. See Environment diagram initialization. Available only for application environment and application system environment diagrams.

Auto Layout in architecture diagrams

If the environment contains components and interactions between components, each new diagram is initialized with these components displayed at the top left of the frame of the described environment.

The Auto Layout button allows you to reorganize the diagram elements taking into account the exchanged flows.

The Diagram compression/dilatation coefficient enables the specification of the distance to be expected between elements.

When you use the Auto Layout function, the previous presentation of your diagram is lost.

The auto layout facility is proposed for the following diagrams:

• Application Environment

• Application Environment Diagram

• Scenario of Application Environment Flows Diagram

• Application

• Scenario of Application Flows Diagram

• Application Structure Diagram

• Application Deployment Environment Diagram

• Application System Environment

• Scenario of Application System Environment Flows

• Application System Environment Diagram

• Application System

• Scenario of Application System Flows

• Application System Structure Diagram

• IT Service

• Scenario of IT Service Flow Diagram

• IT Service Structure Diagram

• Logical Application

• Scenario of Logical Application Flows Diagram

• Logical application structure diagramme

• Logical Application Deployment Environment Diagram

• Logical Application System Environment

• Logical Application System Environment Diagram

• Scenario of Application System Environment

• Logical application system

• Structure diagram of the logical application system

• Scenario of Logical Application System

• Resource Architecture Environment

• Resource Architecture Environment Diagram

Environment diagram initialization

An environment diagram represents a use context of an application or an application system.

An application environment is used to represent a use context of an application. An application environment allows presenting the other application systems, applications, microservices or actors with which this application can interact.

An application system environment allows presenting the other application systems, applications or microservices with which this application system can interact.

In order to simplify the description of a specific use context of an application system, for example, Add Items button provides the list of components with which the application system interacts and helps you to select the objects you wish to add in your diagram.

The Sub-Elements selection and Expand selected elements buttons help you in your selection.

Creating a Sketching diagram with HOPEX IT Architecture

A sketching diagram is a drawing that enables you to exchange with your coworkers without an issue of methodology or formalism.

Sketching diagrams can then be reworked and transformed into diagrams recognized by an HOPEX Solution.

For more details on the use of a sketching diagram, see Sketches.

To create a sketching diagram for an application, for example, with HOPEX IT Architecture:

1. From the Applications navigation menu, select the application of interest to you and click Create a diagram.

2. In the wizard window, select Sketching diagram.

The diagram opens in the edit area. You are now in the HOPEX graphic editor.

Creating an ArchiMate@ diagram with HOPEX IT Architecture

HOPEX for the ArchiMate® Framework product provides facilities to use the set of concepts defined by the Open Group for ArchiMate®. ArchiMate® concepts are mapped with HOPEX Enterprise Architecture building blocks so as to manage compatibility and continuity with other models.

You can associate a diagram based on ArchiMate@ formalism to an application, for example.

For more details, see Using ArchiMate Diagrams in an Enterprise Architecture solution.

Using diagram comparison

The comparison of diagrams of an application system or architecture of an application system deployment enables to compare different versions of the same object.

For more details on use of a diagram comparison Facilities Comparing Diagrams