Describing Applications
With HOPEX IT Architecture an application is described by:
• The information flows it processes and transports, see Describing flow scenarios,
• The elements that provide the services associated with the functionalities it covers, see Describing the structure of an application and its services..
These complementary approaches help to draw up an exhaustive list of the components of an application (services and APIs) and the components of its environment interacting with it.
Describing flow scenarios
HOPEX IT Architecture offers flow scenario facilities to describe precisely data exchanged.
At each level of the application architecture, it is possible to define flow scenarios between system components in specific contexts.
The objective of flow scenarios is to verify that content is correctly conveyed between components.
The scenario of application flow diagram below describes the "Purchase request management" application.
Example of a Scenario of Application Flows for "Managing Purchase Orders".
For more details on flow scenarios, see Creating a flow scenario sequence diagram.Describing the structure of an application and its services.
Structure diagrams use interactions to describe the data exchanged between components.
“Purchasing Request Management" application structure diagram
The “Purchase Request Management” application uses two IT Services: “Display purchase request list” and “Assign and handle purchase request”. The “Assign and handle purchase request” IT service invokes Excel micro-service.