Describing structure and services of an application
At first, an application can be described from a logical point of view, see Describing Logical Application Architecture.
However, and from a concrete point of view, an application is described by several types of diagram;
an application structure diagram is used to represent the service interactions between the application components using service interfaces.
*For further details, see .For further details, see Application structure diagram.
A Scenario of application flows describes the flows exchanged between the IT services or the microservices used by the application. A scenarios can represent a particular application use case or more globally all the flows exchanged within this application.
*For further details, see .For further details, see Using a Scenario of Application Flows Diagram.
Flow scenario sequence presents the agents necessary for the scenario (IT services, microservices, data stores) and exchanged sequenced application flows.
*For further details, see .For further details, see Creating a flow scenario sequence diagram.
an application deployment architecture used to represent technical elements that support the application.
*For further details, see .For further details, see Describing an Application Deployment Architecture.
A Use Case Diagram used to represent the exchanges between the application and actors, according an UML approach.
*For further details, see .For further details, see Creating an application Use Case Diagram.
For more details on modeling applications with HOPEX IT Architecture, see Modeling application architectures.