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 interactions between the application components in the form of exchange contracts.
For more details, see Application structure diagram.• An scenario of application flows describes the flows exchanged between the IT services or the micro-services used by this application. A scenarios can represent a particular application use case or more globally all the flows exchanged within this application.
For more details, see Using a Scenario of Application Flows Diagram.• a flow scenario sequence presents the agents necessary for the scenario (IT services, micro-services, data stores) and exchanged sequenced application flows.
For more details, see Creating a flow scenario sequence diagram.• an application deployment architecture used to represent technical elements that support the application.
For more 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 more details, see Creating an application Use Case Diagram.For more details on modeling applications with HOPEX IT Architecture, see Modeling application architectures.